Windows 10 Mobile Build 10586.63 Issues: Battery Life, Corrupted Settings and More

Reading time icon 4 min. read

Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

Windows 10 Mobile build 10586.63 is released, and it was troublesome even upon its release. First Microsoft started the rollout, then the company decided to pull it, and now it is available again, but only for Insiders on Fast Ring.

Build 10586.63 is rumored to be an upgrade version of Windows 10 Mobile, which means that it shouldn’t feature any bugs of flaws. But, users who already installed it are reporting various problems, that appeared after they updated their phones. So, if you’re also experiencing some kind of a problem after the update, you should know that you’re not alone.

Windows 10 Mobile Build 10586.63 Reported Problems

We’re going to start our ‘list’ with the installation of the latest build. Although the build is available again, one user reported on Microsoft Community forums that he’s unable to install the latest build due to an error 0x800F081F.

“I have tried lots of times to install the latest insider update 10583.63 on my lumia 930 but it always fails with error (0x800f081f) as it prepares to install. I am currently on insider preview 10583.36. I have 20 gb free space. I have tried soft reset, hard reset and reinstalling about 5 times but always fails as it prepares to install.

Anyone else seeing this or any thoughts?”

One other insider suggested him to try to revert to Windows Phone 8.1, and then update to the build 10586.63 from there, but we’re not sure that this solution is effective.

Next is the charging problem. Namely, one user reported on Windows Central forums that his Lumia 930 is charging a lot slower since installing the update.

“Having experimented with loads of different combinations of chargers and wires, with hugely differing results, I had managed to record charging speeds on Lumia 930 of around 60% per hour using a Qualcomm 2.0 enabled charger and a high quality cable. Having updated to 10586.63, I don’t seem to be able to get anything above 27.76% per hour using any combination of charger and wire. Is anyone else having problems? Has Qualcomm compatibility been shelved for this update? “

While we’re at Windows Central forums, one user also complained there that he’s unable to access some basic settings on his Windows 10 Mobile device.

“After updating to this build .63 … I am unable to open most of the system settings like equalizer..glance… Etc etc almost all of the. ….. any other solution then resetting?”

Unfortunately, we don’t have solutions for any of these problems.

Users in China also appear to have problems after installing this build. One user complained on Microsoft Community forums that, after he applied the update, he wasn’t even able to turn on his phone.

“I’m using the Lumia950xl of the Republic of China version. And join in the windows insider plan. Today I update my phone to the last preview version (10586.63). It download successfully and restart, but when it going installing the update when restarted, errors happened and show me a crying face. Then it restart again and show crying face again and again. Finally a recover my phone by the software Windows Device Recovery Tool. Would you please check out what wrong with it. Wish to receive your reply. Thank you.”

Next is the missing Phone app tile: “After I updated my phone to build 10586.63 the phone app tile for sim 1 is vanished from my start screen and can’t pin that back. Sim 2 tile is still there. When I linked both no tile is in the start screen at all.”

And finally, the last complaint we managed to find is the problem with pairing Windows 10 Mobile device with other devices. Namely, one user reported that he’s unable to pair his Windows 10 Mobile phone with his Band 2.

“Darn. All was going so well with my new Band 2, but after the 10586.63 update to my 1520.3, the Band won’t pair. Anyone?”

All these errors indicate the fact that Microsoft rushed with the releasing this build, as it still needs to be ‘polished.’ The company saw that, and the build was pulled until some problems are solved, but it looks like Microsoft rushed once again when re-launching the build.

Unfortunately, we don’t have solutions for any of the above mentioned problems, so if you know how to fix some of them, your suggestions are most welcomed.

Also, if you experienced some other problem on your Windows 10 Mobile device, after installing the latest update, tell us in the comments, and we’ll update the article.

More about the topics: windows 10 mobile, windows 10 update