Windows 10 Already Upgraded to 1703 Continues to Download

check

  • I've run into similar non-specific upgrade errors due to being on older BIOS versions. If these are all the same model computer, I would look for common denominators like BIOS revision or installed drivers or software.

    1 found this helpful thumb_up thumb_down

  • View Best Answer in replies below

    65 Replies

    • jrp78

    • Hi jrp78, thanks for the reply, but I've already done this. Still have no luck.

      Was this post helpful? thumb_up thumb_down

    • So there's no meaningful error from the media creation tool gui when you try to run the upgrade that way?

      Was this post helpful? thumb_up thumb_down

    • I have the following errors

      For media creation tool

      for windows update


      for Windows update assistant, it just says "Windows Update Failed"

      Was this post helpful? thumb_up thumb_down

    • Running a manual upgrade will give you more details - but failure could be because of FDE (think bitlocker), AV or other unsupported product

      Was this post helpful? thumb_up thumb_down

    • What AV software if any is installed?  Wass the latest build installed before trying the 1803 upgrade?

      Was this post helpful? thumb_up thumb_down

    • jrp78, I replied with screenshot of errors, but still being reviewed by spiceworks moderators.

      Rod-IT;AceOfSpades, no antivirus, just Windows Defender. the current build is Windows 10 version 1709 (OS build 16299.579)

      Was this post helpful? thumb_up thumb_down

    • It clearly has something stopping the upgrade - does it have bitlocker or any other full disk encryption, is it dual boot, does it run Hyper-V - it has to be doing something.

      Was this post helpful? thumb_up thumb_down

    • christianearlerosario2 wrote:

      I have the following errors

      For media creation tool

      for windows update

      for Windows update assistant, it just says "Windows Update Failed"

      Make sure if you have dual boot to mark the current Windows Partition to make it active.

      Was this post helpful? thumb_up thumb_down

    • Is this a case of one of the hidden partitions being too small?  I don't recall the details of that one.

      Was this post helpful? thumb_up thumb_down

    • Here are a few things you could try

      - run Microsoft Update Troubleshooting tool https://support.microsoft.com/en-gb/help/10164/fix-windows-update-errors

      - make sure to have the latest BIOS

      - startup in a clean boot state, and try running the update again

      2 found this helpful thumb_up thumb_down

    • For about 10 of the 150 computers we have on win 10, I have had to set back to factory and run all of the updates.

      It was quicker for me to do that as background task than to try to spend hours nutting it out.

      If it was more than 10 computers I would have done something more drastic, but I was able to spread them out over time.

      Was this post helpful? thumb_up thumb_down

    • I was just thinking maybe the media creation tool has it's own logs. I found this article. https://support.microsoft.com/en-us/help/928901/log-files-that-are-created-when-you-upgrade-to-a-new...

      Check to see if you have any logs that might have some more clues.

      Was this post helpful? thumb_up thumb_down

    • No Antivirus ? Don't virus's mess with boot sectors if they can ?? Scan the machine with Norton or something with a bit of guts regardless !

      0 of 4 found this helpful thumb_up thumb_down

    • How are you deploying the OS? It shows errors related to an agent.

      Was this post helpful? thumb_up thumb_down

    • We recently came across this issue it was related to the language pack that was installed on the machines when they we originally pre built by the vendor.

      I created an image to include the 1803 though the windows deployment tool kit extracted the correct version for the new machines.

      but the work around for us was to download the correct language version from US to UK (Caters from Australia Language)

      having said that we are using desktop central to manage the patches not WSUS and downloaded the 1803 update then manual install that to the affected machines

      Hope this might assist in the case

      cheers Scott

      Was this post helpful? thumb_up thumb_down

    • I've run into similar non-specific upgrade errors due to being on older BIOS versions. If these are all the same model computer, I would look for common denominators like BIOS revision or installed drivers or software.

      1 found this helpful thumb_up thumb_down

    • Depends on how much time you have, I am sure this could be resolved.

      1. What is the hard drive set as in the BIOS?

      2. Does this happend to other machines?

      3. What is the machine type?

      Was this post helpful? thumb_up thumb_down

    • Depends on how much time you have, I am sure this could be resolved.

      1. What is the hard drive set as in the BIOS?

      2. Does this happend to other machines?

      3. What is the machine type?

      1 found this helpful thumb_up thumb_down

    • I had similar problems with this update.

      I found using the Windows 10 Update Assistant worked for me.

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

      2 found this helpful thumb_up thumb_down

    • Uninstall Java, and AV. I have Java mess up the update.

      0 of 1 found this helpful thumb_up thumb_down

    • Steve713

    • ChrisN315 wrote:

      I had similar problems with this update.

      I found using the Windows 10 Update Assistant worked for me.

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

      I had to use the same thing on a couple of machines.  No obvious reason for the failure but I think it was hardware related due tot he fact almost all my problem machines are from the same batch.  Everything was as up to date as the manufacturer would allow.

      On one machine it still failed trying this so I backed up the profile and did a clean install of 1803 and it's been fine since.  Except that 1803 seems very heavy so it's slowed it down horribly but that's not unique to this machine.

      Was this post helpful? thumb_up thumb_down

    • Never had this happen with the upgrade to 1803, but I recall often having update issues caused by SATA drivers.  Try removing the name-brand SATA driver from Device Manager (Intel, etc) and let Windows install a generic driver.  Reboot, and try the update again.

      This is one of those cases where the solution is counter-intuitive.  Using the "right" driver caused a problem, while using the generic driver fixed it.

      1 found this helpful thumb_up thumb_down

    • We have had a similar situation as well. On one machine we did a restore back to a couple of weeks prior to the last update then re-launched the update and that worked.

      Was this post helpful? thumb_up thumb_down

    • Happens quite often to us when running software to deploy and image.  Download Microsoft Update Assistant and it will download and install just fine.  It is a pain when you have 20-30 PCs to do that to, but that's the fix I have found to be the least invasive.

      https://support.microsoft.com/en-us/help/3159635/windows-10-update-assistant

      1 found this helpful thumb_up thumb_down

    • Sorry this is a long chain and may have been addressed. Did you roll back the last update then try the upgrade assistant? We had to do that on a few machines.

      Was this post helpful? thumb_up thumb_down

    • Looking at the log, you have a corrupted Microsoft Update service (GUID = "7971F918-A847-4430-9279-4A52D1EFE18D").  When this happens you will also have problems installing security patches on that machine.  I had a couple of Windows 10 v1703 machines with this issue.  The way I've gotten around this in the past is to create an ISO image of the Windows 10 update and do the update manually, but do NOT check the box to get updates during the main install.  After the install those machines started working properly.

      1 found this helpful thumb_up thumb_down

    • I had same issue when we updating to 1803. Make sure the display drivers of the system is up-to-date.

      The main issue that caused my computer from not updating was the update not able to restore  the "Recent Items" list  (From my log files). I cleared the list and the update was successful.

      https://community.spiceworks.com/topic/2132445-need-help-with-windows-10-1709-and-1803-update-errors

      1 found this helpful thumb_up thumb_down

    • If this is just one computer, you're wasting your time. Re-image. Always consider how much time you're spending to fix when you could just start fresh in a predictable & minimal time frame.

      EDIT: Apparently the truth isn't helpful to someone out there, so I'll throw in stuff the OP has probably already tried. I still think that based on the fact he's opening a topic here and didn't say computers--plural, he's already wasted too much time.

      1. Reset windows update, scripts are available here on Spiceworks.
      2. Run SFC

      3. 'Reset' Windows

      If that doesn't work,then re-image because you've definitely wasted more time than that would take.

      3 of 4 found this helpful thumb_up thumb_down

    • We had to uninstall Symantec and use Windows Defender to get 1803 to work (which is fine for us).

      Was this post helpful? thumb_up thumb_down

    • Everything I'm reading on that error is that you don't have enough resources. What are the specs of the machine you're trying to update? How much free space does it have (feature upgrades are known to require up to 40GB free space)?

      Was this post helpful? thumb_up thumb_down

    • As something else to try, a basic chkdsk /f on c: and the recovery partition may help, and an sfc /scannow never hurts, its always a good place to start by checking file integrity, otherwise WU Assistant as other have suggested or Create an 1803 iso and don't check for updates during install.

      1 found this helpful thumb_up thumb_down

    • Mike400 wrote:

      Looking at the log, you have a corrupted Microsoft Update service (GUID = "7971F918-A847-4430-9279-4A52D1EFE18D").  When this happens you will also have problems installing security patches on that machine.  I had a couple of Windows 10 v1703 machines with this issue.  The way I've gotten around this in the past is to create an ISO image of the Windows 10 update and do the update manually, but do NOT check the box to get updates during the main install.  After the install those machines started working properly.

      Beat me to it Mike400!

      I have hit a few of these also where I have had to run the update manually from ISO and not take the updates (though, it still seems to pull updates later in the session on some).  Then just run Windows Update\WSUS later.  Do the manual install with updates, and I blows up.

      I had 1 random one where it ended up being the USB dongle for my Logitech keyboard\mouse combo that threw a similar error (but that was for an older update, not 1803 or 1709).

      1 found this helpful thumb_up thumb_down

    • Rod-IT wrote:

      It clearly has something stopping the upgrade - does it have bitlocker or any other full disk encryption, is it dual boot, does it run Hyper-V - it has to be doing something.

      FDE may not be this obvious. In all my experience with any Win10 upgrade, you won't get errors. The upgrade simply won't be applied, once it reboots. You'll likely get some odd boot screens, and dual-booting.

      Was this post helpful? thumb_up thumb_down

    • The easiest is to backup, wipe & install fresh & restore files.  I have one PC that still won't properly update - its a driver issue that's not compatible and i haven't taken time to fix it and since its my machine - i really don't care I'll work around it.  the remainder that I have done this with I have updated all the drivers to be new or current from the manufacturer and there hasn't been an issue to date

      Was this post helpful? thumb_up thumb_down

    • Is upgrade the only option or can you not create a another partition, and wipe the original? If not, I would try as others suggested and use the upgrade assistant. It scans and tells you any possible reasons that an upgrade is not possible.

      Was this post helpful? thumb_up thumb_down

    • Make sure that the firewall or anything isn't blocking it.  I would start with a clean install if you can if this isn't already a clean one.  I would also check if any Antivirus could be blocking it, etc.

      Was this post helpful? thumb_up thumb_down

    • Downlevel phase: Because this phase runs on the source OS, upgrade errors are not typically seen. If you do encounter an error, ensure the source OS is stable. Also ensure the Windows setup source and the destination drive are accessible.

      It says it is failing at this phase so this might be something  you have to check if you have not already.

      Was this post helpful? thumb_up thumb_down

    • I've had several machines that I needed to remove from my domain, update, then rejoin. Haven't had the time to get down to the root cause yet.

      1 found this helpful thumb_up thumb_down

    • One thing we do in our IT department when Windows update is hung up or gives us an error is go into the registry (as admin) follow this path: HKLM>software>policies>Microsoft>Windows>WindowsUpdate>AU. Modify the UseWUServer value data to "0". After that, open Services (as Admin) and restart the Windows Update Service. This will reset Windows Update and download and install all of the current updates. Also, you can use the link below to download the 1803 version from the Microsoft site using Windows 10 Update Assistant which also works for us.

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

      Was this post helpful? thumb_up thumb_down

    • I didn't bother to read all of the other replies, so I apologize if this was already mentioned.  Try uninstalling KB4338825 and then run the upgrade again.  In fact, you might want to attempt to uninstall each of the most recent round of OS updates (not Office updates).

      Was this post helpful? thumb_up thumb_down

    • I have run into this issue, for me the only solution is to "reset" windows, the option to reset but keep your data is the option I used. I backed up my laptop, reset Windows, I then UPGRADED windows to 1803, then reinstalled my applications. I also discovered some of my apps no longer supported Windows 10, and had to purchase upgrades for those. Apparently 1803 is sort of a MAJOR change. So don't panic when drivers and apps don't work, download the latest versions and reinstall them. Key part is RESET with keeping your data, otherwise you blow out the whole thing, and if your like me, your life personal and professional life is stored on your laptop. MAKE SURE YOU HAVE A GOOD BACKUP before doing ANYTHING! :)

      1 found this helpful thumb_up thumb_down

    • I was having the same issue, I just downloaded and run this script (As administrator)

      https://gallery.technet.microsoft.com/scriptcenter/Reset-Windows-Update-Agent-d824badc

      It basically reset all the Windows Update services and delete all corrupted updates to start fresh.

      After I run it the updated worked perfectly.

      Was this post helpful? thumb_up thumb_down

    • Have you tried taking it off the domain and installing the update?

      Was this post helpful? thumb_up thumb_down

    • I had a similar issue with a Windows 10 PC. I tried just about everything, but in the end I had to end up doing a repair install from a bootable Windows 10 USB stick. After I did that I was able to run the update that wouldn't install properly.

      1 found this helpful thumb_up thumb_down

    • Yeah I've had my fair share of 1803 issues as well... Some of them were solved by running windows update troubleshooter, some others with the update assistant, while some others I had to create a full installation media and do an update manually. For the latter, make sure you do it without applying updates during installation.

      Was this post helpful? thumb_up thumb_down

    • We had to do this too... with all of our machines. They wouldn't take either 1709 or 1803 updates while joined to the domain but updated without issue as soon as they were put into a workgroup. After they were updated we put them back on the domain and further updates were fine.

      Was this post helpful? thumb_up thumb_down

    • I have only scanned the replies, so may have missed something, in which case I apologise. However, I had one hell of a problem upgrading to 1803 from anything with volume licence media - this transpired to be a dodgy ISO from Microsoft. I'm unsure if it was the same error but it was something similar. New installs were fine.

      I think the upgrade was cached somewhere (may not have been SoftwareDistribution) so if this is an upgrade from prior to Microsoft fixing their stuff, a dodgy cached copy may be hanging around.

      I can't give any more info at the moment as I should have left the office a while back, but thought I'd quickly note this in case it rang any bells for anyone else

      1 found this helpful thumb_up thumb_down

    • If you clear or change the name of the Software Distribution folder, make sure you stop BITS and WUAUSERV prior and then restart after.

      1 found this helpful thumb_up thumb_down

    Read these next...

    • Snap! KB5020282, Patch Tuesday, Android leaking traffic on VPN, Podcast.ai, etc.

      Snap! KB5020282, Patch Tuesday, Android leaking traffic on VPN, Podcast.ai, etc.

      Spiceworks Originals

      Your daily dose of tech news, in brief. After leaving Apple in 1985, Steve Jobs founded a new company called NeXT, Inc. which unveiled its first product, the NeXT Computer, at a gala event on October 12, 1988. While not a commercial success, the Ne...

    • Prevent user from login to servers

      Prevent user from login to servers

      Windows

      I have one user in particular that loves to logon to the server to run reports he is not a member of any admin groups he is only a users. Is it posible to enforce a way where hi is only allow To log in to one computer only, let's say, his workstation.

    • Video conference set up advice?

      Video conference set up advice?

      Collaboration

      I take care of the computer network for a small business that has 2 locations.5 years ago they wanted a video conference system.  I knew a little about that but they went with the guy that put in their camera system.He put in a big screen TV, an Intel NUC...

    • Spark! Pro series - 12th October 2022

      Spark! Pro series - 12th October 2022

      Spiceworks Originals

      Today in History: 1979 Douglas Adam's Hitchhiker's Guide to the Galaxy Hits the BookstoresThe Hitchhiker's Guide to the Galaxy, the first book in the highly popular series of comic science fiction novels by British writer Douglas Adams. The saga mocks mod...

    • HDD Amber LED Flashing -HPE PROLIANT ML350 GEN9

      HDD Amber LED Flashing -HPE PROLIANT ML350 GEN9

      Hardware

      Hello Mate,I have one HDD that is flasing amber for our HPE PROLIANT ML350 GEN9. can i just change the HDD is it will be okay? We have windows server 2008 R2 as software.

    nybergcarceses.blogspot.com

    Source: https://community.spiceworks.com/topic/2154834-windows-10-update-1709-to-1803

    0 Response to "Windows 10 Already Upgraded to 1703 Continues to Download"

    Post a Comment

    Iklan Atas Artikel

    Iklan Tengah Artikel 1

    Iklan Tengah Artikel 2

    Iklan Bawah Artikel