Monday, February 13, 2012 4:40 AM
Getting "file failed verification" when attempting to install VS2010. The installation ISO was obtained from the Microsoft Volume Licencing center, and there was no checksum on the download page to enable me to verify whether the file downloaded successfully. I downloaded it twice with the same result. I attempted to install on my regular PC (Windows 7), and on a brand new VM (also Windows 7) with the same result. I have placed a vslogs.cab file generated from the "brand new VM" attempt on Dropbox
Monday, February 13, 2012 6:18 AM
Hi Brett, thanks for posting the error log. I found the following error below from your logs.
[02/14/12,15:14:28] Microsoft Visual Studio 2010 Professional - ENU: File failed validation: e:\setup\..\.\WCU\dotNetFramework\dotNetFx40_Full_x86_x64.exe; error = 0x80091007
[02/14/12,15:14:28] Setup.exe: AddGlobalCustomProperty
[02/14/12,15:14:28] Microsoft Visual Studio 2010 Professional - ENU: ***ERRORLOG EVENT*** : CRootComponent::Install(): Cannot install; setup files failed verification.
This does infact mean that the download was not completed successfully and therefore the installer is corrupt. Could you please tell me the file name that you downloaded from the MS Volume Licensing Center? Here are the SHA1 checksums that can be found from the MSDN download website.
en_visual_studio_2010_premium_x86_dvd_509357.iso - A4E69966496AD0F704FE9D97FAC2A723EF75A99B (SHA1)
en_visual_studio_2010_professional_x86_dvd_509727.iso - F0ED50712D83BF0EDA7D284DA76DF49E4C88CEF7 (SHA1)
en_visual_studio_2010_ultimate_x86_dvd_509116.iso - 84C90BB02AF92347010FF9058E0A2BA28F19CC53 (SHA1)
- Edited by systemx Monday, February 13, 2012 6:24 AM
Monday, February 13, 2012 10:04 PM
I calculated the SHA1 checksum as 999b094078fec1e3bd26202e0805df628a3f4782, so that doesn't match, but then neither does the filename.
Monday, February 13, 2012 10:29 PMThanks for the info Brett, I am downloading that particular file right now and will install it on one of my machines here and post back the checksum if the install succeeds without any errors.
Tuesday, February 14, 2012 12:47 AM
Hi Brett, I have not managed to find time to install the ISO, but the md5 that I have is f5c9d0e1ebb73f1530942ad04f20c17c. Could you please re-download the ISO again as the ISO you have is certainly corrupted.
Tuesday, February 14, 2012 12:53 AMIs that the MD5 checksum you calculated from the copy you downloaded, or is it one which was published by Microsoft?
Tuesday, February 14, 2012 1:04 AMHi Brett, I downloaded the same ISO with the same file name as you posted earlier directly from Microsoft.
Tuesday, February 14, 2012 7:00 AM
Well, you were correct. The installer was corrupt. I downloaded a third time, getting a different checksum from either of my previous two attempts, and different from yours -- and of course the same result. Then I finally bit the bullet and for the fourth attempt I used IE with the download manager plugin, and bingo! the checksum matches yours, and installation is working properly.
Why oh why doesn't Microsoft post checksums for their ISOs in the Volume Licensing Center? It would save so much pain!
- Edited by Brett Donald Tuesday, February 14, 2012 7:02 AM