If you downloaded an ISO and have problems...

Note: this post has been edited with revised information

I just received my first report of a user who downloaded an ISO version of our SDK and reported an installation problem. It turns out the problem was due to a corrupt ISO download.

To verify that your download of an ISO file for a Windows SDK Feb CTP build is not corrupt, download the CRC Utility. (Note: this is not a Microsoft application. Use at your own risk. )

To run the CRC test, open a command prompt and run the utility. providing it the name of the file (i.e. crc c:\6.0.5308.0.9.WindowsSDK_Vista_idw.DVD.Test.img) The CRC utility will run two tests on the ISO: it will verify if the ISO is valid, and it will give the AutoCRC signature for the file. The AutoCRC signature for the Windows SDK Feb CTP ISO is 0xE18E3367. You should also confirm the size of the ISO is correct: 1.06 GB (1,141,606,400 bytes).

If it fails any of these three tests, re-download the ISO. If it still fails after re-downloading, please email me. Thanks!

Comments

• Anonymous
  March 02, 2006
  Hmmm, mine's 1,141,606,400 - the one at work. It installed successfully too! Weird.
  
  Signature returned is 0xE18E3367 - different from yours. It installed perfectly and everything has worked fine as of now.
  
  My setup at home crashed now. I need to figure out why this evening. Obviously, the crc test you suggested is not going to help - because at work it worked fine even though my test results didn't match what you said is valid.
• Anonymous
  March 02, 2006
  Funnily, the download at home had that exact size in bytes (1,141,606,400) and also the same signature 0xE18E3367
  
  I extracted the files from the ISO and ran it directly, and it worked.
  
  What's weird is how your ISO size and signature are different. Is it possible that your numbers were based on a build different from the public Feb CTP?
• Anonymous
  March 03, 2006
  I'm sorry, I was looking at an internal build. You're right about the ISO information.