Disable Get Even More Out of Windows

None of the many suggested registry keys worked for me. I was able to observe that when the hated "Get even more out of Windows" screen was displayed, there was a UserOOBEBroker.exe process running. Killing that process doesn't make the screen go away, but doing a reboot does of course. I created a scheduled task to run every five minutes and reboot the machine if UserOOBEBroker.exe is running. The task runs a cmd file that contains a line like this:

tasklist /fi "imagename eq UserOOBEBroker.exe" | findstr exe > nul && shutdown /r /f /t 0

My complete cmd file writes a line to a log file, so I'm able to see that a reboot has been triggered. I've had the scheduled task running on 40 remotely-manged machines for a few days, and it's successfully freed up several machines that had the nag screen displayed.

I wish that MS could give me back all the hours that I spent struggling with this problem.

That's what I'm saying. Bad on Microsoft for making it so hard for those of us that are not tech savvy.

I disable that registry key already as part of my imaging process. When i make a new windows 10 image, i start up the vm with the network card disconnected. i then run the following command. Need to do it before windows can connect to the internet. I might just be clicking "run as administrator" on this and it does work.

reg add HKLM\Software\Policies\Microsoft\Windows\CloudContent /v DisableWindowsConsumerFeatures /t REG_DWORD /d 1 /f

I do it this way because when i first started imaging windows 10, certain metro applications would prevent sysprep to run properly. So had to do before they got downloaded and installed.

Regardless, my point is this is set for me on every machine that has windows 10 in the company. And obviously does not solve the issue.

Once I upgraded my 22 machines from the 1909 to the 2004 Windows release and verified that.  the "Suggest ways I can finish setting up my device to get the most out of Windows" is unchecked in Notifications and Actions, I have not had a reoccurrence at any reboots since July. 

Rick

If you're using script, this command is confirmed to work:

REG ADD "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\UserProfileEngagement" /v "ScoobeSystemSettingEnabled" /t REG_DWORD /d 0 /f

This doesn't work on 1909, just saw the blue setup screen on a device with this registry setting.  Perhaps only 2004 respects the setting?

This was, as mentioned in the OP, already the setting I tried. Was supposed to work then too. Maybe 2004 finally started respecting the setting again, but I remain skeptical.