Looking for:
Windows 10 download taking forever - Microsoft Community.Research shows Windows updates can take six hours to complete | Computerworld |
- Solved: Windows 10 update stuck at checking for updates
Windows updates taking forever to download free.Is Your Windows Update Taking Forever? Get Methods Now! [MiniTool Tips]
Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff microsoft. There is something wrong here. I have always had my servers apply updates at am it gives backups a chance to finish and still will complete the reboots and come back online before am With Server , I am forced to use gpedit to control the different days of the week I cannot simply use a maintenance window of for all of my servers to reboot at the same time on the same day , but I am now having issues with Server We always tell our servers to reboot for updates when needed so they do not hang out and wait for a user to reconnect to a session and then that user logs out of a session in the middle of a business day, then it decides it can finally reboot.
I have no issues with r2, r2, but I do with I've done 3 servers now. All updates very sluggish. Including ones right after a clean installation of the OS. Latest example Then started applying it at am. Still running at am. Can't really tell because the update process gives us really no useful information on estimated time. I've been working on Microsoft servers since LAN Man and I've gotta say that this is probably the worst mess for updating I've ever experienced.
I've just downloaded a latest Windows Server Standard Version And another "same here". No 3rd party AV solution to blame. Disappointed to see this has been a known problem for some time with no official word from Microsoft on a resolution.
Time for a slashdot article maybe? The more servers we deploy the more I'm feeling my monthly updates taking much longer and becoming more painful. I had 3 x R2 servers this morning took 20 mins for the May updates. Up at the top. Not sure if it does help as the other thread I linked at the top has 11 votes. Same thing. Very slow when installing updates We experienced similar issues after upgrading to Windows Domain Controllers.
Windows updates on our DCs were taking hours to perform the monthly rollup when pushing them manually. The DCs on the other hand were receiving this update. What we witness when checking our update status the following was occurring:.
This step during the update process was taking hours. This update was being pushed to all DCs. THe DCs running on Acropolis did not experience the same slowness when installing this update. I am still investigating why that is. I hope this helps others that may be experiencing similar issues. This is a real issue with Server It's not individual systems.
This issue occurs on every Server host and VM that I manage. The update timescale is just way too long. It's got to the point where there is not enough time to backup all of our VM's, then update them all, in a night. Who wants to spend all night nursing a HV host through updates anyway.
After disabling Windows Defender before updating updates take about one and a half hour instead of almost four hours. Just to share my experience: I updated 4 physical nodes cluster R2 with last Tuesday patch in about two hours. Now I'm updating a 4 nodes physical cluster and the first node is still updating for over two hours All 6 six servers download and install the June updates in minutes, and minutes to reboot.
The two servers failed repeatedly when attempting to even check for updates. So I rebooted both servers, was finally able to check for updates from Microsoft. Then it takes about 30 minutes to download and install. Then I actually timed the first one and it took 34 minutes to reboot back to the logon screen.
This is really, really bad. Currently waiting about an hour or more on multiple VMs using "sconfig" to install updates on CPU fluctuates and is never really idle, and definitely not being maxed out.
Why the hell does it take so long to do updates? Has anyone ever put in a ticket with Microsoft so we know they are at least aware of the problem? I've been on a few forums and tons of people are having this problem. Out of about 8 VMs, I think I had one install at 5am on it's own Some updates installed on one of my Terminal Servers running Server this morning, kicking out all the users logged on that particular server Rebooted on the "preparing updates" screen. Stayed there for 25 minutes and then rebooted again.
Came back to the "installing updates" screen for another 30 minutes and rebooted again! Came back again to the "installing updates for another 15 minutes and finally came back online! I have some servers still running Server and those are much faster to update.
I greatly regret throwing away my Citrix farm infrastructure running on Server for these Windows Server terminal servers. Lot of issues with processor and RAM ressources, freezes etc. Microsoft should look at the English definition of the word "upgrade" because moving from to was definitely not an upgrade in many aspects. We can clearly live and experience what can a monopolistic empire can do to customer care and service Same issues here: server takes forever to install updates, seems to be stuck already in "Preparing windows" after clicking on "restart" to install the update.
KB from takes 56,57 minutes from clicking on "check for updates" until OS is rebooted. It makes no difference, if updates are installed directly via Windows Update or manually Is it possilble to get some kind of useful Information from Microsoft concerning slow Server updates? I can confirm as well. Windows updates are running on a single logical processor of the 24 available 2x Xeon E We see this on our other servers with completely different hardware as well. Same exact behavior. Only 1 logical of the 16 is engaged Xeon E Neither of these systems is doing anything but installing Windows Updates.
No other loads. Therefore, at least from my vantage point, Windows Updates on Server would be much faster if they used more than one logical processor. Install KB first!!! Microsoft strongly recommends you install the latest servicing stack update SSU for your operating system before installing the latest cumulative update LCU. SSUs improve the reliability of the update process to mitigate potential issues while installing the LCU and applying Microsoft security fixes.
For more information, see Servicing stack updates. Can you see why people are frustrated? Standard corporate blame game on the little guy with no say in what they have to provide? We are NOT thick. We have been doing this for longer than some of your own employees, so give us some credit. Small businesses and schools relying on your products, because our leaders don't know any better and think Microsoft are the only solution.
Downtime is not an option for us, we have no resilient server farm. This month with KB we have seen a couple of failures on a couple of our servers. To me it seems like an issue with the trustedinstaller perhaps timing out while shutting down, we have to manually download the patch and it finally went thru on some of these. Are there any hotfixes for these issues on Windows ? I've finally given up and just disabled Windows Update and the Module installer service.
On is 'just' a DC with nothing else going on. But be carefull with Server , there are still some things that need to be fixed. Total Patch Time CU without. I have dealt this feedback and can provide you that update size alone is not the matter. It is in the code. If I am able to install a server in a time of 3 minutes the system cannot be powerless enough to patch anything within a reasonable time.
Just for fun we could install a second server from scratch to make the sillyness of this bug obvious. Showing this a complete clean installation should remove all doubts the issue is by design, and MSFT has fixed it in later code.
Is Your Windows Update Taking Forever? Get Methods Now!.Windows 10 Updates failing/taking a long time to download and - Microsoft Community
Most of the time, Windows Update does its job with little if any attention from us. While we might check and install updates manually from time to time, most Windows 10 computers are configured to apply important updates automatically, while older versions like Windows 7 and Windows 8 usually apply these fixes the night of Patch Tuesday. Sometimes, however, when the patch, or maybe even service pack, is being installed during shutdown or startup, the update installation gets stuck—freezes, locks up, stops, hangs, clocks, whatever you want to call it.
Windows Update is taking forever and it's clear something needs to be done. The installation of one or more Windows updates is probably stuck or frozen if you see one of the following messages persist for a long time:.
You might also see Stage 1 of 1 or Stage 1 of 3 , or a similar message prior to the second example. Sometimes Restarting is all you'll see on the screen. There might also be some wording differences depending on which version of Windows you're using. If you don't see anything at all on screen, especially if you think the updates might have been installed completely but could be the cause of whatever you're experiencing, see our How to Fix Problems Caused by Windows Updates tutorial instead.
There are several reasons why the installation or finalization of one or more Windows updates can hang. Most often, these types of problems are due to a software conflict or a preexisting issue that simply wasn't brought to light until the Windows updates started installing.
Much more rarely are they caused by a mistake on Microsoft's part regarding the update itself, but it does happen.
There's an actual issue with Windows that can cause Windows Update installations to freeze like this but it's only applicable to Windows Vista and only if SP1 hasn't yet been installed. If your computer fits that description, install Windows Vista SP1 or later to solve the problem.
Some Windows updates can take several minutes or more to configure or install, so you want to make sure the updates are truly stuck before moving on. Trying to fix a problem that doesn't really exist might just create a problem. You can tell if Windows updates are stuck if nothing happens on screen for 3 hours or more. If there's any wonder after that long, take a look at your hard drive activity light.
You'll see either no activity at all stuck or very regular but very short flashes of light not stuck. Chances are that the updates are hung before the 3-hour mark, but this is a reasonable amount of time to wait and longer than we've ever seen a Windows update take to successfully install. If so, log on as you normally would and let the updates continue to install successfully. If nothing happens most likely then move on to Step 2. Restart your computer using either the reset button or by powering it off and then back on with the power button.
Windows will start normally and finish installing the updates. If the Windows update installation is truly frozen, you have no other choice but to hard-reboot. On a tablet or laptop, removing the battery may be necessary. If you're using Windows 10 or Windows 8, and you're taken to the sign-in screen after the restart, try tapping or clicking the power icon on the bottom-right and choosing Update and Restart , if available. If you're automatically taken to the Advanced Boot Options or Startup Settings menu after restarting, choose Safe Mode and see the comments in Step 3 below.
Start Windows in Safe Mode. This special diagnostic mode of Windows only loads the minimum drivers and services that Windows absolutely needs, so if another program or service is conflicting with one of the Windows updates, the install might finish up just fine.
If the Windows updates do install successfully and you continue to Safe Mode, just restart from there to enter Windows normally. Complete a System Restore to undo the changes made so far by the incomplete installation of the Windows updates.
Since you can't access Windows normally, try doing this from Safe Mode. See the link in Step 3 if you're not sure how to start in Safe Mode. During the System Restore, be sure to choose the restore point created by Windows just prior to the update installation.
Assuming a restore point was made and System Restore is successful, your computer should be returned to the state it was in before the updates started. If this problem occurred after automatic updating, like what happens on Patch Tuesday, be sure to change Windows Update settings so this problem doesn't reoccur on its own.
Since these menus of tools are available from "outside" of Windows, you can try this even if Windows is completely unavailable. This option is not available in Windows XP.
Start your computer's "automatic" repair process. While a System Restore is a more direct way of undoing changes, in this case of a Windows update, sometimes a more comprehensive repair process is in order.
Test your computer's memory. It's possible that failing RAM could be causing the patch installations to freeze. Fortunately, memory is really easy to test. Update BIOS. An outdated BIOS isn't a common cause for this problem, but it's possible. If one or more of the updates Windows is trying to install is involved with how Windows works with your motherboard or other built-in hardware, a BIOS update could solve the issue.
Do a clean install of Windows. A clean install involves completely erasing the hard drive that Windows is installed on and then installing Windows again from scratch on that same hard drive. Obviously you don't want to do this if you don't have to, but it's a very likely fix if the steps prior to this one were unsuccessful. It might seem likely that reinstalling Windows, and then these same exact Windows updates, will cause the same problem, but that isn't usually what happens.
Since most lockup issues caused by updates by Microsoft are actually software conflicts, a clean install of Windows, followed promptly by the installation of all available updates, usually results in a perfectly working computer. If updates are stuck installing on or just after Patch Tuesday the second Tuesday of the month , see our Details on the Latest Patch Tuesday piece for more on these specific patches.
Actively scan device characteristics for identification. Use precise geolocation data. Select personalised content. Create a personalised content profile. Measure ad performance. Select basic ads. Create a personalised ads profile. Select personalised ads. Apply market research to generate audience insights.
Measure content performance. Develop and improve products. List of Partners vendors. Tim Fisher. General Manager, VP, Lifewire. He writes troubleshooting content and is the General Manager of Lifewire.
Facebook Twitter LinkedIn. Updated on August 06, Michael Barton Heine Jr. Lifewire Tech Review Board Member. Article reviewed on May 26, Tweet Share Email. In This Article. Possible Causes. Are the Updates Actually Stuck? Step by Step: Fix a Stuck Update. Extra: Still Having Issues? Was this page helpful? Thanks for letting us know! Email Address Sign up There was an error.
Please try again. You're in! Thanks for signing up. There was an error. Tell us why! More from Lifewire. Windows 10 Update Failed? Here's How to Fix That. How to Fix a Black Screen in Windows How to Fix Libmmd. How to Fix Crypt How to Change Windows Update Settings. How to Check for and Install Windows Updates.
How to Fix Msxml3. Your Privacy Rights. To change or withdraw your consent choices for Lifewire. At any time, you can update your settings through the "EU Privacy" link at the bottom of any page.
No comments:
Post a Comment