I intend to remain subscribed to this thread for the time being so that
(a) if you find and report here a solution that works for you, I can pass on your findings;
(b) if he or his technical advisers find a solution which works for his computer, and let me know the details, I can post here accordingly.
It may be that your computer's problem has now gone away. If not, the following may be of interest.
The similar problem mentioned in my previous post was finally resolved by the technical advisers replacing the hard drive, which they believed to be faulty, and reinstalling Windows 10.
After they had done that, this Microsoft update article and fix appeared.
There is some background information here .
The fixes (i.e. the non-automatic update, or the adjustments to the Registry) in the update article mentioned above may be worth considering if your computer's problem is likely to have been caused as in the two preceding paragraphs.
In the meantime I had experienced several of those wanting to update, then reboot, and If I let it reboot, it reached 33% and then cut out, restored the previous version. Once there was another error, with a code that I wrote down and gave the support people when I was there about an hour ago. And the last thing that happened, last night, after trying to update and trying to go back to the previous version for something like 3 hours without success, I gave up and shut down and disconnected the PC. I didn't want to fuss more about it, since it is less than a year old and under warranty.
So, we'll see what happens... Luckily I have two laptops, one of them a Mac and one Windows.
So, we'll see what happens...
That will be interesting.
Thanks for reporting back on this.
Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.