Sometimes you'll just get a message telling you to try the update again at a different time. If you click 'Advanced options' and then 'View your update history', you can see recently installed updates that were successful, and uninstall some or all of them — again, this can be a handy troubleshooting option. Windows 10 has actually streamlined the update process, so you should be seeing fewer errors. Microsoft feels your pain: it knows the update process can cause problems every now and again, which is why it's developed a troubleshooter program specifically for it — search the old Control Panel for "troubleshooting", then select 'Fix problems with Windows Update' from the list on-screen.
The link should be available in Windows 7 and 8 too, but if not you can get at it on the web as well. That said, if you haven't yet upgraded to Microsoft's latest and greatest operating system then it's probably still worth your while , as it's more than likely to solve your update problems at the same time.
Safe Mode is like a restart with extras — only the very basic apps and code that Windows needs to run are loaded into memory, so there's even less chance of a rogue, damaged file interfering with the update. In Windows 10, hold down the Shift key then choose Power and Restart from the Windows sign-in screen. On the next screen you see pick Troubleshoot, Advanced Options, Startup Settings and Restart, and you should then see the Safe Mode option appear: try running through the update process again if you can.
A quick search online will give you Safe Mode instructions for older versions of Windows. System Restore has been helpful for solving Windows problems for many a year now, but it happens to be quite well hidden in Windows Go through the wizard, then choose 'Show more restore points' to see all your available options.
Pick a time and date, then complete the wizard to go back to how Windows was configured at that point and hopefully solve your update issues at the same time. The process doesn't affect your personal files or programs, but it may not be available to you depending on how Windows was originally set up.
If Windows' own troubleshooter doesn't work see step 4 then you can try and carry out the same process yourself manually: stopping the Windows Update service, deleting the temporary files it's created, then starting Windows Update again.
Note that in Safe mode, wuauserv reported that it can't be stopped because it was not started. Although I did try to restart in Safe Mode with Networking, that option has not worked on any computer with Win 8, 8. Details required : characters remaining Cancel Submit 2 people found this reply helpful. Seriously, Windows 10 clean install, 3 days old and its already hung!
This is a bug and should have been picked up in rudimentary testing. The workaround - Start in safe mode, restart several services, delete a load of data files and restart the PC several times. You have to be kidding?! Theres a reason the fruit is getting so many customers. Thank you for replying. In case, if you need any assistance you may always post your questions along with your valuable suggestions in this forum. Details required : characters remaining Cancel Submit.
The recommended sequence worked for me, but not smoothly. I didn't learn until later the other methods to enter Safe Mode. The first time, wuauserv wouldn't stop. Various other steps worked, or didn't work, maybe depending on timing. For example, when I tried to rename Catroot2, I got "Access is denied. Once it was stopped, the rename worked.
The last command in the sequence, "net start msiserver" failed, eventually saying something like "the process didn't respond. But then the "net start" command worked. Go figure. So, Microsoft Update is working again. Details required : characters remaining Cancel Submit 3 people found this reply helpful. Choose where you want to search below Search Search the Community.
Search the community and support articles Windows Windows 10 Search Community member. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
I have the same question Will see. Net with SCCM after the gold image is installed. I guess I could add Office updates to O source files to speed it up a bit. That will be the plan if MS won't be able to fix the issue as promised. I noticed something in my environment. In fact, the client starts downloading updates SoftwareDistribution folder gets some files , but after a few minutes, the application svchost.
And guess what I'll have to automate it now by adding the reg key in a task sequence. You have to add the registry key. I made the mistake in first thinking "I already set it with GP on the server" but forgot that the client for the reference image is not yet in the domain and that the policy therefore is not applied. Also this solution applies to Windows machines that will not download from a WSUS 3 SP2 based on Windows Server yes I know that Server is old and unsupported but this is not something to discuss now.
You can download any of the two from Microsoft's Update Catalog. Office Office Exchange Server. Not an IT pro? Internet Explorer TechCenter. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums.
Answered by:. Archived Forums. Windows 10 Installation, Setup, and Deployment. Sign in to vote. Hi Basically my question is in header. Wednesday, August 3, AM. Hi, I added the last update KB as a package in the task sequence.
Wednesday, August 3, PM. Thursday, August 4, AM. I have ran into the same issue. It generally happens during the download of Office updates. Also seeing this behavior in 32bit and 64bit builds. Package it stops on varies. Richard P. Would you mind detailing step-by-step what you did? Dear Sven, Glad to hear this issue has been solved. Friday, August 5, AM. Monday, August 8, PM. Please unmark my comment an answer. My test machines claim they are up to date, WSUS claims they still have a number of updates outstanding.
Tuesday, August 9, PM. Still working workaround is to inject update directly into image like via DISM. Wednesday, August 10, AM. This does not explain why my update stalls forever in deployment task. Here's a feedback about this issue. Perhaps some upvotes are in order. Monday, August 15, PM. Other than the title, what do you consider to be horrible? Makes me nervous what will get rolled out as a build tomorrow for machines Richard P. I'm still seeing the issue client stuck on "Downloading" updates despite having pre-installed KB Tuesday, August 16, PM.
Thursday, August 18, AM. These settings resolve my problems: 1. Friday, August 19, AM. Hi, tried that but not a solution in my environment :. Friday, August 19, PM. Installing KB via MSU will fix the issue but only until a LPK is installed since installing a LPK will require to be reinstalled which will fail or better stall to download, eventually it may download because lots of WU related services are crashing constantly and trying over and over after a crash.
In addition, WindowsUpdate. I have two cases open with premier support, the WindowsUpdate. Any or build has no issues. Issues has been confirmed on fresh, standalone install of WSUS on R2 with clean, manual install of Enterprise.
FAIL is my only comment. Hi dmatth! Thanks for your feedback, just keep us posted! Monday, August 22, AM. Tested with computer in domain and not in a domain, same problem.
0コメント