No I'm on w7x64 mostly. W10 is a PITA.
I had PL update to .131b
twice today (!?) I have it set to 'notify' for updates. The issue continues.
PC certainly likes telling me that msg & seems to do it at times inconsistent with the PL idle-saver schedule....?
OTAs for w10, I seem to one of many who had major BS with the upgrade to xx.1607. I purposely waited until the later 'fixed' version was released hoping the early victims had sorted it out. How wrong can you be?!

I had days of seeing '
restart to finish installing updates' on boot, after multiple failed 1607 patch attempts. Re-D/L GBs then fail & start again after reboot.
The problem is/was that this failure nukes the patch record. Win will then not allow ANY further patch to install - great for 'security'.
You either get it to upgrade somehow or kiss goodbye to any future fixes. I tried all sorts of big cumulative patches & workarounds. Got nowhere.
E.G.
C:\Windows\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 61% complete.
Windows Resource Protection could not perform the requested operation.
C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:I:\sources\install.wim:1 /limitaccess
Deployment Image Servicing and Management tool
Version: 10.0.10586.0
Image Version: 10.0.10586.0
[==========================100.0%==========================]
Error: 1392
The file or directory is corrupted and unreadable.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Several different error codes. Normally it failed at exactly 61% regardless of error.
In the end I gave up (like many others if forums are to be believed), & tried a fresh install from rom.
Failed. Failed. Failed.
- W10 tried to take over & do some sort of recovery -reboot & start over.
- I fdisked within w10 setup - a 'clean install' added 400mb to the 'system reserved' partition & yup - FAILED+reboot & start over.
After 3 variations of those 2 patterns I wiped the SSD outside of win control & started fresh. Went on!
Yaaay only 3 days & total drive contents loss!

Then I reconnected my other HDD & it decided to re-index the contents.
On cold boot the next day - guess what? Win says 'oh corrupted HDD - I'm going to 'repair' those TBs...' 5 hours later it finished. Obviously nothing ran properly after that.
2 days worth of chkdsk on boot & after boot have finally restored the pathways to the effect that I no longer get random bad references being flagged. It all ran perfectly before that patch, tho perfect isn't a word I normally associate with Windoze.

So yeah w7 is still my go-to. I learnt with Vista to never trust an MS OS before you get at least one service pack!
