But since the update is automated and forced, Windows tries to install it again after rebooting, causing a loop of reboots for some users.
Writer Adrian Kingsley-Hughes of CNET sister site ZDNet wrote about his travails trying to install the update on Sunday and getting stuck in a series of reboots.
The second trigger is to open a program that is associated with a file type that often reverts.
That second program also snoops at file associations according to procmon.
So more likely it is certain actions that the program causes sets up the first trigger; and another program completes the trigger sequence.
According to procmon, it does some registry snooping with file associations.
I was half expecting it to try regardless and break the associations completely, but was fortunate.
One user said the update fails and the PC reboots every single time.
Another person tried to manually install the update rather than waiting for Windows to install it but ran into the same glitch.
So forcing updates on Windows 10 users is a policy with definite pitfalls.
On a Microsoft Windows forum, other users wrote about their trouble trying to install the update.
This policy is clearly designed to try to protect users by making sure all Windows 10 PCs have the latest bug fixes and security patches.