The problem seems to occur at stage 6 of 10 of the update process, where the handset reboots after the update. Users trying to install the update are faced with the following error message:
An error prevented the restoration of your phone to its previous version.
Your phone can’t be used in its present condition and there are no restore points for it on this computer. The phone might restart and return to normal if you disconnect it. For further assistance, contact your mobile operator.
ERROR CODE C101002E
Well, if you are affected there is hope ...
WinRumors has outlined a possible fix for the WP7 update handset bricking problem. It's long and convoluted, involved downloading firmware from untrusted sources and there are no guarantees ... but it could bring your bricked handset back to life.
Microsoft is investigating new public reports of a vulnerability in all supported editions of Microsoft Windows. The vulnerability could allow an attacker to cause a victim to run malicious scripts when visiting various Web sites, resulting in information disclosure. This impact is similar to server-side cross-site scripting (XSS) vulnerabilities. Microsoft is aware of published information and proof-of-concept code that attempts to exploit this vulnerability. At this time, Microsoft has not seen any indications of active exploitation of the vulnerability.
The vulnerability exists due to the way MHTML interprets MIME-formatted requests for content blocks within a document. It is possible under certain conditions for this vulnerability to allow an attacker to inject a client-side script in the response of a Web request run in the context of the victim’s Internet Explorer. The script could spoof content, disclose information, or take any action that the user could take on the affected Web site on behalf of the targeted user.
Microsoft has published a one-click “Fix it” workaround for the bug that involved locking down MHTML. This will prevent the launch of script in all zones within an MHTML document. Any application that uses MHTML will be affected by this workaround.
The latest removed driver will be automatically selected in the drop down, if this is not the item with the entries below you need to locate these by browsing through the items. One (or all) of the following parts should be in the list:
Click on the Restore button and Driver Sweeper will restore the files and directories. This can take a while, don't close the application before you get a notification that the backup is restored.
Restart your system and you are done!
Might work, saving you from a reinstall ... or it might not ...