requires a restart to finish installing 1709

This new setting attempts to prevent this by allowing Windows to use users’ sign-in credentials to create a special token. Before this setting, a user might log in to their PC only to find they cannot use it until an update finishes.

The reasoning for it makes enough sense: Some updates require a PC to restart and then sign back in to finish installing. So what exactly is this setting doing? I set out to learn more… A Brief HistoryĪ little more research into this setting showed that Microsoft first introduced it in Windows 10 Insider Preview Build 14291. After disabling it, Chrome did indeed stop automatically launching after logging in. NOTE:In Windows 10 versions prior to 1709, this setting is worded as “Use my sign in info to automatically finish setting up my device after an update” “Use my sign-in info to automatically finish setting up my device and reopen my apps after an update or restart” Still nothing stuck out as the cause… I knew this had to be something simple.Īfter a lot more troubleshooting and inquiring others, the following Windows settings came to my attention found under Settings > Accounts > Sign-in Options > Privacy: I dug further into the plethora of Registry autostart keys, Group Policy settings, Task Manager, and the Windows Task Scheduler. I checked the typical Windows startup directories for both the user profile and the system thinking this must be the issue.

Google Chrome would consistently automatically launch and show it’s previous browsing session whenever Windows was logged into. Successfully Tested On: Windows 10 Home versions 1703 - 1809, Windows 10 Enterprise versions 1703 - 1809, Windows 10 Long-Term Servicing Channel (LTSC) version 1809Īfter upgrading a number of personal computers to more recent builds of Windows 10, an odd problem came to my attention.

Requires a restart to finish installing 1709