Can't complete 1709 update?

[Crockett12]

I have Windows 10 Home, version 1607. I keep getting a pop-up which says --

“Your device needs the latest security updates. Microsoft can’t install important security updates on your PC until you install the most current version of Windows 10.” Then – “Once the download is complete, you’ll be prompted to choose the best time for you to complete the installation. After it’s installed, your device will be running Windows 10, version 1709.”

Then it starts the download in the background and after the download it reboots my PC. After the reboot Windows Download Update Assistant says -- “Something went wrong. Couldn’t download Windows 10. Please check your network settings and try again. You can contact Microsoft support for help with this error. Here is the error code 0x80072ee2.”

I’ve sent an e-mail with the error code to Microsoft twice and have yet to hear back from them. I’ve gone through a number of attempted downloads with the same result. How do I fix this?

 

[Puffnstuff]

Have you tried using the update now site or the media creation tool instead of WU? I had issues with upgrading those early versions that only the media creation tool could overcome. You might also try the windows update troubleshooter.

https://www.microsoft.com/en-us/software-download/windows10

https://support.microsoft.com/en-us/help/4027322/windows-update-troubleshooter

 

[JackMDS]

Download your version of Win 10. Make a USB Flash

https://www.microsoft.com/en-us/software-download/windows10

Start your current Win 10. Navigate with Win Explorer to the USB and click on Setup, follow the instructions to do local update.

 

[Crockett12]

I've tried all the suggestions by Puffnstuff and JackMDS and none of them worked. I haven't even figured out how to turn automatic updates off -- which keeps trying to update to the point that it's becoming annoying. Haven't heard back from Microsoft either. Makes me wonder if they don't care -- or are having so many people having trouble with this update that they're under water with people needing help! Way to go Microsoft!

 

[Puffnstuff]

Try running a registry cleaner like auslogistics and allow it to repair your registry then reboot and see if the behavior persists. You should probably also run a system file check to make sure that your system file integrity is okay.

https://support.microsoft.com/en-us...er-tool-to-repair-missing-or-corrupted-system
https://www.auslogics.com/en/software/registry-cleaner/

 

[sonitravel09]

Nothing worked. Tried all solutions. Have to wipe this 1 month old install or disable updates altogether.

 

[JackMDS]

All of these post Updates conundrums while looking the same from the outside are not the same disorder inside.

The trick is to try some of the suggestions, if it helps, Hora, current installation is saved.

If it does not Help, then wiping out the SSD/HD and fresh Install is the solution.

We all due respect I do not thing that even Microsoft's Win programmers know the cause to all of these conundrums.

In the future this Update approach would probably would be labeled as past "Stupidity".

In medicine phenomenons like these occur frequently. In the first half of the 20th century, before the development of modern pharmacology, common solution to sever Psychiatrist illness was Lobotomy. Basically it is Brain surgery that eliminates the psychiatric symptoms but deemed the patient to become Intellectually / Cognitively None functional. In the latter half of the 20th these solution was eliminated (barring some very unusual cases that nothing else known help).

The constant online Updates of Win 10 as done these days is like the Semi-Lobotomy to the OS.

 

[RLGL]

Disable any aftermarket security software and try again.
Go to the windows Forums https://answers.microsoft.com/en-us/insider/forum/insider_wintp for up to date info. Also there was something about disabling dot net framework 3.5 in windows features. Turn it back on after install. There are more...........

 

[Nashemon]

What model computer do you have. There are in fact some computers with certain chipsets/BIOS that will not accept the 1709 update. Off the top of my head, most Gateway PC's from 2011 and earlier, and one particular ASUS PC. I don't recall the model numbers, but I know what they look like if I were to see one. I'm sure the list isn't limited to this, that's just what I've personally seen.

 

[BonzaiDuck]

All of these post Updates conundrums while looking the same from the outside are not the same disorder inside.

The trick is to try some of the suggestions, if it helps, Hora, current installation is saved.

If it does not Help, then wiping out the SSD/HD and fresh Install is the solution.

We all due respect I do not thing that even Microsoft's Win programmers know the cause to all of these conundrums.

In the future this Update approach would probably would be labeled as past "Stupidity".

In medicine phenomenons like these occur frequently. In the first half of the 20th century, before the development of modern pharmacology, common solution to sever Psychiatrist illness was Lobotomy. Basically it is Brain surgery that eliminates the psychiatric symptoms but deemed the patient to become Intellectually / Cognitively None functional. In the latter half of the 20th these solution was eliminated (barring some very unusual cases that nothing else known help).

The constant online Updates of Win 10 as done these days is like the Semi-Lobotomy to the OS.

I feel too chatty this morning, but I have to say that's an interesting analogy. And I agree that what looks the same on the surface may have many different causes underneath, making it hard to pontificate an effective general solution.

By the way. Did you ever meet somebody who left you with a desire that brain transplants were possible?

 

[Crockett12]

Quick update and question.
It's still not updating and I've tried everything suggested plus more. Rather than tell everything I've tired, I'll just give a quick rundown.
I tried using the tool to create installation media on a USB drive -- for downloading Windows 10.

