Windows Phone 8.1 Update Halt

Windows Phone 8.1 Update has been stopped temporarily for HTC 8X and HTC 8S smartphones. According to Microsoft, an issue may occur on a small percentage of users related to missing drivers.

"There are a small set of devices for which we aren't offering the latest build of the Developer Preview program due to an identified problem that requires mobile operator or OEM driver updates," posted at the FAQ in Microsoft's official Web site.

Moreover, Microsoft confirms that the drivers required for Windows Phone 8.1 Developer Preview program will be offered when the official update for the device is available.

Microsoft Windows Phone Chief Joe Belfiore confirmed the issue at Twitter about the error 8018830f and it is affecting a small percentage of HTC users worldwide. His team is currently working to resolve the problem. However, there are two more issues he also confirmed regarding the Windows Phone 8.1 update.

Updating Issues on Windows Phone 8.1

There are three issues known about updating to Windows Phone 8.1 and have been attributed to compatible smartphones:

1. Error 8018830f: Microsoft Windows Phone Chief Joe Belfiore confirmed at Twitter that this error was a "packaging problem" with the update and the fix is already out. Users are encouraged to try again and it should work now.

2. Error 80188306: Another error reported at Microsoft which renders some users unable to open the update after installation. A moderator replied to the issue and suggests Soft Reset action on the device, using a different Wi-Fi connection for faster Internet speed and by downloading certain apps such as Storage Cleaner or Shrink Storage to increase storage space on the device. As a final resort, users should contact the network carrier to reinstall packages which might have been corrupted.

3. Low Storage Issue: Windows Phone Chief Joe Belfiore also confirmed this problem on the Windows Phone 8.1 and according to his tweet, retrying won't work and may be related to low system storage. The software development team is currently working to fix this issue.