MySQL Bugs: #62710: Workbench crashes when I select the locaton of the default dump folder

Bug #62710	Workbench crashes when I select the locaton of the default dump folder
Submitted:	12 Oct 2011 19:48	Modified:	15 Oct 2011 17:51
Reporter:	MIchael Sharp	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	5.2.35 CE	OS:	Windows (xp sp3)
Assigned to:		CPU Architecture:	Any
Tags:	DEFAULT, dump

Description:
Workbench 5.2.31 and 5.3.35 crash when I try to set the default location of the dump files.
Happens every time. No exceptions

How to repeat:
Edit
 Preferences ...
Tab --Administrator
  Button ... Location where dump files should be placed by default.
------------------------------
I get a popup error message:
MySQL Workbench Unexpected Error
MySQL has encountered a problem
External component has thrown an exception
-------------------------------
Then more text offering to submit a bug report

Suggested fix:
First started on my backup network using Workbench 5.2.35 -- server 6.0.0-alpha-community-nt. Recently installed Workbench 5.2.35 from 5.2.31.

Then started happening on my working network using Workbench 5.2.31 -- server 6.0.0-alpha-community-nt

Both have been working flawlessly for most of the year.

When it crashes right click around the bug icon and select copy back trace to the clipboard. Paste here the back trace. Thanks.

I uninstalled all versions if MYSQL Server and Workbench from the computers on both of my networks. I deleted all leftover folders. 
I uninstalled recent Windows updates then re-installed them.
I then installed server version 5.1.54 and Workbench 5.2.34 CE. 
I installed my database from a backup and am now able to work on both systems without crashes. This took about 15 minutes for each network.
I think that the solution to my problem was with Windows update, sense the issue arose on both networks at about the same time, and they were not running the same server and workbench versions. I thought I was synchronizing both networks but had missed several Server and Workbench update.