📎 AI Summary:
The thread discusses an issue where the screen saver stopped working after installing a specific Windows 10 LTSB patch (KB3176492), with the user noting that the problem occurs when the DoD banner-related registry setting is disabled. The original poster investigates whether the update affected the screen saver’s functionality and confirms that the issue was present after the update but not before, leading to questions about whether the screen saver depends on the DoD banner. Contributors suggest troubleshooting steps, including testing with built-in screen savers and monitoring system logs, and suggest that the banner is unlikely to directly impact the screen saver. Overall, the discussion centers on identifying if the Windows update caused the issue and how to verify its root cause.
liz08

liz08

Active Member
Member details
Joined
Oct 9, 2017
Messages
21
Thread Author #1
Hello,

After windows 10 LTSB patch - Microsoft Security Bulletin MS16_095 - (KB3176492) , screen saver doesn't work, if dodbanner is disabled.

Note : screen saver being used is customized where in avi file is played after the screen saver time out.
Also there are no code level changes that would affect the screen saver performance.

Please let me know what were the changes incorporated in the above mentioned windows update that might have caused this issue.

Regards
 

Sort by date Sort by votes
Neemobeer

Neemobeer

Windows Forum Team
Staff member
Member details
Joined
Jul 4, 2015
Messages
8,995
#2
Do you mean the DoD as in gov and why are you removing the banner? Pretty sure that's a STIG requirement.
 

Upvote 0 Downvote
liz08

liz08

Active Member
Member details
Joined
Oct 9, 2017
Messages
21
Thread Author #3
Hello,

We have enabled a registry key to allow the user to show/hide the banner . As mentioned in my previous post, before the LTSB patch it was working as expected.
 

Upvote 0 Downvote
Neemobeer

Neemobeer

Windows Forum Team
Staff member
Member details
Joined
Jul 4, 2015
Messages
8,995
#4
Have you confirmed this update is the real culprit? I would remove the update and verify it's the issue.
 

Upvote 0 Downvote
Neemobeer

Neemobeer

Windows Forum Team
Staff member
Member details
Joined
Jul 4, 2015
Messages
8,995
#5
You may always want to test with a built-in screen saver to rule out the custom one.
 

Upvote 0 Downvote
liz08

liz08

Active Member
Member details
Joined
Oct 9, 2017
Messages
21
Thread Author #6
Hello,

The issue was verified using the OEM prior to the LTSB update and after the LTSB update... The issue is not reproducible in the old OEM..
 

Upvote 0 Downvote
liz08

liz08

Active Member
Member details
Joined
Oct 9, 2017
Messages
21
Thread Author #7
Hello,

I would like to know if screen saver is dependent on DoD banner.
 

Upvote 0 Downvote
Neemobeer

Neemobeer

Windows Forum Team
Staff member
Member details
Joined
Jul 4, 2015
Messages
8,995
#8
Couple of suggestions. You can try lowering the timeout to 1 minute and try running procmon to look for problems loading the screen saver or try Windows 10 - Troubleshooting program crashes with it configured to the screen saver. You might see some kind of failure if it runs and crashes.
 

Upvote 1 Downvote
Solution
Neemobeer

Neemobeer

Windows Forum Team
Staff member
Member details
Joined
Jul 4, 2015
Messages
8,995
#9
A logon banner shouldn't have anything to do with the screen saver. If the screen saver was built in-house it's certainly possible it's looking to see if the banner is enabled. A screen saver is a program so it can do validation of anything a regular program can.
 

Upvote 0 Downvote
You must log in or register to reply here.