Windows 10 update 1709 issues

[Canadian Tech]

I have an Asus desktop on the bench that refuses to do a Windows 10 update to version 1709. I thought maybe it was an update issues so I downloaded it manually and tried to install it but no luck. The update downloads, starts to install then gets to about 50 or 60% and reboots to a back screen and will sit there for hours if you let it. Do a hard restart and it comes back and leaves where it left off until it hit 81% then once again it just freezes and will once again sit there for hours frozen at 81%. Restart the system and of course the update fails and it restores the previous version. Saw somewhere where it could be a compatibility issue so tried to block the update for 180 days through group policy but the update just comes back. I know I'm missing something but how do I stop this update from coming back? Or how do I get this update to install properly?

Edit: I forgot to mention that I differed the feature updates through Group Policy Editor. I also tried most if not all update fixes.

 

[GTP]

I had one similar, so I disconnected internet, uninstalled AV, went into device manager and uninstalled (not disabled) video, network and wifi drivers. Also uninstall nVidia/ATI drivers from "Programs and Features."
Manually ran the update, which completed without any issues.
Reinstall AV, devices and video drivers and we were good to go!
Hope this helps.

 

[Porthos]

I also tried most if not all update fixes.

If @Barcelona advice does not help (I would not waste that much time) Its time to back up and nuke it.

 

[GTP]

If @Barcelona advice does not help (I would not waste that much time) Its time to back up and nuke it.

Or this.
I had time that day so just wanted to do it out of curiosity.

 

[Canadian Tech]

I'm not sure a nuke and pave would help as I read somewhere that this Asus wasn't compatible with the update 1709.

 

[Porthos]

I read somewhere that this Asus wasn't compatible with the update 1709.

If in doubt I slap in a spare SSD and load windows on it.

 

[GTP]

I'm not sure a nuke and pave would help as I read somewhere that this Asus wasn't compatible with the update 1709.

Correct me if I'm wrong, but to my mind that could be possible but highly unlikely.

 

[fencepost]

Is the processor one of the ones that was going to have compatibility issues with the updates? I recall some kerfuffle last year about Microsoft dropping support for some processors with one of the updates, and basically pushing it over to the manufacturers to have responsibility for updates for those systems.

https://arstechnica.com/information...-could-be-ending-early-on-some-intel-systems/

 

[Porthos]

Would be a real low end netbook type processor if so.

The following Intel Clover Trail processors are currently not supported on Windows 10 Creators Update:

• Atom Z2760
• Atom Z2520
• Atom Z2560
• Atom Z2580

 

[orinoco]

If @Barcelona advice does not help (I would not waste that much time) Its time to back up and nuke it.

Correct me if I am missing a trick here, but surely this would be a massive ballache? I always try to avoid a N&P. I have fab which does some of the heavy lifting but the number of programs that need to reinstalled on most systems makes N&P my most avoided route to fixing. I subscribe to Ninite as well

 

[GTP]

Yeah sometimes an N&P is a PITA when they have programs from obscure sources or they've forget their licence keys passwords etc.
I know a lot on here - including me - advocate N & P's all the time and 75% of the time its the right decision.
The other 25% you just use your best judgement.

 

[orinoco]

My customers always tend to be in that group that have obscure programs and don't have their licence keys backed up, if it was a slick process I would definitely be a supporter

 

[Porthos]

but the number of programs that need to reinstalled on most systems makes N&P my most avoided route to fixing.

Every computeris different. I personally find , at least with home users they dont have lots of programs and most of the time the only program really on there might be Office. In reality yo did not make the mistake so times like this reinforce the need for image backups (upsell an external drive).
It usually boils down to what and how you charge for service. Program installs in my view is client responsibility and if they installed the programs in the first place then they can do it again or pay me $ to do it. If they dont have the disks whows fault is that? Not yours.

I know what I just said sounds dickish but it is how you explain it to them that wins them over.
I just had one where something went wrong and windows would not boot. His only software was Office 2010 which I was able to pull the key. (I have all the disks) So after a $80 install of Win 10 and a $30 install of Office I was also able to sell him a lifetime MB licenscefor $89 and a $69 external.

$191 profit. The 1st 40 gigs of a fab's backup is included. Anything over that is .50 a gig. He only had 6gigs of data.

 

[Porthos]

My customers always tend to be in that group that have obscure programs and don't have their licence keys backed up

Every one who owns a computer needs that come to Jesus moment when they learn to keep their software disks or downloads saved to a disk and the keys.

 

[Markverhyden]

I know what I just said sounds dickish but it is how you explain it to them that wins them over.

Exactly. When I make them aware that no one, not even M$, can completely repair a windows installation their objections tend to disappear.

 

[Canadian Tech]

So when I posted last night the client had already taken the system home and booted it up to find that the update wanted to run again, hence the reason for my post. I told her to bring it back to me but this morning she tells me she's not going to bring it back until she decides what to do. I did tell her the best option would be to wipe the system and reinstall so she said she'll decide what to do. She has been very pleasant about the whole thing so I don't think she's unhappy with my service.

 

[Canadian Tech]

Here's the article I found regarding some systems not being compatible with the Windows 10 Creator's Updates...https://answers.microsoft.com/en-us...s/5152bb37-f95d-48a6-b7b2-ad0d5c738923?auth=1 SO it seems that some systems are not compatible with the feature updates and Microsoft is leaving it up to the manufacturers to fix it.

 

[Metanis]

Treat the machine like it's had a viral or malware infection and do the standard repair methods that fix broken permissions and locked or hidden services.

 

[Larry Sabo]

I've had systems where, after I removed the HDD for testing/backup and re-installed it, the update completed without a problem. No idea why.

 

[glricht]

Correct me if I'm wrong, but to my mind that could be possible but highly unlikely.

I thought so too until just last week when I worked on an MSI MS-6650 AIO. It was originally Win 7 but had been upgraded to Win 10 about two years ago and worked fine all the way up to 1709.16299.125. Then the latest update came out to bring it to 192. After 192 was installed, the PC would freeze on reboot just prior to requesting the Win 10 password. If I did a system restore prior to the 192 update, it worked fine. Re-applied the 192 update and it froze again.

Temporarily replaced the HD and did a clean Win 10 1709 install. All was fine until the last update to 192 was applied and it froze again. Did the clean install multiple ways (sometimes updating the drivers -- including video -- before the Win updates, sometime not updating the drivers at all), but the PC always froze after applying 192.

Checked the MSI site and there are drivers up thru 8/8.1, but nothing specifically for 10. Only thing I can think of is that there's something in 10 that the MSI PC didn't support, but didn't come into play until the 192 update. Pure speculation, I know, but didn't know what to think.

Ended up re-installing Win 7 using the COA and it works like champ.

Weird.