Windows 10 update freezes at 82% complete

Anonymous
2017-12-17T22:20:14+00:00

Gateway SX 2851 Desktop has been trying to update to Win 10 version 1709 build 16299.98 from version 1703 build 15063.726. It started as a win 7.

This has happened with version 1607, 1703, 1709, 1803, 1809 (skipped), & 1903.

Every time the update runs it freezes at 82% complete. It will sit there for hours on the blue updating screen but the spinner is frozen. It appears there is no hard disk activity happening. My only choice at that point is to power-off the computer. When I re-power it and restart it attempts to recover the update and fails. It then reverts back to the previous version. 

This has happened 3 times now. I have uninstalled McAfee before the first attempt. I also uninstalled Easy Tether and Virtual Box. No other programs are running.

Any ideas from anybody?

Moved from: [Windows / Windows 10 / Network & internet]

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2018-01-29T02:05:37+00:00

Hi, Bill, I too, have had the exact same problems as you, even though I have an older computer, an Acer Aspire from 2011.. I found this in another thread:

Quote:

I was having a similar problem, and after multiple attempts (over 7 times) trying different solutions like disabling virus protection, disabling startup programs, running update database corruption repair, etc. My computer never got past 81% before freezing and not updating.

I stumbled across a forum talking about problems with  Anatel  PCI-E Wlan cards (wi-fi) and old drivers that would hang up their computers and after removing the card (not just disabling) their machines would update and run fine. Since I was running my machine through an Ethernet connection, connected to an access point, I could remove the Anatel card in my computer and still have an internet connection. I tried it, and my computer a Gateway FX6860 updated to Windows 10 Fall Creators version without any problems.

Check to see if you have an Anatel wifi card and remove it and replace it with something newer or an Ethernet or usb connection to the internet and try the update. this worked for me.

I took out the Anatel Wi-Fi card and tried the updates again and they WORKED.

Was this answer helpful?

100+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2018-05-05T18:22:55+00:00

Pull out the PCIe Wireless card and run the update again. Wireless cards based on the RT3090 PCIe wireless card hang every Windows Update since the Creators update, including the Fall Creators Update and the April 2018 update. (1703, 1709, 1804)

Was this answer helpful?

40+ people found this answer helpful.
0 comments

102 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-06-29T02:58:01+00:00

    Hi,

    I checked my system and I also have an Anatel wifi card installed. I removed the card, ran updates and it worked. Thanks for the tip!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-07-05T01:31:33+00:00

    Wow, hours and hours spent trying to solve this. My dad paid $100 and the "geek" couldn't solve it. 

    I did the Microsoft support, they took over the machine, did the usual resetting of windows update, delete folder, install windows fresh - same symptoms as everybody here, froze at 75% blank screen, power off, then 81%, power off, then came back to an essentially dead version of windows where I had to apologize for seemingly destroying the machine. Luckily if you re-power enough times it eventually rolls back to 1703. Later I searched and found this thread. I am back at dad's for the 4th, so I immediately removed the side cover of his Gateway machine, pulled the wifi card - lo and behold, it's an Anatel card! 

    The reinstall/update finally worked after many months and dozens of hours of struggles! 

    Thanks Vishnu from Microsoft Support, you may want to stop wasting people's time with a solution that doesn't work (and that I tried many times myself.) I didn't get back to support as most people don't - they ask if it was successful before you can possibly know - not very useful. So append Windows Support Case Number 1431724164 - solution did NOT work - customer had to find solution on their own. Again.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-07-05T14:07:07+00:00

    I submitted this solution to MS Support directly a long time ago.  Sadly, MS support has gone the way of most company's help desks and support capabilities; the epitome of "you get what you pay for".

    Was this answer helpful?

    0 comments