Windows 10 Mobile Build 10586 Problems: Continuous Restarts, Faulty Apps and More

Reading time icon 4 min. read


Readers help support Windows Report. When you make a purchase using links on our site, we may earn an affiliate commission. Tooltip Icon

Read the affiliate disclosure page to find out how can you help Windows Report effortlessly and without spending any money. Read more

Microsoft announced a new build for Windows 10 Mobile, which goes by the number of 10586, a few days ago. It started to roll out to users of Fast Ring, and from today, it is also available for Slow Ring insiders. And while the new build fixed a lot of issues from the previous build, it also caused some new problems for Windows 10 Mobile insiders, so we created a list of all reported problems in Windows 10 Mobile Build 10586, so you won’t be surprised by these bugs.

You can also have a look at the many issues caused by Windows 10 1511. Here are some the reported bugs from Windows 10 Mobile build 10586:

  • After we released Build 10581 to Windows Insiders in the Fast ring, we discovered a bug in the build that will cause the filesystem to become partially corrupted after doing a factory reset. For those of you who did a factory reset of your phone, you most likely did not notice this issue on Build 10581. Due to this bug however, upgrading to Build 10586 will cause your phone to go into a reboot loop after the upgrade completes – rebooting at the Windows or operator logo. To recover your phone, you can use the hardware key combination to reset your phone which will then put it at the OOBE experience on Build 10586. We highly recommend that you make sure you do a backup your phone before upgrading to Build 10586 due to this bug. Additionally, you can also recover your phone by using the Windows Device Recovery Tool to go back to Windows Phone 8.1 and then upgrade to Build 10586.

  • Deploying Silverlight apps through Visual Studio to your phone still won’t work in this build. This issue will be fixed with the release of Visual Studio 2015 Update 1 on Nov. 30th. You can deploy UWP apps to your phone without any issues.

  • There is a known issue where the tile for Insider Hub still remains under All apps but doesn’t open. Insider Hub isn’t included in this build. There isn’t a way to get it back unfortunately. However, it’ll return in a future flight! In the meantime, use Insider Hub on the PC as a workaround.

  • Some users have reported that they’re unable to use Maps and HERE maps after installing Build 10586: “Windows 10  (MOBILE) on Nokia Icon phone cannot open MAPS app.  Is an update in process or should this application work?”

  • You might encounter continuous restarts after installing the new build: “updating to 10586 built preview, my 640 xl is restarting again and again for more then 2 hour what should i do, please help me its very urgent”

  • Some users have also reported that they’re even unable to install the new build due to an unexpected error 0x8024201f: “How update 640 xl from 10562 to 10586? An error message 0x8024201appear all the time… “

Here are some other issues described by Windows 10 Mobile users related to the most recent 10586:

I am currently running OS Build 10.0.10586.11 on my Lumia 1520.  As far as I can tell, there is no way to add credit cards to the current Wallet App, nor is there a way to turn on NFC Payments. I’ve got a secured SIM, and my carrier supports NFC Payments.

After solving the boot loop problem and the overnight fix for the Lumia app updates, there is only one problem remaining with my 930. The store takes very long to start, especially in weak signal areas (H/H+). Sometimes it takes over 10sec until the store is ready for use.

I have upgraded my Lumia 1020 to the 10586 build of Windows 10. After the upgrade, my Messaging app was completely unresponsive. Would take 80+ seconds to open the app, then again to open a thread, and again to send a message. So – last night I did a factory reset on the device. After the reset, now my Messaging app works quickly, however I’m missing a lot of history. The app did load history, but it did not load any history past Feb 2014.

As you can see, even if some people believe that Build 10586 is going to be a RTM build for Windows 10 Mobile, there still are a plenty of errors that need to be resolved by Microsoft before it releases the new mobile OS for good.

If you have any solutions for these reported problems, please tell us in the comments, because you’re going to help a lot of people by solving their problems with the latest Windows 10 Mobile build.

More about the topics: windows 10 mobile