Bug #73491 Error Installing Workbench 6.1.7
Submitted: 7 Aug 2014 0:35 Modified: 14 Aug 2014 1:26
Reporter: Scott Weigand Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:6.1.7 OS:Windows (v7 Pro SP1 x64)
Assigned to: CPU Architecture:Any
Tags: install, setup, Workbech

[7 Aug 2014 0:35] Scott Weigand
Description:
While trying to install Workbench 6.1.7, which seems to take a lot longer than usual, errors while copying new files with the error "Error 1310.Error writing to file c:\Program Files (x86)\MySQL Workbech 6.1 CE\images\icons\tiny_align_v_middle.png.  Verify that you have access to that directory."

I'm using my own account, which has administrator rights. During my first attempt, it removed my previous version (6.1.4)

How to repeat:
1. Download MSI file
2. Run file (be prepared for system to hang majorly)
3. Do a "Complete" install
4. Wait for it to start "Copying new files"
5. Error appears

Suggested fix:
I think there is a deeper issue as the install hangs badly at every step, but certainly the popup is a mystery.
[12 Aug 2014 18:13] MySQL Verification Team
Thank you for the bug report. The failed install was done with user Administrator privileges?. Thanks.
[12 Aug 2014 18:15] Scott Weigand
Yes, I did the install using my sign-in which has Administrator privileges.
[12 Aug 2014 19:47] MySQL Verification Team
Thank you for the feedback. Is there a chance on your environment while the install process was running a third application like anti-virus, backup tool, defragment tool, etc was acting on c:\Program Files (x86)\MySQL Workbech 6.1 CE\images\icons\ folder?. Also the issue happens all the times?. Thanks.
[14 Aug 2014 1:26] Scott Weigand
This one is all on me. Turns out I got a few bad segments on the hard drive (LOL?). And I'm willing to bet the image file in-question is right in one of those segments.

** Hard Drive 0 - DST Short Test **
Test Results : Fail
Error Code 2000-0142
Validation 71025
Msg: Hard Drive 0 - S/N XXXXXXXX, Short self test unsuccessful.

I'm running a CHKDSK C: /F/R, may fix the issue. Else, I get a new drive under warranty.