16 Hours For A Win 10 Update

Forum Moderators: open

Message Too Old, No Replies

16 Hours For A Win 10 Update

RedBar

3:03 pm on May 17, 2017 (gmt 0)

Win 10 laptop up-to-date Monday evening this week.

Tuesday evening switched it on and it commenced an update that did not complete for 16 hours, During that time it failed to update twice.

Another Win 10 laptop updated seemlessly within 30 minutes.

Is there any way out of this Win 10 update nightmare other than leaving the machine switched on permanently? Saying that I have friends who have experienced similar even when leaving theirs on all the time.

I do not have this issue with my Lumia phones even when they have been switched off.

I want to buy a new PC box yet these awful update experiences are steering me away from Win 10, to what I have no idea, but a machine out-of-order for 16 hours is ridiculous.

engine

3:14 pm on May 17, 2017 (gmt 0)

There's a reason why it's not updating. In the failed data there is usually a link to follow to indicate of known issues. What did that say?

Was it a problem with the download, or was it a problem with the actual installation?

The idea is that you can just leave the box running and go away and it'll do it for you.

I'm not keen on leaving certain machines running overnight, too, so I usually have to run the update on those at switch on.

It's annoying, but i'd rather do that than not have the system updated.

RedBar

3:23 pm on May 17, 2017 (gmt 0)

What did that say?

"A security issue has been identified..."

This linked to an MS page regarding WannaCrypt, this was for both failures.

engine

3:27 pm on May 17, 2017 (gmt 0)

hmmmm, that's a bit of a worry.
I assume you've scanned the hard drive for malware.

Also, sometimes, independent a/v tools interrupt the Microsoft scan for malware and give a false positive.

RedBar

3:38 pm on May 17, 2017 (gmt 0)

I assume you've scanned the hard drive for malware.

System is clean as a whistle, I do that every weekend, I reckon MS was having an internal conflict with itself!

IanCP

9:09 pm on May 17, 2017 (gmt 0)

I've said for years the problem with M$ updates is they are drip fed to you. Most of the time that isn't a real problem, but 16 hours is right out of control. I've had installs literally stall though.

Complaining to Microsoft on the Windows Insider forums usually only elicits a "canned response" which is useless.

Just thinking about it, I can't ever recollect M$ really ever offering a solution to anything on those forums - mostly any solution comes from another person relating their own personal experience.

Sorry mate, I don't know the answer.

keyplyr

9:33 pm on May 17, 2017 (gmt 0)

16 Hours For A Win 10 Update

The Win10 updates have never taken more than 10 or 15 minutes for me and I have them set to update in the background, then let me know when a restart is needed.

Unless you're referring to the "upgrade" from an earlier OS version to Win 10. That took about 45 minutes for me.

They may be drip...drip, but I think the major factor is your ISP & the speed of your network. I have mine set to update when I sleep, then they install when I first turn on my machine in the morning.

The speed of the install is reliant on your processor.

I like the way it's set up.