Hopefully it will work. This is way easier and less stressful than deleting the SoftwareDistribution directory from your Windows directory, which is my next suggestion. I have to say that this was a surprise. Most of the time, when I've had difficulty getting Windows Update to work, it's taken hours or days, and I've had to jump through a bunch of hoops to get it done.
If the troubleshooter doesn't work, a good first start is to simply clear away the old update files. To do this, first restart your machine in Safe Mode. It is possible to clear the Windows Update files by stopping the Windows Update service, but I've found it's just a much more reliable experience to make sure nothing's running in the background, so I go straight for Safe Mode.
From there, open File Explorer, navigate to the Windows folder, and delete the folder called SoftwareDistribution. At this point, go ahead and restart your machine and try the update again. If you disabled the Windows Update service, remember to turn it on before attempting your update.
If Windows Update is still failing, you might want to consider going to Microsoft to download the update directly. It's probably not a bad idea to bookmark the Download Windows 10 page on the Microsoft site. Go ahead and completely download the update. I'd recommend hitting Save rather than Run, so that you have the update and can reapply it if you run into any snags.
The tactic above may work if there's a recent feature update as there was in my case. Ed has a great explanation of the differences in this article.
For those, you have to go to the Microsoft Update Catalog , search using the KB number of the failed update, and download the correct standalone distribution package, then double-click to run it. If all that fails, it might be time to run the Windows System File Checker. So let's begin with that. First, open a command shell. Make sure you right-click on the Command menu and run in elevated privilege mode.
This should help clean corruption among your system components. Give it a few minutes to run. Hopefully you'll have a successful result. Hopefully, you're happily updating Windows by now. But if not, I have one more hammer left in my toolbox: repairing your Windows installation itself. Windows offers an in-place repair and upgrade as part of the installation process. To take this final step, read Ed Bott's quick tip on how to make it happen.
Finally, it's worth mentioning that sometimes Microsoft ships problematic updates. You might just need to skip that update. I know, after all that pain, right? But it happens. Here's an Ed tip on hiding problematic updates and moving on with your life. Hopefully, one of these procedures is getting you back on the way to an updated Windows. Let me know how things worked out in the TalkBacks below. A have a Dell laptop, i7, touchscreen. I have tried for nearly 9 months to get past this.
I have turned AV on and off, flushed cache, deleted download locations. I am running Kaspersky AV how about you? Did you ever get past this? The only other thing I haven't tried is a full uninstall of AV and will try that shortly.
RobGreene, had the same issues attempting to update Windows to Build 20H2. Tried everything and anything except rebuild the computer Dell Precision In the end, it was the audio drivers from Dell.
I haven't a clue why either I tried disabling it, still failed. In the end, I removed the driver, let device manager tell me it was an unknown device and then disabled it. Build 20H2 installed without issue.
Re-installed the audio driver and now I'm dealing with the infamous "popping" sound when pushing audio through the onboard speakers. Fix one thing and destroy another. Run Troubleshoter and check what message it is producing.
For my case it was showing that there was some issue in Java Runtime, I uninstalled Java and issue solved. Hi, I have issue with newest update for Windows 10, it is the version 20H2, so I tried everything to fix that problem, but nothing isn't working, so I need help with fixing that issue.
After a month or more of trying all the standard fixes I was finally able to solve my Windows Update failure problem that displayed error code 0x I am posting here in case others may benefit. It appears if you use Macrium Reflect software this may help you but I could not confirm that the problem was caused by Macrium. So whether you use Macrium or not see if this helps you. FIrst thing to do is make a backup of this entry in case anything goes wrong.
Now click on the top level WIMMount entry if you expand it you will see Instances and WIMMount sub-directories but we will not be using those and in the right side panel you should see 11 or so entries. I confirmed this entry on my two other Windows 10 PC's. Finally, check to make sure the wimmount. This is what I used to find my problem with wimmount. You just double click SetupDiag. Open the SetupDiagResults. I have used Macrium as well and did see REG entries for that.
I have been hammering on this issue monthly for longer than I care to admit. I was a hairs breadth away from a wipe and fresh install but dreading it.
You're an absolute hero! I used Macrium over a year ago and haven't been paying attention to Windows updates until EOL popped up. Then, reset Windows Update components with this script , it will completely reset the Windows Update client settings. It has been tested on Windows 7, 8, 10, and Windows Server R2.
After that, please boot computer into Clean Boot and install it manually with the following steps. Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. I tried to turn on. NET Framework, but it was unsuccessful:. I tried to run update with the Update Assistant, but it says:. This machine is very new, I installed Windows 10 H2 last december, so I'm surprising what's wrong.
I just answered to KapilArya, I didn't see your answer until now. Thanks for you answer, I wil try you suggestions. After this the update error code is the same. We haven't heard any related issue about this update package from Microsoft, and I will test the package on my side and feedback result to you. As I know, if you haven't enough space in system volume, update will roll back to previous status. Please make sure you have enough available space. If yes, please post it here. If you want to check if any suggestion for your log file, you could upload here and make sure not leak any personal data in it.
I noticed it actually related with Jan. As you know, installation failed could be caused by many reasons even it is occur on a same update package. For your issue, I would recommend to create a thread to follow up it more convenient. Sorry for deleting my duplicate reply and found your reply is also deleted automatically followed mine.
On the Home Consumer forum, there are tons of reports of this update failing to install. See the link of the forum threads sorted by me too votes filtered by the date range 14th-today. The first page is full of reports of the update failing to install.
0コメント