Windows 10 Mobile Build 10512, 10514, 10536 Download Stuck for Several Users
According to a couple of Windows 10 Mobile users, it seems that downloading Windows 10 Build 10512, 10514 and 10536 takes a very long while to complete. Here are some more details.
It seems that it is taking forever to download Windows 10 Mobile build 10514 and 10536.1000 on my Lumia 930. It has been eight hours now, and the phone is still at the Downloading updates (0%).
A soft reset has restarted the update, and it has been running for three to four hours now. But even after the soft reset, the download is still stuck at 0%.
My Lumia 625 (spare phone) has finished downloading the two builds but when it is preparing to install the builds, it crashes with an error 0x800705b4. Twice. And after that it doesn’t receive the builds.
So, as we can see, the user did a soft reset but that didn’t help too much. We need to remind that these builds are fairly new, so this kind of issues are ‘natural’, if I can put it this way.
Windows 10 Mobile build 10512, 10514, 10536 download met with problems
Somebody else also weighed in, saying the following:
Mine is says updates are available and shows both:
Windows 10 Technical Preview for phones (10.0.10514.0) and
Windows 10 Technical Preview for phones (10.0.10536.1000).
It’s been on “Downloading updates 0%” for hours now, including after several soft resets.
It seems I’m a whole update behind, since two builds don’t usually appear at once, but this is the first I’ve seen of either of these updates being available. Maybe that’s part of the problem?
So, as we can see, these are indeed some annoying problems. If you have experienced them, as well, do leave your comment below and share with us. If you know a fix to these issues, then we’ll be happy to hear it.
Most of us are sick of the messages informing us that the content is unavailable when we access Hulu or Netflix apps. This notification appears […]
Error 0x80070780 arises for some users when they try to copy, delete, back up or edit certain files in Windows 10. The error message states: […]