Microsoft has just released the latest update for its Windows 10 Mobile build 14951, but it appears that it has already experienced problems, particularly concerning a bug that causes people's devices to freeze whenever they try to get the patch.

Windows Insiders flocked to Microsoft's community forums on Thursday, Oct. 20, to report that their mobile devices keep getting stuck at 0 percent every time they try to download the mobile build update.

According to Microsoft, the issue appears to affect only Windows 10 devices that run on Mobile build 14946. The company is now working to change how and when it publishes Build 14951 to prevent similar problems from happening again.

Microsoft also urged insiders to continue sending feedback whenever they encounter issues to help the company find an appropriate resolution.

For now, those affected by the update downloading issue can try four different methods to address the current situation. Microsoft said it is still in the middle of validating these options.

Fastest Option

The fastest way to fix the problem is for users to force the update session on their devices to time out.

1. Make sure to plug your device into a charger.

2. Access Settings on your mobile device, followed by Update & Security then Windows Insider Program. You will need to switch your device to "Slow" then switch it back to "Fast."

3. Activate the Airplane Mode by opening Settings again then Network & Wireless.

4. Go back to Settings then open Time & Language followed by Date & Time. If your device is set to automatically adjust the date and time, you will need to turn this option off.

5. From the date your device is currently set, you need to adjust so that it's set to 7 days in the future.

6. Make your way back to the Home screen then reboot your mobile device.

7. Once the reboot is finished, go back to Settings then Network & Wireless and turn off the Airplane Mode.

8. You will then have to check for updates by going to Settings, followed by Update & Security then Phone Update.

9. When you try to check for potential updates, your mobile device will experience an error but this is to be expected.

10. You will now have to change the date on your device to the current one. You can do this by accessing Settings then Time & Language.

11. Check for updates again by repeating Step 9. This may result in another error but it's to be expected.

12. You will need to reboot your mobile device again.

13. Following the reboot, check for updates again. This should allow you to proceed with the downloading of the Windows 10 Mobile build 14951.

Microsoft noted that some devices encountered error code 80242006 when users tried to check for updates during the previous step. The company is still trying to verify this report but for now, it suggests that users try the additional steps provided by Windows insiders to be able to bypass this error.

14. Go back to Settings, then Update & Security and then Windows Insider Program. Switch your device to "Slow" again.

15. If you check for updates while running on the "Slow" ring, you'll receive a message that your device is up-to-date.

16. Switch your mobile device back to the "Fast" ring again and check for updates. This should allow you to go through with the updating process.

Other possible fixes suggested by Microsoft include one referred to as the "easiest-longest" way, which involves having to wait for your mobile device to time out after 5 days. As soon as it is able to get out of the current update process, it will then receive an updated metadata that would allow it to continue with getting the Build 14951 patch.

The "medium work" process requires users to factory reset their Build 14946 mobile devices. This can be done by accessing Settings, followed by System, then About and then Reset. This should allow the device to download the Build 14951 update without any problems.

The final step is referred to as "most work" that involves having to roll the device to an older mobile build. This should let the device push through with the Build 14951 update.

ⓒ 2024 TECHTIMES.com All rights reserved. Do not reproduce without permission.
Join the Discussion