XPS 8940, security issue, won't lock

Thank you! We have received the required details. We will work towards a resolution. In the meantime, you may also receive assistance or suggestions from the community members.

Have you tried using the Win+L key combo to lock the PC immediately before turning off monitors?

The time it takes to lock the PC automatically depends on low long it takes for PC to go sleep. And read this about opening the Registry and checking and, if necessary, changing the "NoLockScreen" setting....

It'll lock if I go to Start > Account > Lock.  However despite the monitors being set to time out after 10 mins, they will not, so the one monitor will just sit on the lock screen.

I just want to be able to confidently walk away from the computer and know the monitors will timeout and the computer will lock after 10 mins.  This has always been the way.

Try Settings > Personalization > Lock Screen > Screensaver settings > Set wait time and check box "On resume display login" . You can leave screensaver as None or set one if you like.

They buried that setting and it's in a different place now

I bet!  I loved every Cutlass I ever drove!  However not a '68

I set the Machine inactivity limit to 600 secs.  We'll see what happens.

First off, I love the screen name! lol

I have also done that already as well.  Screen saver is set to (none) and the wait time is set to 10 mins also I have put the check in "on resume, display lock screen."

If I go to Settings > System > Power & sleep it also is set for "When plugged in, turn off after 10 mins."

Frustrating I bet! See if these 2 posts might get you on track

https://www.tenforums.com/tutorials/108132-add-remove-dim-display-after-power-options-windows.html

https://answers.microsoft.com/en-us/windows/forum/windows_10-power-winpc/windows-10-issues-suddenly-started/c07d24ab-45a8-478b-bc70-6c474ff209b3

Still no luck. I ran powercfg /energy and noticed this: 

Does that monitor have a time-out setting on its own On-Screen Display (OSD) that needs to be changed?

Did you try using the Win+L keys?

Suppose you just turn that one monitor off?

Both are plugged into the GeForce 2060 Super.

I want to get away from doing it manually.   I would like the monitors to timeout after 10 mins and the computer to lock automatically... This is the way.

@DIGITALCat   - BTW: Which monitor is the one that won't time out, DP or HDMI?

Do you have an add-in video card and are both monitors connected to the add-in card or is one connected to onboard Intel UHD Graphics?

---

@DIGITALCat wrote:

Both are plugged into the GeForce 2060 Super.

I want to get away from doing it manually.   I would like the monitors to timeout after 10 mins and the computer to lock automatically... This is the way.

---

Yes, I understand, but just trying to cover possible reasons why one doesn't go off. Is the one that doesn't go off set as Display #1 or #2. What happens if you reverse them, eg, change #1 to #2 and #2 to #1?

Is something running in background that keeps that screen awake,eg syncing files to the cloud or checking for Windows or software updates, new emails etc?

Did you recently install the Flash Removal Update from Microsoft, KB4577586 ? There are sleep issues related to this update, but I don't know if that's what's going on with your PC.

That fix seems to be:

1. Setting>Windows Update>Other options>Set delay of Windows Update on max days
2. Close Setting screen
3. Wait some time (~1 min)
4. Open Settings>Windows Update>click Resume Windows Update at right
5. Close Settings screen
6. Full power-off, and boot, not a warm restart

You can also try changing the lock timeout settings in the Registry. Be sure to export (copy) the Registry and/or manually set a System Restore point before making any changes to the Registry to be safe.

Seem to remember a screen lock/sleep issue on a machine a couple years ago that had a user without a password. Adding a password to their account fixed the issue.

Also, something to try would be to set use my signin info to finish setting up my device to off under accounts > sign-in options. I've had issues with that with RDP.

Try a clean boot because it's very possible as @RoHe states you could have a program keeping your session active. That seems most likely at this point.