Dot Net 4.5.2 update fails repeatedly with error 643

[PcTek9]

I was working on a windows vista computer, and noticed the update to microsoft's .net 4.5.2 technology had failed repeatedly over and over. I tried the .net diagnostic tool, which failed. Logs were sent to microsoft. I tried running the fix-it tool and nothing worked. I tried reinstalling the update, then downloading the standalone update and installing that, (multiple times). Nothing worked. So I searched google for hours, and saw that many people had similiar problems and some claimed to fix it with various techniques, so I tried those, and still nothing.
Here's what worked for me. I booted the vista machine with ntfs4dos, walked into the c:\windows\system32\en-US folder and renamed dfshim.dll.mui to butterbean.bin, lastly I rebooted the system, and the 4.5.2 update installed perfectly with no issue at all. Of course now if you are wondering what will I do with the butterbean.bin file? While I was inside of ntfs4dos I simply stroked in: type dfshim.dll.mui|more and watched the miscellaneous hexadecimal gibberish flubber by on the screen. I did see it was an actual MicroSoft file, so apparently this problem with update 4.5.2 really is an issue that MS needs to look at. Have a great day.
Update: Some people are experiencing this same error with Windows 7, & 8 versions. Once 4.5.2 completed installation, I found it had installed a newer larger version of dfshim.dll.mui so I was able to delete butterbean.bin without any problems.

 

[HFultzjr]

I was working on a windows vista computer, and noticed the update to microsoft's .net 4.5.2 technology had failed repeatedly over and over. I tried the .net diagnostic tool, which failed. Logs were sent to microsoft. I tried running the fix-it tool and nothing worked. I tried reinstalling the update, then downloading the standalone update and installing that, (multiple times). Nothing worked. So I searched google for hours, and saw that many people had similiar problems and some claimed to fix it with various techniques, so I tried those, and still nothing.
Here's what worked for me. I booted the vista machine with ntfs4dos, walked into the c:\windows\system32\en-US folder and renamed dfshim.dll.mui to butterbean.bin, lastly I rebooted the system, and the 4.5.2 update installed perfectly with no issue at all. Of course now if you are wondering what will I do with the butterbean.bin file? While I was inside of ntfs4dos I simply stroked in: type dfshim.dll.mui|more and watched the miscellaneous hexadecimal gibberish flubber by on the screen. I did see it was an actual MicroSoft file, so apparently this problem with update 4.5.2 really is an issue that MS needs to look at. Have a great day.
Update: Some people are experiencing this same error with Windows 7, & 8 versions. Once 4.5.2 completed installation, I found it had installed a newer larger version of dfshim.dll.mui so I was able to delete butterbean.bin without any problems.

Nice tip!

But how in the heck did you come up with that fix?

 

[ZATZAi]

Interesting, I've been seeing that error a lot myself as well across Windows 7, 8 and 8.1 even with NiNite...

 

[PcTek9]

Nice tip!

But how in the heck did you come up with that fix?

** I'm a computer guru... It's what I do.

but ... since you asked nicely... remember that when windows installs updates it writes a log file of the update. I found the log file, and opened it in notepad. It was huge. I quickly went to the bottom of it, (probably 30 pages of technical stuff if you read it all), and I found on the last page that a file had been locked by some higher authority than the administrator account, and of course, the file name and path were posted in the log. Since Microsoft's own update software could not delete, remove, or access the file, I wasted a few moments trying to delete it as administrator. Naturally, that failed. So the next step is simple, mount the drive from Linux or something like ntfs4dos, rename the file, reboot, install updates. It worked, and as I stated a newer version of that file was installed by Microsoft.

 

[HFultzjr]

** I'm a computer guru... It's what I do.

but ... since you asked nicely... remember that when windows installs updates it writes a log file of the update. I found the log file, and opened it in notepad. It was huge. I quickly went to the bottom of it, (probably 30 pages of technical stuff if you read it all), and I found on the last page that a file had been locked by some higher authority than the administrator account, and of course, the file name and path were posted in the log. Since Microsoft's own update software could not delete, remove, or access the file, I wasted a few moments trying to delete it as administrator. Naturally, that failed. So the next step is simple, mount the drive from Linux or something like ntfs4dos, rename the file, reboot, install updates. It worked, and as I stated a newer version of that file was installed by Microsoft.

Very nice!

Thank you.

 

[citizensmith]

nice find - thanks for sharing

 

[johnrobert]

Too bad I wont remember it in the future