I went through the process and rebooted after it looked like the reinstall had succeeded. After the reboot, a popup came up that said “We couldn’t install Windows 10. There was code: 0xc1900101 – 0x20017. Then – the installation failed in the SAFE_OS phase with an error during BOOT operation”.” I tried the USB route twice with the same result!
Since the error code indicated it was probably a driver issue -- I opened Device Manager and there weren’t any yellow exclamation marks. Then I went through all the drivers to see if any needed updating and searching automatically. All drivers showed "up to date"!

Since I’ve tried many fixes that haven’t worked – in order to not wipe my drive -- along with the laborous task of reinstalling everything -- I’m wondering if I bought a copy of Windows 10 Professional as an upgrade – and installed it without wiping the drive -- would it fix my problem?

Thanks,
Crockett

 

[Crockett12]

Forgot to reply to the guy who asked what computer I had.
Yes it's an ASUS!

ASUS ROG GL502VV DB71 Laptop
Intel Core i7-6700HQ 2.6 GHz
GeForce GTX 1070
Windows 10 Home 64 bit
16 GB DDR4 memory
GeForce GTX 1070 (8 GB GDDR5)
1 TB 7200 RPM HDD + 256 GB PCIe Gen3x4 SSD

Should I contact ASUS?

Crockett

 

[daveybrat]

What model computer do you have. There are in fact some computers with certain chipsets/BIOS that will not accept the 1709 update. Off the top of my head, most Gateway PC's from 2011 and earlier, and one particular ASUS PC. I don't recall the model numbers, but I know what they look like if I were to see one. I'm sure the list isn't limited to this, that's just what I've personally seen.

Agreed, i've had several Gateway PC's 2011 and older and a few Asus towers that simply will not take 1709 even with a clean install on my test SSD drive.

 

[Kaido]

Agreed, i've had several Gateway PC's 2011 and older and a few Asus towers that simply will not take 1709 even with a clean install on my test SSD drive.

Hmm, I was just working on some systems last night & a couple wouldn't take the 1709 no matter what I did. I'll try a fresh install from the MCT on USB, but now I'm having doubts. Dang.

 

[daveybrat]

Hmm, I was just working on some systems last night & a couple wouldn't take the 1709 no matter what I did. I'll try a fresh install from the MCT on USB, but now I'm having doubts. Dang.

I've had it now on over a dozen desktops. The problem is an incompatibility with the old bios on the motherboard. Problem is that Gateway, Acer, and some Asus models don't have any newer bios's available.

 

[Kaido]

I've had it now on over a dozen desktops. The problem is an incompatibility with the old bios on the motherboard. Problem is that Gateway, Acer, and some Asus models don't have any newer bios's available.

Wow lame. Is it due to not having UEFI?

 

[daveybrat]

Wow lame. Is it due to not having UEFI?

Nope, i've installed it on even older computers with no UEFI support and it's worked fine. It's just certain vendors motherboards that have some hardware incompatibility with 1709. It'll even work perfectly with 1703 but as we know it'll just keep trying to install 1709 anyways.

 

[JackMDS]

Put the installation on DVD and give it a try booting from the DVD Drive.

 

[BonzaiDuck]

I agree with Jack. Your "activation" would have been assured with the installation of version 1607, and you should be able to make a media disc or USB of the latest version and install it.

I am skeptical about reports that older systems and BIOS's show failures installing Windows 10 #1709. I could be wrong, the information from those above who mentioned certain models and makes may be useful.

But I have an old GATEWAY E475 M executive laptop with a T8300 C2D processor -- released around 2007 or 2008. I installed Windows 10 on it in spring 2015. It has been through all the updates including #1703 and #1709 -- the latter most recently and at most a few weeks ago. It runs tip-top perfect.

Here's some more information that may or may not be useful. I've discovered that my dual-boot Win7SP1-64/Win10-64 system gets a corrupted boot sector or MBR after the Creators or Feature updates. It is easy to fix with a Macrium Rescue disk -- which you can obtain Free and burn yourself. I'm wondering if this could be the trouble with the OP's installation.

Would a system that was originally configured as MBR rather than GPT cause this problem? The OP's system is a fairly recent system with what looks to be a SKYLAKE processor.

Something else is going on there. "Cannot download Windows 10" -- On SOME system, you should be able to create a reliable install disc. There is also a feature called "Windows Update Assistant." On that particular laptop, there HAS to be a fix for this.

 

[RLGL]

Is fastboot disabled in the BIOS settings? This setting can cause issues with the updates. Needs to be set to
"disabled". There are numerous other causes, best to do a fresh install

 

[Polar2002]

I also tried every thing to update to 1709. Nothing worked. Today, I use the Media Creation Tool to install 1803. To my surprise, it installed perfectly.

 

[Kaido]

I also tried every thing to update to 1709. Nothing worked. Today, I use the Media Creation Tool to install 1803. To my surprise, it installed perfectly.

I think they must have patched things up. Did a few 1803 installs today without a hitch.

 

[daveybrat]

I'll chime in as well. I've had numerous older PC's that simply would not take 1709 either in an update or even a clean installation. But i tried those same PC's with the new 1803 build and it works now. Not sure what changed but i'll take it!

 

[Eug]

Good to know that 1803 may play nicer. My nettop wouldn't take 1709 whatever I did... until I swapped out the Intel 330 in it for a different SSD. After that it worked fine with 1709.

It seemed 1709 was just not compatible with certain combinations of hardware.