14 DAY TRIAL // Microsoft recently kicked off the rollout of Windows Phone 8.1 Update 1 for smartphones that have been upgraded to Developer Preview, but a small percentage of users have already been affected by an issue that prevents them from installing the update.
Known as error 8018830f, the issue has been acknowledged by Microsoft, as the company confirms that it is now working on a fix for this problem. Even though there's no ETA for the release of said fix, we expect that Microsoft will want to address this problem as soon as possible.
However, this is not the only problem Windows Phone users have experienced since the release of the update. Many HTC 8X and HTC 8S owners have already reported that they have been unable to download and install the Windows Phone 8.1 Update 1 since Microsoft released it for the public.
Well, it looks like there's an explanation for the whole situation. Although we would have preferred an official statement soon after the problem had been identified, we are forced to accept, once again, a short statement that a Microsoft spokesperson offered to WPCentral.
Here is what Microsoft has to say about Windows Phone 8.1 Update 1 for HTC smartphones:
“We have paused delivery of Windows Phone 8.1 Update to customers with the HTC 8X and HTC 8S who are using the Preview for Developers. Microsoft and HTC have identified an issue and are actively working to fix it, and will resume delivery of the update once a fix is in place.”
Given the fact that no additional details have been disclosed on the matter, it's hard to tell what's causing the issue. The good news is that Microsoft is actively working to fix it, and hopefully, Windows Phone 8.1 Update 1 will be available for download for HTC devices sooner rather than later.
Keep in mind that this problem affecting HTC 8X and HTC 8S is in no way related to error 8018830f that we reported on yesterday.
Previous information appeared on Microsoft Support Forums pointed to outdated firmware as the cause of these problems for HTC devices, but this hasn't been confirmed yet.
Microsoft's statement is only meant to confirm that the issue has been acknowledged and a fix is in the works, as no explanation has been given regarding the cause of the problem.
We will keep an eye out for any additional details on the matter and will update the news as soon as new info becomes available, so stay tuned for more on this one.