Releasing new Windows Phone 8.1.1 Preview for Developer’s update, Microsoft promised that the build would fix glitches present in the Windows Phone 8.1 Developer Preview.
The Windows Phone 8.1.1 developer preview is now available for download, and several early adopters of Windows Phone 8.1 have already received the upgrades on their devices.
The highlight of build 8.10.14176 [screenshot below] is the remedy to the 80188308 error bug which is notorious on account of having prompted quite a few storage malfunctions resulting in the running out of storage space in the system partition during the update.
However, it is suggested to those still receiving the impugned error on a Nokia Lumia smartphone, to reset the device with the aid of Nokia Software Recovery Tool.
Addressing growing concerns about the storage error bug, Microsoft has issued a statement assuring its users that the 14176 update should fix this issue, and those who have not been able to install the Windows Phone 8.1 Preview for Developers update need not be disheartened as they still have the option to update their smartphones to the latest version of the software.
However, for the users of smartphones that come equipped with a relatively lower storage capacity, a bug other than the 80188308 error might be causing storage snags. Microsoft recommends that in such a scenario, the users should unclutter their device by uninstalling some apps and games, or by deleting pictures/videos, and creating more space.
Besides the above-mentioned plus-points of the build 8.10.14176, and the statement which says that it will provide “a bunch of performance improvements and general fixes,” additional details about the update have not yet been shared in the public domain.
As of now, the users who have successfully downloaded and installed the updates, have reportedly, not come across any features other than performance improvements.
“immensely exasperating glitches present in the Windows Phone 8.1 Developer Preview”
That’s quite an exaggeration, don’t you think? Besides it was a small percentage of users experiencing the problem to begin with.