This was a fun one to track down. When we did in-place upgrades on Windows 8.1 to Windows 10 1703, we never got this “Choose privacy settings for your device” screen. However, going from 8.1 to 1803, this screen will appear once for the first user who logs in with local administrative rights (even though we define certain privacy settings through GPO):
Trying to track this down was hard, but I was inspired by this post on Reddit.
The first stab I tried was logging in as a regular user, running ProcMon and then trying to filter on the registry write operations, but even then, it was too much noise (60K+ events). I then tried another approach. When you click the Accept button, there’s a UAC prompt that comes up with a title of “User settings: OOBE”. I made note of the word “OOBE” and cancelled it making changes. I ran Process Explorer as admin logged in as a regular user, then switched over to logging in as an administrator until I got the privacy screen, switched back to the regular user and then did a search for “OOBE” in the process list. One of the processes that came up was svchost.exe and it had the following key open:
I drilled around in this parent key and found this setting:
Ah ha! It was set to REG_DWORD 2, so I set it to 1 and tried logging in again as an administrator. No prompt to set privacy settings! I deleted the whole PrivacyConsentStatus key and the prompt still did not show up. I went back and set PrivacyConsentStatus to 2, logged off and back on, privacy settings page showed back up, I clicked the Accept button on the privacy page and then went back to this registry key to see the results. PrivacyConsentStatus was set back to 1 and a new entry called PrivacyConsentSID was created with a REG_SZ value with my user account SID. I deleted PrivacyConsentSID and it seemed to have no effect on the system.
The fix is simple: copy the following into a REG file and then fire it towards the end of OSD
Windows Registry Editor Version 5.00
- Soli Deo Gloria