Must log out and back in after wakeup from sleep

This regards a new system running Windows 10 Pro, Version 1607, Build 14393.1358. I don't think this is the Creator's version, but not sure.

I initially had some problems with the Sleep mode. The computer would go to sleep (with traditional blinking light) for a few minutes, then wake by itself and shut down completely. Enabling the Hybrid Sleep mode seems to have fixed this, but one sleep-related problems still remains.

When waking from sleep or, for that matter, starting from cold, the Lock Screen comes up (although it shouldn't, as described below), and hitting Enter there brings up the sign-in screen. But when I sign in, the computer either wakes (or starts) properly except that changes I have manually made to the Registry don't apply. If I log out and back in again (no restart, just log out/in), then everything is fine.

The changes to the Registry are pretty simple. One is to bypass the Lock Screen, which I detest and have tried to defeat both with a Registry change (NoLockScreen DWORD=1), and by using the Group Policy Editor. The other is to change the Application Window background color from white to something less glaring. The first fix, for the Lock Screen, works some of the time, but always, when waking from sleep, app windows are white and I have to do a Log Out and Log In to make the registry hack work.

There's only one account on this computer, otherwise I'd think that the wake-from-sleep account was using a different set of rules. If anyone has ideas, I'm all ears. Thanks!

Thanks, Brink; saw that some time ago and made sure it was off.

One other thing I was wondering, which might have a bearing here: This computer was originally named "Lab" because it was supposed to replace a Win7 computer in an engineering environment. But for some reason the hardware on this Dell is not compatible with a development program... some USB issue... so it was repurposed for the office. I wanted to change the computer name, but that entailed creating a new Administrator account with the new name and copying a bunch of preference files from 'Lab' to 'Office' and then deleting the 'Lab' account. This proved too much of a hassle, so I dumped out of that and just deleted the new 'Office' account instead. Now, under Accounts, 'Lab' is the only one that shows. This does leave me wondering, however, if some vestiges of the old 'Office' preferences are still hanging around somewhere. With that account gone, and 'Lab' the only one showing, I would think that changes to the Registry should 'stick' for any log-on.

That link went to a Win7 forum post, and I couldn't find equivalent boxes under Win10, but I did check the single account on this machine and it looks like an Administrator/User account for sure.

It is Win10/Pro, but I did the Command Prompt thing anyway; here's what I get:

C:\windows\system32>net users Lab
User name Lab
Full Name Lab
Comment
User's comment
Country/region code 000 (System Default)
Account active Yes
Account expires Never

Password last set 6/27/2017 7:19:01 PM
Password expires Never
Password changeable 6/27/2017 7:19:01 PM
Password required No
User may change password Yes

Workstations allowed All
Logon script
User profile
Home directory
Last logon 6/28/2017 12:07:59 PM

Logon hours allowed All

Local Group Memberships *Administrators
Global Group memberships *None
The command completed successfully.


C:\windows\system32>

Was that recommendation to keep the Lock Screen from showing up? If so, I found out what that was all about. There's yet another way to inhibit the lock screen that I found on another group. You go to C:\Windows\SystemApps and find the entry: MicrosoftLockApp_cw5n1h2txycwy and rename it; putting .bak behind it is recommended. That works like a champ, except that Microsoft, those sneaky guys, evidently found a way to regenerate that item on the list! I found my original renamed entry (.bak) and a new one, from yesterday!

So, as you can see, I have now renamed the new one .backup and the Lock Screen stays gone. We'll see how long that lasts! If their ugly picture of rocks shows up again, then I'll implement your Customization Tutorial. Thanks for that one, haven't seen it elsewhere.

But back to the problem of the wakeup without the updated Registry value, I do have one more observation. With the Lock Screen disabled, when the Log-in Screen comes up from sleep, instead of a blank for the password there's a notification that a wrong password was entered. (Say, what?) So you click 'OK' and enter the password to start things going. This is not an issue when starting from cold; of course the Lock Screen shows, but when it's dismissed the blank for the password is there.

Actually, my desire to put the computer to sleep is based on my longtime experience with the Windows Vista system that it replaces. Boot took so long under Vista sleep was a necessity. But this Win10 machine boots so fast, I might as well just turn it off rather than put it to sleep. At least until enough MS Updates slow the boot process down over time. I truly appreciate your attention to this. Great forum!