MySQL Bugs: #71538: Upgrade to MySQL Win Community Server 5.5.35 fails with unhandled .NET exception

Bug #71538	Upgrade to MySQL Win Community Server 5.5.35 fails with unhandled .NET exception
Submitted:	30 Jan 2014 23:41	Modified:	10 Aug 2015 10:42
Reporter:	Giuseppe Piscopo	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL for Windows: Installer	Severity:	S2 (Serious)
Version:	5.5.35	OS:	Windows (WIndows 7 64bit)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
When trying to upgrade MySQL Server Community to version 5.5.35, an unhandled .NET Framework exception is generated. After that, there's no way to go on with the upgrade process.

How to repeat:
1) Download "mysql-installer-community-5.5.35.0" from your website
2) Execute that and wait for "Update Products" window to show up
3) Select "Install updates"
4) Accept license terms on License Agreement screen
5) Leave checked the product upgrade named "Upgrade MySQL Server 5.5.27 to MySQL Server 5.5.35"
6) Press Execute
7) If asked to download an update to the Installer itself, choose "No"
8) Press "Next" at "Apply Updates" screen
9) Press "Execute" with the only pending change being MySQL Server 5.5.35 upgrade
10) Wait less than a second to see a dialog about an unhandled exception in application, asking to see more details, or continue or quit. At this point, whatever you choose, you cannot complete the installation process.

Detailed text from .NET unhandled exception standard dialog

Attachment: dotNET Unhandled Exception Details.txt (text/plain), 6.39 KiB.

Error dialog

Attachment: Server 5.5.35 Update error.png (image/png, text), 109.25 KiB.

Hello Giuseppe Piscopo,

Thank you for the bug report.
I tried with latest MySQL Installer, and attempted to upgrade from 5.5.27 to 5.5.35 as well and it worked without any issues. 
Probably this is fixed, please feel free to reopen this bug report if you encounter this issue again.

Thanks,
Chiranjeevi.

screenshot

Attachment: 71538.PNG (image/png, text), 56.49 KiB.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".