The best way I can think of to test this is to do the following: What do you use for configuration management? More than likely, as others have said, it’s a configuration that’s causing this. This tells me that’s it not an update that caused this behavior. We now have upper management breathing down our necks because everyone is complaining about this issue and the CIO is trying to fend everyone off the best they can while we figure this out but nothing is working.ĭoes anybody have ANY ideas because we're at wits end here. I also found that my computer's screen will lock after 2 minutes but when I boot in safe mode it goes. So far the only thing I have found was earlier today when I was working on this issue is that my windows screen saver settings auto default back to five minutes even after changing the settings AND modifying the registry key to set the screen saver up to 15 minutes. * we did find a registry key that disables the computer's ability to lock entirely (including using Win+L), but this poses a security issue for obvious reasons and so we aren't going this route. There are no settings in our Azure AD tenant, group policy, or on-prem domain that pertain to screen saver and screen lock timers Disabling Dell Optimiser on computers that have it - Didnt work.
Disabling Windows Dynamic Lock (this is normally disabled by our policy anyway, but that's a whole other story) - didn't work.Power plan advanced settings - didn't work.modifying power plan settings - didn't work.To try and bypass this new "feature" we have tried: We have opened up a support ticket with Microsoft and they deny anything is wrong, but other companies have agreed with us that this is new and is affecting them as well. I work in IT for a company that has in the last few months been plagued by an update that has made it so nearly every computer we own now auto-locks after 2-5 minutes. I’ll update when we get this figured out.Īnd u/psokid outlined a great step by step process for checking where the problem lies, so if anyone else runs across this thread later, try that first.
It looks like we may need to go look through our AzureAD and Intune settings. We reconfigured the settings and applied the policy and everything is now working for 95% of employees.Įdit: Thanks everyone for your suggestions.
Most employees had their screen saver set to none so it just locked the screen. Specifically it was a configuration profile that was affecting the max time before the screen saver activated. We reimaged a device and figure out the issue was with an Intune policy. Solution: Thank you everyone for your suggestions.