New
#270
Thank you Maurice.
Something niggled me all night in that although on various attempts to get the update to install I had deleted the folder C:\Windows\Softwaredistribution\Download on this last occasion I couldn't remember doing it.
Anyway after my last failure last night I used system restore to a point on 29th September. This went OK apart from the fact that it messed up Norton which I had to uninstall and re-install. I was then out for the rest of the day and it hadn't auto installed so I thought I'd give it one more try being extra cautious that I followed all the steps. It installed in about 10 or 15 minutes. Well done Maurice.
I now have the 222 version.
I did then run wushowhide but couldn't find any mention of KB3194496.
Do I now have to run 'net start wuauserv' to start updates?
Many thanks,
David.
Yes, it is still being offered, and I just shot myself in the foot trying to find out. Wushowhide finally worked for me. The update was hidden. So I unhid it to see if it was still being installed. Apparently unhiding equates to requesting download and installation. Wushowhide now fails to hide it - I assume because it is being downloaded. And I don't know how to cancel a download and install other than shutting down , and that just delays things until I boot up again. So I guess I'm about to try installing the update on our laptop.
Good for you!... Didn't work for me, and I wish it had. Nor did the "office hours" settings...kept on trying to install. That was after a successful sfc /scannow run, as well...! I have no idea why the MCTool option worked, but I suspect a difference in the upgrade scripts between the MCT method and WU. Who knows!?
Thanks for replying! I tried it but it remains intermittent: restart works but not shutdown. I havent had that bug for so long.
There is another thing related to Num Lock, there is no need to press enter for the login password. Unless its a new feature, I had to press enter before version 1607.
Exactly the same as my system Mike. I've tried all sorts of stuff to enable numlock on the login screen but as you say it's intermittent. As you say numlock stays on fine after a reboot but from acold bootup I have to use the numlock key.
Actually there was one thing that worked for me and that was disabling fast sart-up. However it slowed my bootup time for a lot longer than it takes to press the numlock key :)
Read this ZDNet article and see if it will help you:
Why the latest Windows 10 cumulative update is failing and how you can recover | ZDNet