Right-click on it and click Stop on the context menu. Open C: Windows SoftwareDistribution and delete all contents there. Restart Windows Update service. Right-click on Windows Update service and click Start. Download the updates again. Have you ever encountered a similar problem while trying to get the new Windows 10 update? Don't worry! In reply to Dalvin ramos candanedo's post on March 22, Glad this guide was helpful. Sumit Volunteer Moderator Article Author.
I will redirect people to this when any similar issues are reported by the users. In reply to Sumit Volunteer Moderator 's post on March 23, Unfortunately, this didn't work for me.
Stage 3 started checking for updates, on my computer, and ran for 12 hours before I finally decided to kill the process. I have been working on this problem for weeks, trying the above and others Fixit,sfc and various KBxxxx. Every KBxxxxxx. I need a more aggressive fix. In reply to EdwardMoxey's post on March 26, If your updates are stuck in the background while you still have access to Windows, you can restart as normal; if they're stuck before or after the OS loads, you're going to have to hold down the power button and do a hard reset.
This can cause issues itself, so make sure your updates definitely aren't progressing at all. 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.
But I observed that after a reboot, the update which got stuck would then install successfully. So I grinded my way through the updates, installing two or three at a time then rebooting when I saw the window I described above for more than 20 seconds with no progress. Some of them popped up a message like "this update is not required for your computer", so I just deleted those without installing. When I finished installing all or so updates, I tried running Windows Update again.
I left it for a bit, then went to shut the computer down in disgust. And the little yellow Windows Update shield appeared on the shutdown button! I let it install the 7 or so updates, then powered it back up. I left it a while, then once again the little yellow windows update shield appeared on the shutdown button!
This time there were 50 updates. I'm not arrogant enough to say that this will fix your problem. All I'm saying is that this fixed your problem for me. Best of luck! I solved the problem in the following way as suggested here :.
Stop the Windows Update and Application Experience services if they don't stop, disable them and then reboot. Simple solution: Open Windows Update, go to change settings, make sure it's set to install updates automatically, change the Install new updates time to the next hour as opposed to the Set the computer to never sleep when plugged in.
It may take up to two hours for the updates to start, so be patient. Change the power setting to put the computer to sleep to never you can change it back when updates are successful. Recently I restored an -I think- notebook recovering it to its initial system image, a 64bit version of Windows 7 without SP1. I uninstalled some craps coming with the notebook and installed some basic purpose software like 7zip, VLC, an antivirus, etc.
I made the update to SP1 appeared after some reboot among Windows Update list after the very first ones I had installed and returned the PC to the owner. After a week or so, the person who asked me for help told me he noticed that every time he checked for windows updates the process went on forever even waiting for long time for the task to complete. At first I thought of malware despite the person insisted it was not possible and that it happened since the beginning, anyway I decided to restore the PC again to its original system image just to be sure.
I made the same things I did the first time but, instead of returning the PC immediately, I decided to keep it for a while using it just to surf the web a little, watch some videos and listen to music in spare time Meantime I launched Windows Update to search for updates and, indeed, I noticed that the process went on for very long time never finding anything nor stopping and coming to an end, just as the owner had told me.
I tried solving the problem following almost every reply to this question, and the duplicate one here on SuperUser without solving. I tried several of the fixes listed on this Microsoft support thread and still nothing worked. Anyway, since I saw Windows Updates worked at the beginning, I decided to restore the PC to its original system image again to try to install the updates one by one trying to understand WHEN and hopefully even why the problem manifested itself I remember I uninstalled KB update too, but I don't think that's really necessary.
There are several different issues with Windows Update, which, superficially, all sound the same. My Windows 7 VM was in just this state. By right-clicking svchost. I tried turning of IPV6, something suggested among the answers which I thought I'd already done on all machines after other issues but it made no difference in this case.
I was loth to start picking and choosing KB hotfixes and updates, when there are a number of similar issues with Windows Update; I'd much prefer it to apply all the updates itself, in the right order, if there's a way to get it in a state where it will do that. The last one had completed the previous day, over 24hrs ago. Turning then to the question of Hyper-V, I looked and found where you can configure the number of processors for a VM.
The setting is greyed out when the VM is running, so you must shut it down to change the setting: I increased the number of processors from 1 to 2 and saw an immediate change: the VM now actually seemed to be doing something. Both CPU and memory usage rose and fell constantly. I shut it down and increased the number of processors again, from 2 to 4, and saw a corresponding increase in the effects: a great deal of continuing activity in Task Manager, different in each of the 4 processors, and again, an increase in the amount of memory it could utilize, still rising and falling but now approaching the full 4G allocated.
It seemed to be tearing through the updates now. To recap, there are a number of different problems that can cause Windows Update to hang or run slowly, and Microsoft have published a variety of hotfixes and updates in this general area.
So any time this comes up, it's quite likey there's more than one contributing factor. In any given case, upping the number of Hyper-V processors configured may or may not be the complete answer, but there's no doubt that doing so brings a dramatic improvement in the machine's ability to utilize both CPU and RAM.
You can use this script. Run it As Administrator, use option 2 and 3, and when finished restart the PC. I had the same issue with an older Win7 laptop I hadn't booted in a year.
After trying the above solution s , especially installing KB and KB, I finally relented and used the super-duper-fixit-all patch on Microsoft's "answers" site. This was the only thing that solved the problem for me, after hours and hours of searching and testing. There are various reasons this can happen. However I have lately found that this happens on every fresh windows 7 install, where it didn't used to. Windows 7 performs a silent update to windows update component the first time it gets an internet connection.
The current version of this silent update as of is the one causing the problems. This update is very badly designed and will easily break your windows update component if while it is installing you open the "Windows Update" program, or internet explorer, or install anything, or several other things. Even if the update goes without a hitch, there is also a secondary and known issue where there are just too many old updates clogging up windows update.
None of the solutions listed here work for issue 1. The troubleshooter will find a bunch of problems that it claims it fixed, but it didn't. Every time you run it you will get more problems listed as fixed with no actual solution.
As for issue 2, that one just requires you to manually install some specific updates which also isn't mentioned here.
0コメント