text: Solved: Windows 10 Update Takes Forever – Driver Easy.
  Was this reply helpful? Yes No. Sorry this didn’t help. Thanks for your feedback. I got about 20s of downloads with full speed 20Mbps and after that I get into a download loop that looks like: s of data with 0,Mbps and then a pause of 20s with no data.
  Everything looks to be OK with update service except this strange slow download pattern! During these slow update, I ran speedtest. I don’t think it’s my internet connection since from other websites and even microsoft. Choose where you want to search below Search Search the Community. Search the community and support articles Windows Windows 10 Search Community member. I’m using Windows 10 Pro and have a big problem with extremely slow download of updates.
  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 Report abuse.
  Details required :. Cancel Submit. User Independent Advisor. Once rebooted, try start again Windows Update. Probably there is some problem with the previous downloaded Update data.
  Tell me if you resolve. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. Vijay A. Verma Volunteer Moderator. Try following one by one. Skip a step which you have already tried. I would recommend that you perform a Windows 10 repair upgrade. Repair upgrade fixes all Windows errors and retains all files, applications and settings. Disclaimer – This is a non-Microsoft website.
  The page appears to be providing accurate, safe information. Sometimes, instead of boosting the performance, the Windows update might make your PC sluggish. To be honest it is more frustrating to have a slow PC than a no PC. Intentionally Windows updates will never make your PC slow. However, some times, after updating, your laptop or PC might slow down. The following are the 3 common reasons. Most computer users are familiar with Incompatible firmware or buggy updates but even experts fail to pay attention to junk or cache files.
  In the next section, you will find the easiest method to remove junk files after Windows update. After completing the update, your laptop or PC will have an enormous number of cache and junk files. Finding these cache files is near to impossible. Since these junk files are collateral of the update, just cleaning your temp folder will not do the job. Considering the complexities involved in removing these junk files we have come up with a unique tool that can optimize entire PC performance in a single go.
  The tool is Remo Optimizer, which is a holistic tool that aims to enhance the entire computer performance in 3 simple steps. Not only to clear the Junk files, but Remo Optimizer will also let you fix incompatible firmware or driver issues. You can also roll back Windows updates using the restore option. All the things considered Remo Optimiser is the only tool you need to improve the performance of your computer.
  New updates bring new features such as better visual appearances which might require advanced hardware. Insufficient hardware resources will also slow down the performance of computers.
  Considering the fact that Windows 10 is a huge advancement in visual appearance, it requires a lot of RAM and a better processor to perform well. Fortunately, you can just disable the additional visual appearance features and improve the performance of the PC. The following are the instructions on how to disable these visual features. Start-up applications are the apps that start simultaneously while booting Windows. This not only impacts the performance but also increases the boot time.
  By the way, even the start-up applications can be disabled using the Remo Optimiser tool. In some cases, your computer might be running slow due to flawed update. However defective updates are very uncommon and Windows. Windows is also proactive if there are any issues with the update. Most probably they will provide you with hotfixes to rectify the issues as soon as possible.
  Windows 10, very slow download of updates – Microsoft Community.How to Make Microsoft Download Updates Faster | Small Business –
  When the Windows 10 May Update is ready for your device, it will be available to download from the Windows Update page in Settings.
  Choose a time that works best for you to download the update. You’ll then need to restart your device and complete the installation. After that, your device will be running Windows 10, version 21H1. To check whether you’re already running the May Update, select View update history on the Windows Update settings page. Also note the following:. If updates are available, install them. If version 21H1 isn’t offered automatically through Check for updates , you can get it manually through the Update Assistant.
  If you run into problems updating your device, including problems with previous major updates, see common fixes at Troubleshoot problems updating Windows 10 , or use Fix Windows update issues to step you through the troubleshooting process.
  If you’re warned by Windows Update that you don’t have enough space on your device to install the update, see Free up space. If you experience internet connection issues while updating your device, see Fix network connection issues in Windows. If you’re still running Windows 7 or Windows 8. Get more info about Windows Update. Check for updates. Need more help? Expand your skills. Get new features first. A subscription to make the most of your time. Try one month free. Was this information helpful?
  Yes No. Any other feedback? The more you tell us, the more we can help. How can we improve? Send No thanks. Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents. Contact Support.
  Windows 10 Cumulative Updates are way too slow to download and install – Microsoft Q&A.
  Is it just me or are the server updates just slow?! I had updated all the r2 and ones in about an hour, yet the servers took the best part of a day to update and install! Not sure what “best part of day” is time-wise but probably not normal, may need to check log files and or event logs for clues.
  Regards, Dave Patrick Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff microsoft.
  The updates are now cumulative. When you install the latest update only the delta updates from previous cumulative would be applied. I don’t have problems with any of servers here both physical and virtual. Hey bubba, We know what cumulative means but the issue is that the cumulative updates are so freekin large that it takes forevere to install even on a new all flash drive server virtual or physical.
  Updates need to be made smaller so this does not happen. It does not matter if WSUS is used or not; it is the length of time it takes a cumulative update to install on Windows server that is the problem.
  Billions of dollars are spent for licensing of MS enterprise products so we deserve better. We’re experiecing the same issue on our servers. All flash or not, it is extremely slow. I’m afraid to update my new servers because the long downtime that affects our users. Brand new Domain Controllers choking for minutes before you can press the reboot-button to make it go offline I have a feeling our organization will want to behead me everytime I need to update our servers.
  Another “me too” here regarding the performance of updating Windows Server I did notice this whilst first creating templates for these machines, but brushed it off. So far it’s been running for an HOUR, and no idea how much longer left to run.
  Not sure if it’s just the fact that the cumulative update process obscures how many actual updates are being installed which, in and of itself I’m not particularly fond of..
  Updates finished installing – took about an hour and ten minutes. Clicking on restart took a further 11 minutes almost to the second to be returned to the login screen. We have also extremely slow installation for Windows Server updates. KB was taking more than 40 minutes and the reboot was minutes. Dude, of course we’re checking the windows update logs.
  If you read between the lines here, it is professionals complaining who have experience with patching other OSes and we are comparing that with the relative performance of deploying these updates. The robot that’s just sitting here saying ” For what it’s worth, I too am having serious performance problems with installing patches on freshly-built servers.
  I have the same performance problem if I install the first ones from Windows Update, and then try and deploy the next month’s via SCCM. Oh look, it had failed after half an hour, with CBS. Even with the maximum run time set to 60 min on the package, as it was when it was first deployed. The majority do succeed it’s true that this server may have a machine policy refresh problem, maybe , but after taking at least an hour. However, the time to download these mega-packages and then presumably check each component to see if it’s required is not at all efficient.
  I like the idea of having cumulative update packages so that you can deploy them to new servers and be sure that no un-superseded update that was in a deployment group from 3 years ago will be missed. But only as an option, and really, only if they’re able to install efficiently. This new Updated Policy for Windows Server is just awful. These Preparing for Install takes forever!
  I really hope that Microsoft support engineers will see this thread and forward to appropriate specialist to fix this nonsense! I would like to weigh in also. I have an environment with many hundreds of Server OS’s , , and many variants thereof, but it is only the Windows servers that seriously feel like a huge step backwards for inclusion into an enterprise environment.
  The interface is inferior for — in no way at all do the downloaded Windows Updates reflect accurately as to the true download status of the Windows Updates files in Server This new “simple” interface is a nightmare for admins like me that care about knowing simple things such as: What is the correct percentage of the file currently being downloaded?
  How large is the file, and how much space is being occupied by the download? Where is the xxMB of xxMB currently downloaded dialog at? Why in the world did the development team think it was a good idea to replace all of the working Windows Updates parameters that admins used to have access to with an “SCONFIG” console that has to be invoked via Powershell? Seriously, did you fire every single project manager and UI specialist you have?
  That’s just the tip of the iceberg. Server is buggy, flaky, and a HUGE step backwards in almost all aspects of interoperability so far even in terms of comparison to Windows Server At this point my preference remains for deploying R2 servers, because is really not ready for prime time. I should be doing real, actual work right now rather than endless troubleshooting this Server that should still be in RC stage. I completely agree. The time it takes to install updates in is unbelievable. I have HV hosts that take 30 minutes to reboot and get their guests back online after applying an update.
  That is after waiting an hour for the update to apply. It wasn’t applied the first freaking time? That leads to more downtime and lost sleep. I have to say this Slowdown with updates is incredibly inconvenient – A Hyper-v cluster that used to take a few hours to update in R2, is now taking me a whole weekend to update in The Fact that it also applies Cumulative updates one after the other is bonkers.
  Why didn’t it just apply the December CU in the first place??? Or are they not really Cumulative despite the name? Every Windows Server that we have deployed is taking over an hour to install any MS updates. This is true for new installations that have nothing on them but the Windows OS. The downloads of the MS updates is quick, installing is not.
  All other Windows OS versions we have are quick to install comparative to Windows Is there any one how have tested this with RTP? We have had and have MS support case. It is a slow process, and the full story is not revealed yet. And this is such case that is Microsoft supports weakest point spanning different support team. I can do understand it is complex, but there is quite many with the same issue, so there most be some pattern to dig in to.
  But we even see slow installation on physical servers. We now use to put 60 minutes max runtime for Windows Server cumulative in SCCM, but is also limit the maintenace windows. So it is a puzzle to get Everything to work, and for a system administrator all the hassles take away your precious time!
  Oh man. I’m another “Me Too” as these updates are crazy slow. It’s been 45 minutes and “Getting Windows Ready. Don’t Turn Off Computer” is still displaying.
  Trying to spin up a new machine to replace a failing DNS server and this is not helpful. Please reduce the update packages Microsoft. This makes it nearly impossible to get things online quickly. I have no idea where the server is in the update process or how much longer I’ll have to wait.
  Licenses are getting more expensive, servers require more resources, and updates are slower. Linux is looking like a better option to this. Please fix it. I’m stunned this still isn’t resolved going on 9 months now I installed 6 VMs spanning 3 hosts. I just rebooted after installing one of the CU’s KB on a VM and the “getting windows ready” screen and such is insane.
  On a machine that normally boots in under a minute, that was an 8 minute reboot, on top of the 30 min update install time. If it helps narrow it down, the Server Core machines take just as long even with VMs offline and they aren’t running any AV solution. It may be all in my head, but it does feel like W patch faster that way, and with less errors. I’m with everybody, I just install a R2 server from scratch with office on it and made all of the update during the time the Cumulative update hang on my server I’m so tire of this.
  So Microsoft – what poor code have you written, that takes so long to do so little? I tried to update my template image today. It’s non-domain joined vanilla install, and grabs the updates from the internet. At The system said it needed to reboot, and went to the blue screen that says not to power off. This is a esx VM on brand new Nutanix hardware. The cluster is extremely under-populated because it’s a target for DR emergencies.
  Windows update download slow free –
  I really don’t want to upgrade to if this keeps up. Just awful. Thursday, March 15, PM. Wednesday, March 21, PM. At I started checking for updates. At the system finally completed the reboot. This update process is messed up and needs to be addressed as a top priority. Tuesday, March 27, PM. Wednesday, March 28, AM. Wednesday, March 28, PM. Yup, Server is absolutely horrible with Windows Updates. We patch about 50 Win servers monthly and over half fail every time and need multiple reboots and re-checks to finally get updates installed.
  And when it does finally work even on the ones without errors , the update process takes on average about minutes depending on the month. Meanwhile, all of our and servers are patched and rebooted in less than 15 minutes with no errors. Our Windows server maintenance would take us about an hour if all we had were R2 servers.
  Instead, it takes hours because of Windows I can’t believe there isn’t more outrage about this – aside from what I see from some people within this and a few other threads scattered around the Internet. Tuesday, April 3, PM. Just chiming in to say, “Same here! Friday, April 6, AM. Wednesday, April 18, PM. Lots of complaints, and no solutions. Thank you Microsoft!
  Quite frustrating. Wednesday, May 9, PM. Edit: As I posted this, it finally shutdown. Edited by tjstechie Thursday, May 10, AM.
  Thursday, May 10, AM. Update time is getting worse with every update. Vanilla server fully up to date until the Patch Tuesday update. Update failed after spinning for over an hour. Hello MS??????? Guess I will have to open a Premiere Support case for this stupidity.
  Tuesday, May 15, PM. Sometimes reboots are solving the problem, sometimes not. I with everyone else here, updating in Server is terrible. Friday, May 18, PM. Hello everybody, this is really month by month worst! What is the solution if any????
  Sunday, May 20, AM. 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? Sunday, May 20, PM. Tuesday, May 22, PM. Server has been so bad for updates. Really slow and unpredictable The more I’m deploying the worse the monthly update process is getting. I’m also cautious to deploy any more Seems like Microsoft has gone backwards with this.
  Your killing the sleep of sysadmins. Thursday, May 24, AM. Tuesday, May 29, PM. Wednesday, May 30, PM.
  I’ve yet to try Server but as it is supported, I don’t see why it cannot at least bypass slowness that is network related.
  Hope this helps. Thursday, May 31, AM. It is sad – and annoying :- Bugsy – Denmark. Friday, June 1, AM. Kleist 0. Friday, June 1, PM. Also very very very slow in germany with Server Std. I does not thought a update-process could be slower than MS Exchange CUs – but the winner in very very slow-performance is the Server form MS. Thanks zu Microsoft for more tea-time. Tuesday, June 12, PM. Tuesday, June 19, PM. I’d also like to chime in, even though I have another thread open.
  Cumulative updates will not install automatically like it should, or even if I go through settings and kick of an update manually. The only way I get updates to come through is manually downloading and installing or going through sconfig option 6. And even then it takes over an hour to install the updates. Wednesday, June 20, PM. Mark me down as another member of the “windows isn’t very good” brigade.
  Friday, June 22, AM. Microsoft wake up, and fix it!!! Monday, June 25, PM. It’s the same here. I can only apply Updates on sundays now in non productive times. Windows Updates Need forever for downloading and installing Updates. But even after that, when trying to reboot it takes sometimes several Hours until Windows Server getting up again. Stuck at “Getting Windows Ready, don’t turn of Computer” It is completely independent whether with wsus or without.
  Also Independent from VM or hardcore Server. As I can see here, this has been an issue for over a year now. Alternatively, you are welcome to join me on Sundays and apply Updates Sunday, July 1, AM. Monday, July 2, AM.
  Everyone up vote this so it gets some attention. Monday, July 2, PM. Come on Microsoft. Tuesday, July 3, AM. Still its not great but better than it was. Wednesday, July 4, PM.
  Thursday, July 5, AM. Best of luck! Friday, July 13, PM. Another compain here Just patched the file server took 90 minutes to install. I almost quit my job for such a long down time. It’s crazy missed my reboot window by an hour because of this! Saturday, July 14, AM. Short update on this, this morning I updated a identical server with windows defender disabeld and update time was as following 20 minutes installing before reboot 22 minutes reboot until logon screen 18 minutes cleanup processing TIworker, disk cleanup This was almost 40 minutes shorter in time as first server, was willing to upload a picture but am not allowed account validation But why is tiworker process running as normal like all other processes?
  Tuesday, July 17, PM. Wednesday, July 18, AM. Robinson 1. Another frustrated Administrator. Tuesday, July 31, PM.
  So this is great that we can post a what’s the deal with here in the Microsoft TechNet forum, but how about a real answer from someone from Microsoft and then a solution. As an MSP engineer I manage updates on many servers across multiple customers with mixed MS Server versions and is the worst at every location for updates. Every takes times longer to download, install and then reboot than any other version of MS server back to So how about stop with the blow off question and answers like we are home users and actually fix it!
  Thursday, August 9, AM. Thursday, August 16, PM. Friday, August 17, AM. Agreed, Windows Update on Server is very slow, compared to R2. Friday, August 17, PM. It’s unclear if you’re talking about Defender here, but it looks like most if not all of that folder is automatically excluded via the default set of exclusions.
  Sunday, August 19, PM. Server guest in a Hyper-V environment. It’s been over an hour since I told it to shut down and update. Wednesday, August 29, PM. No I was talking about Sophos Anti Virus, sorry should have been a bit clearer. Brand new fast server and no this is not a WU vs. WSUS issue. It is a partching rollup strategy by MS which is defective and worrying for any admin that hass to sit there and watch for hours wondering if their server will come back up.
  Friday, August 31, PM. Ever use a server in the real world? MS has been very good at listening to their admins in the past so I have lots of hope. Particularity when you decide to change the UI with each release so we have to relearn how to get to everything when it used to be a breeze Win7. Every admin I know has asked for this. Thanks for listening to your customers! Best Regards, Eve Wang It seems to be getting worse.
  Same here, brand new Server , SSDs, taking forever to even start to install anything. This is terrible. Here we are Sept 1st and we still have the same exact problem with Windows Server Monthly cumulative updates.
  I have a new production server I installed last month for a client. The update trashed the server, went into repair mode and could not come out of Safe Mode.
  I had to revert a a replication for an hour while I fixed the issue and reinstalled the update. The process to me three hours of work for what should have been a simple update. Windows now sits at the update screen for hours while the server shows no progress.
  What a bunch of Microsoft BS!!! This OS is suppose to be as good or better than R2 right!? I hate this nonsense from Microsoft, fix this issue MS, Fix it! I would love to turn off updates but the new server will not let you do that! Does anyone have any ideas for this problem?
  I did notice this if anyone can help. I logged on to my Exchange server that updated with no issues same update. That tells me there is a problem with the server being able to stop this service or others. Normally, I would just open the task manager and end that service. Being on another server, I could not do that. If anyone knows how to end a service while on another machine that info might help me track down the issue on the next updates freeze. Sunday, September 2, AM. Getting really bored of seeing this.
  Sunday, September 2, PM. Tuesday, September 4, PM. Saturday, September 8, AM. It’s a ploy to get on soon.
  Think how small those updates will be, for a while, at least. Monday, September 10, AM. Similar situation here. Production service interruptions related to patching are now measured in hours instead of minutes. Given that service disruptions related to maintenance have changed so significantly and no resolution seems to be forthcoming, our customers are now actively weighing these hours-long service interruptions against the cost of higher availability solutions or moving away from Windows as the server operating system of choice.
  Thursday, September 13, PM. Friday, September 21, PM. I would really like some explanation for why is this happening. I have a bunch of Server but only the servers running web services are slow to patch and reboot last patch cycle it took nearly 2 hours to install and reboot them to a working state.
  The next round of patches, I’m going to try setting all the web related services to disabled, reboot, try installing the updates and see what happens. Tuesday, September 25, PM. Same problem here, every server. The original post was over a year ago and we’re still struggling with this issue? Microsoft has apparently gone radio silent as well, definitely thinking going to was a big mistake. Thursday, October 4, PM. Juergen 0. Another “me too”! Edited by J.
  Juergen Friday, October 19, AM. Wednesday, October 10, PM. Well, that didn’t do a bit of good. I’ve been waiting at “Getting Windows ready Don’t turn off your computer” for over an hour now. Also one of my DHCP servers has been installing updates for over an hour too. This is ridiculous. Thursday, October 11, AM. Thursday, October 11, PM. Thursday, October 18, AM. I’ve actually instituted a block on all deployments as a result of this. The service downtime is simply unacceptable.
  Thank god there’s still Linux. Thursday, October 18, PM. Tater 2. I’ve also decided to block any future installations of Server due to these issues. I’ve now begun testing Windows Server and so far it does not appear to have the same slow update issues. No kidding Updating Standard with 1 update, and have been to the cleaners, the mailbox, and the bank Saturday, October 20, PM. Just to add my two cents worth. Update: It took 1 hour 54 minutes from starting to download the update to getting the login screen once update installed.
  Edited by peter crozier Tuesday, October 23, PM. Tuesday, October 23, PM. This sometimes helps me, when Im all in tears ;- Yes, I tried that on one of mine Friday, October 26, PM. Just another frustrated sysadmin, grrrrrrrr. Tuesday, October 30, PM. Hmmm, will this help? It does roughly coincide with the top post mid Tuesday, November 13, AM. Sounds like if we have successfully installed KB, we can begin installing the Deltas?
  Wednesday, November 14, PM. Seriously Microsoft, this is a joke, fix the broken update system. Tuesday, November 27, PM. You guys really suck donkeys, ianc. Edited by ianc3 Tuesday, December 4, PM. Tuesday, December 4, PM. My disappointment is immeasurable and my day is ruined.
  Friday, December 7, PM. And sconfig is broken: Confirmed on multiple different WS servers. You know what’s not normal? Server updates I just created two VMs, installed server and ran updates. Nothing else. My hardware is FAST. Updates took We know you suck at some things, but maybe put some more resources into the important ones like Windows updates and server backup.
  What the honest hell is wrong with you? You need me to come in and straighten up some of the people in your departments? Check my logs? Saturday, December 8, PM. Edited by lolix2 Thursday, December 13, AM. Thursday, December 13, AM. Has anyone found any official statements from Microsoft on the slow update issue?
  Friday, December 14, PM. Did Someone have try windows update on server and how ir take to run in over-all. I’m so tired on my server Tater 0. So far I haven’t had any issues with updates on I’ve completely given up on and have upgraded my servers to No more update problems. Saturday, December 15, AM.
  Edited by greg smith jr Saturday, December 15, AM. Thanks for the info. Monday, December 17, PM. Installed the previously downloaded KB manually reboot then the previously downloaded KB manually It worked without further errors and later updates were also successful. Friday, December 21, AM. Microsoft’s official statement is called Server It is clear Microsoft has fallen off the bus with updates.
  Saturday, January 5, AM. Rob Holmes. Sunday, January 13, AM. Monday, January 14, PM. Edited by gustavoxp Tuesday, January 15, PM. Tuesday, January 15, PM. Get this crap fixed!
  Monday, January 21, AM. Microsoft wants to boost Server sales by not supporting Server properly. Server and Windows 10 are the worst OSes ever. Boot Window safe mode and patch..
  Bypass all dumb dumb slowness. Try it, its FREE! Wednesday, January 23, AM. We build Hyper-V hosts, and VM’s to deploy to customers. Oh to have server R2 back. At least that could be rolled out live in less that a week!
  Thursday, January 24, PM. In the time it has taken to install the January cumulative patch to Windows , I have managed to: – download the evaluation ISO on a Mb connection – install it in VirtualBox – install all updates including the cumulative update – reboot to desktop 5 mins later, Windows finally finished whatever it was doing and rebooted.
  Saturday, January 26, PM. Thank you Microsoft for no improvement at all. Rick Turske. Thursday, January 31, PM. And another one here. Tuesday, February 12, PM. I agree with you. MS should fix it. Thursday, February 21, AM. I can totally agree with you guys. It’s a nightmare with updates on – plain and simple and a fact. Don’t let MS support fool you otherwise.
  It needs to be fixed. With have thousands of Windows Servers for many different customers and everywhere we have we are seeing issues across the board and they’re getting more. W2K16’s update process is unreliable as hell. Tuesday, February 26, PM. Part of this may just be a result of the size much smaller. We only have a limited patching window of 5 hours Wednesday, March 13, PM.
  Windows is very quick. Monday, March 18, AM. It takes more than two hour to download and to prepare for installation. Despite that, installation was failed! I tried two other times and, finally, was installed. Maybe for monday I will finish to patch the server…. This is the second server I set up this week and the same issue happen on the first.
  See you on next Windows Update Hell chapter. Friday, March 29, PM. Monday, April 1, AM. Our company has had some specific experience with this in the past few weeks.
  Thursday, April 4, PM. Same problem here! I will do an inplace upgrade of the VM to and see what happens. Wednesday, May 1, PM. Please provide a solution. Or a response, other than someone saying “1. Perform a clean boot Wednesday, May 15, PM.
  Going on over 2 hours now waiting for the cumulative to install. This is pathetic. Thursday, May 16, PM. Everything is going bad on Microsoft side. Whatever they touch now it gets broken, discontinued or not usable. I am waiting for Server for more than hour to install one update, can’t see any progress and not sure how long it will take to finish.
  There is no control on anything these days in terms of managing windows systems, and if there is anything it might be taken away with next update. Friday, May 17, AM. Microsoft Enterprise. Browse All Community Hubs. Turn on suggestions.
  Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Show only Search instead for. Did you mean:. Sign In. New Contributor. Although there is no internet connection speed issue on other mobile devices and computers connected to the same modem, the internet download speed is 2 Mbps and the upload speed is 9 Mbps on my computer. I’ve tried the most common solutions suggested on Microsoft’s site and other sites on the subject.
  None of them worked out. I reinstalled Windows 10 by protecting the files and programs on my computer, but there was no solution. I also shut down all non-Windows applications and services that started automatically when the computer was booted, again, there was no solution.
  I tried more actions without any solution. My computer did not have such a problem 2 weeks ago. It started suddenly. Windows 10 Pro was upgraded recently to version Even though, I’m not sure I suspect this might be the problem. Any advice is appreciated. Thanks in advance.
  Labels: Labels: slow download speed WiFi Windows Tags: slow download speed. This is also a common reason, as users reported outdated Windows causing Windows store downloads slow frequently. In a thoughtful move by the Microsoft developers, there is a hidden cap over the download limits for the Microsoft store. This is done so that you can browse other sites along with downloading applications and games from the Microsoft store. This cap can be removed easily, and I shall show you how to.
  There are also some reports that third-party antivirus software may be causing interference with the internet connection, causing Windows 10 slow download speeds. Now that you have a slight idea about why you may be getting Windows 10 slow download speeds in Microsoft store, here are some of the potential solutions that you can use to diagnose which reason is causing the error on your device, and how you can solve it easily. The update glitch in Windows 10 is a very frustrating bug, as it prevents the normal functioning of the entire operating system if the pending updates are not installed on time.
  Users have reported that if they did not update Windows 10, they experienced Microsoft store slow download speeds. The only way you can solve this if you update your Windows 10 device by installing all the pending updates that are available for your device. This should solve the error and you should get good download speeds according to your bandwidth. Inside the Microsoft Store, also check if there are any pending updates for the Store application itself.
  Update the store app, as outdated applications may also reduce the speed by malfunctioning. There is also a possibility that there might be some error with your internet connectivity, which is causing Windows 10 slow download speeds. To confirm if there are any issues with your internet connectivity, check your internet speeds by using network monitors, or you can use free internet tests available online.
  If the internet speed is slower than that of your bandwidth cap, reboot your router, and create a new profile for the same on your Windows 10 device. If you still see Windows store downloads slow , call your service provider, and have them troubleshoot the issue from their side. Some users have reported that outdated Windows 10 store caused the download speeds to fluctuate, leading to slow download speeds.
  The cache refers to the data stored by apps and sites, which are used to load them the next time faster than before.
  You must be logged in to post a comment