Windows 10 1703 Update Failed
If you look up my threads, you'll find that last winter going from 1511 to a properly working 1607 proved impossible after seven tries, so I cleared the system SSD, disconnected all the other HDD/SSD's and did a clean reinstall. Well, same thing is happening with 1611 to 1703. Windows is now daily trying prompting me to make the update, which I'd delayed, and now won't even complete the most recent 1607 cumulative updates unless I allow 1703 to come along for the ride. 1703 crashes (computer freezes) at 25% during 'working on updates' every time, even with MBAM turned off and disabled in Autoruns. The only good news is that a manual shutdown and reboot brings back 1607 intact. I'm neither in the mood nor see the need for another clean install. What the heck could be going on this??Win 10 Pro x64 desktopi7-4790K.
Hi, you may know that here:in the yellow section there is an outline of how you can explore the logsand in 'Here's how' suggestions that may help.Please post any error message you receive.Hi, best to eliminate elementary issues - please try some basic checks.1. Download and run Hard Disk Sentinel (trial) and post a screenshot of its GUITo post a screenshot please use the Insert Image icon above your post to the left of the video icon2. If ok:From an admin command promptWindows key + X, click command prompt (admin)chkdsk C: /FYour PC will need to restart.Post back the result, which you can get after a restart as follows:ororMake sure the result is clear or fixed- else do not proceed.3. Separate downloading the iso and the update and installation process.Download it manually:When you have that you can use it repeatedly, and you also have a useful bootable tool for certain repairs if you create a DVD or bootable USB drive.4. Before you try upgrading again - which is a risk - please create a disk image of what you have now. (We strongly urge people to routinely use disk imaging- so many advantages, including potentially reducing the need to clean install). Macrium reflect (free) + its boot medium + external storage for image sets.If things go wrong, you can get back to where you were fairly readily.(Disk imaging helps even if your disk fails or your PC is unbootable e.g.
And also creates a full backup)5. When upgrading:- disable your AV, disconnect any unnecessary peripherals; also see 'Here's How' in the tutorial below.What went wrong? See:- & see the yellow Tips sectionThen see this where many error numbers and messages are listed:Please also post a screenshot of your partitions: Minitool Partition Wizard is good for this - please make sure all text in columns is fully displayed.And see. Look it, thanks for the list but the vast majority of what you posted has been covered (Win 10 Mgr) or, if I'm not mistaken, is not particularly relevant, given the same kind of problem going from 1511 to 1607, when I jumped through all those hoops and it didn't do any good, hence starting over with a clean reinstall.
Chkdsk is clean as usual, as is sfc /scannow. HD Sentinal screenshot is attached.
The Windows 10 April 2018 Update is almost here. For systems that see a “Windows 10 is no longer supported on this PC” error while trying to. “Windows 10 version 1511, 1607, 1703 and 1709 will continue to receive monthly servicing. Once you’ve upgraded to Windows 10 version 1703 with the Creators Update, you’ll notice some major changes to the ways you can configure software updates. Some of those changes are welcome.
That's clean. There are no error messages during the update attempts, just a computer freeze (though I didn't go back and check Event Viewer, if anything would be there). Creating media tools and all that is all fine and dandy - how many times have I done those! Cortex start failed please try again video. - without a way through the roadblock. And last time we were unable to find it.At this point, I can think of only two things to try:- In-place repair install - but would that bring in 1703 or just stay with 1607?- Turn off all A/V, disconnect all other drives and peripherals and see if the update goes through (not that I want or need it). An annoyance to be sure, one that I'd like to avoid.- other - am I missing something? (your tutorial, etc., links are for upgrading to Win 10 from an earlier version.
Not clear how they apply here). A couple of things to bear in mind- some hardware configs are incompatible with the Creator's build e.g. Broadcom devices.If the upgrade failure is hardware related, an in-place upgrade repair install won't help, for example, as you know.Analysis requires looking at the logs. Have you done that?
The same log files apply to any upgrade.What was your error message?Please also post a screenshot of your partitions: Minitool Partition Wizard is good for this - please make sure all text in columns is fully displayed. I ran the update from Windows Update to see if we could spot the problem. Prior to that, I shut down MBAM, got rid of its entries in Autoruns and rebooted. Looking at Event Viewer, from the time Update finished configuring the update and restarted the computer, until the time I restarted it after Update crashed while 'working on updates' (25% again), no category in Event Viewer shows any entries, none at all. Anywhere else to look?OTOH, it did finish the cumulative updates for 1607.Follow up: Uninstalled MBAM and tried an in-place repair install using the latest download from a USB stick. Same result: freeze crash at 25% working on updates. Again, restored 1607 and nothing in Event Viewer.
Btw, when it crashes, the SSD light goes full and holds, then maybe 10 seconds later the dotted circle stops and partially falls apart. See attached files from last try Thursday afternoon (setup from USB stick). The setuperr.log file ends before 'working on updates' starts.
The last error code refers to the software distribution folder, which I've deleted. The setupact.log file ends well before the last try started, so is not included.
Nothing relevant in event logs. Not sure the miglog should be posted, but here it is.I don't have a broadcom controller. This is an i7-4790K cpu on an ASRock Extreme6 mobo. Not an old computer.Will give offline and w/o updates a try Friday.
I've just noticed you have a number of Reserved partitions on the other disks. (The rest of the text is lost).Disks 3,5,6.This takes me back to the idea of disconnecting the other disks. Crude, but definitive.Also check your system boots ok when that's done.Suggest you try that first, and attempt the upgrade without updates.Otherwise: thanks, so what you can do is try searches on any part of the logs, as you will see they are not, put politely, immediately informative. That goes for many of the responses to requests for help with these too, unfortunately.Take any sections of the text and error numbers and see what you can find.Did I mention the setupact.log?It's also in what I posted above about logs.In any further attempt you make to upgrade, think how to make the environment- hardware and software- as simple as possible. You will read comments such as:The most likely cause of this error is an incompatible driver or hardware defect critical for booting the intermediary environment necessary to perform upgrade actions.
Some of the identified drivers that are known to cause this error are listed here and are the first steps you can try to resolve the issue:. Make sure you are not running any drive-encryption software. If so, you must decrypt your drive before updating. Check for and uninstall any desktop utilities you may have running. For example, uninstalling IOBit or Intel Desktop Utilities (including Extreme Tuning software, but excluding Managed Engine) has been observed to resolve this issue. I suggest you to update the graphics card before proceeding to upgrade to the latest build. Please remove any connected USB devices (except the keyboard and mouse) and then try the upgrade.
Try disabling or uninstalling your antivirus software and see if the upgrade will succeed. Problems have been observed updating to Windows 8.1 if ESET or AVAST are installed.
When the installation of Windows 10 v1803 update failed, the users faces one of the following symptoms on their systems:Symptom No1: When the download of Windows 10 April 2018 v1803 update is completed, Windows restarts to install update. But, after the system restart, the system stuck during the update installation or at Windows Logo and the only method to get the PC back, is to force shutdown the machine using the Power switch.Symptom No2: During the installation of the v1803 update on Windows 10, the system suddenly restarts and starts to revert changes and goes to the previous Windows 10 version (v1709). When the previous version is restored, the system starts to download again the latest update for Windows 10 v1803, but the installation of the update, always fails with the same symptoms or gives the error 0xc1900101. How to fix: Feature update to Windows 10, version 1803 Failed to install.Suggestions: Before proceeding to update your system:1. Completely uninstall any 3rd party antivirus or security program from your system, before installing the update.2.
Disconnect any USB connected devices that you don't need. USB Wireless Mouse or Keyboard Receiver, USB Wireless Network Card, etc.).3. If you have enabled the device encryption on your system (, ), then proceed and decrypt the drive C: before installing the update.4. Be patientthe update takes a few hours to download and install.5.
Before applying the methods mentioned below, try the following:1. Run the 'Windows Update Troubleshooter' from Settings Update & Security Troubleshoot Windows Update, OR – better – download and run the.2. Download and install the latest3. Try to install the Update.Method 1.
Windows 10 1703 Update Failed Error
Force Windows 10 to Download the Update v1803 from Scratch. Delete the Windows Update folder.The Windows Update folder (C:WindowsSoftwareDistribution), is the location where Windows stores the new updates after downloading them. In many cases, the 'SoftwareDistribution' folder's contents become corrupted and cause problems during downloading or installing updates. At these cases all these problems can be easily bypassed if you delete the 'SoftwareDistribution' folder and its contents in order to force Windows to re-download the update(s).To delete the Windows Update folder:1. Simultaneously press the Win + R keys to open the run command box.2.
Type the following command and press OK. services.msc.
From the list of services, at the right pane locate the Windows Update service.4. Right click on 'Windows Update' service and choose Stop. Close 'Services' window. Note: If you cannot stop the Windows Update service, then:a. Double click on it to open its Properties.b. Set the Startup type to Disabled and click OK.c. Restart your computer.d.
After restart, continue below.6. Open Windows Explorer and navigate to C:Windows folder.7.
Locate and then Delete the SoftwareDistribution folder. If you cannot delete the folder with error 'Folder in use – try again', then restart Windows in 'Safe Mode' and repeat the procedure.2. If you have disabled the Windows Update service (Startup type = Disabled), then go to services and set the Startup type to Automatic.8. Restart your computer. Download and try to install the Update v1803.1.
After the restart, go to Start Settings Update & Security.2. Click Check for updates.3. Finally let Windows to download and install the update again. Download & Install the Windows 10 April 2018 v1803 Update Manually.The second method, to resolve the issues while downloading or installing the Windows 10 April 2018 update 1803, is to download and install the update using the 'Windows Update Assistant': To do that:1. Follow the instructions at Step-1 from Method-2 above and delete the 'SoftwareDistribution' folder.2. Navigate to and click the Update now button.3. When asked, click to Run the 'Windows10Upgrade9252.exe' file to start the installation immediately, or click the Save button to run the installer later.4.
Finally click the Update Now button and follow the on screen prompts to install the Update. FIX Windows corruption errors with DISM & SFC tools.1. Open command prompt as administrator. To do that:1. In the Search box type: cmd or command prompt2. Right click on the command prompt (result) and select Run as Administrator.2. At the command prompt window, type the following command & press Enter:.
Dism.exe /Online /Cleanup-Image /Restorehealth3. Be patient until DISM repairs component store. When the operation is completed, (you should be informed that the component store corruption was repaired), give this command and press Enter:.
SFC /SCANNOW4. When SFC scan is completed, restart your computer.5. Try to update your system again.
Install Windows 10 v1803 Update with an in-place Upgrade.Another method that usually works, to fix Windows 10 update problems, is to perform a Windows 10 Repair-Upgrade, by using the Media Creation tool to create an ISO or USB Windows 10 install media. For that task follow the detailed instructions on this article:That's it! Which method worked for you?Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others. I 've had the same issues, and after many attempts and trying most suggestions I 've found online such as uninstall hyper v, remove antivirus, run windows update troubleshooter changing bios settings for virtualisation, and clearing windowssoftwaredistribution folder, fixing Windows corruption errors with DISM & SFC tools and restarting bits and windows installer and nothing seemed to do the trick. Until I thought to try decrypting the C drive i had encrypted with VeraCrypt and bingo this fixed it for me.Omer LandryMar 02, 2019 @20:04:11.
I now give up!!!!!I tried all above and nothing works.I think that Micrsoft has coming to be a real problem to them selves.All updates are so big nowadays so the risk that something happens is now more than 50%.You are lucky if you get away with a clean update. You are now sitting with 120 hart RPM when ever an update is ongoing.I just wasted Saturday and Sunday in trying EVERYTHING!!!!!!Now i have to admit that I have to start al over again from scratch with a factoryreset.I hate Windows 10.JonJan 04, 2019 @02:41:14. Seems like you are going through what was. Until today that is. Check your bios. Under the chipset tab look for something called Virtualization (something). May also be called VT-D.
If you see that setting disable it then save and exit. Try the update again. Note that I am using an Intel chip, but I believe AMD has a similar setting with the term Virtualization.Also, I'm on an older motherboard and chip. If you have a newer system this may be irrelevant.
My specs below:OS Name Microsoft Windows 10 ProSystem Type x64-based PCProcessorIntel(R) Core(TM) i7 CPU 930 @ 2.80GHzBaseBoard Manufacturer ASUSTeK Computer INC.BaseBoard Product P6T SE.Greg SmithJan 04, 2019 @21:12:46. I had a big problem with it getting stuck at reboot.I followed step Method 3 (the previous tips did not work) and I also used msconfig to disable every startup service which was not Microsoft. I also deleted logitech software and some residual anti-virus.This computer is a dual boot Linux/Windows computer, and because it was getting stuck at Windows boot, I thought it may be due to dual boot, but it wasn't. I can tell you that Windows updating is a lot worse than linux these days.
This was a bad experience.Thank you so very much for the tips.CharlesMay 28, 2018 @17:08:12. Have the issue of 1803 install/fail/retry over and over. Using the abovestep (any) won't work on my PC as Windows Update service properties shows it running and all is grayed out. (Yes I'm Admin)3.Double click to launch Windows Update service's properties.4. Set the Startup Type to Disabled and click OK.Doesn't work because everything in is grayed out!I don't remember for sure, but I had a client last month whose PC had been failing on 1709 since it's release due to out of memory issues and these same steps were called for. I ended up creating a boot media with the latest patches incorporated and doing the reinstall Windows 10. I wasted so much time trying so many other ways until I bit the bullet and did the reinstall.What I don't understand is if MS pulled 1803, why is Win 10 Update downloading it (a week ago).JohanMMay 10, 2018 @09:59:36.