A summary of our installation issues
Here's a quick resource for issues that have been reported in the February CTP.
We've implemented a slew of fixes for Beta 2 and will be code complete early next week for that milestone; however, we don't have a formal date for when the Beta 2 will go live.
| Bad 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. |
No code changes to back up this issue. This is simply a user issue. |
| Connection over a proxy server can cause the web setup to fail | User reported the following: I appears the problem was that IE was set up to communicate through an nternal WinProxy firewall. When I placed myself outside of the proxy the install proceeded with no problems. You can fix the problem by going to Internet Properties, Connections>LAN Settings>and uncheck "Use a Proxy server for your LAN. For protection it is advised to go back and re-enable the internal proxy after installation. | Bug assigned to the ReadMe alias |
| Installation on Windows 2000 or below | Installation on Win2k or below is not supported, and Monad will not install on Win2K or below. However, the user can install the rest of the SDK on downlevel platforms if they have the latest msi.dll and msiexec.exe installed on their machine | This is an unsupported hack. Users do install on less than WinXP at their own risk. |
| Minimum version of msi.dll and msiexec.exe on the user's machine | User has an outdated version of msi.dll and msiexec.exe on their machine. Running Windows Update will update those components. | Fix is in place for Beta 2. Meanwhile ask users to run Microsoft Update. |
| No alerting the user when they have low disk space | Dev has revised code in the sdksetup exe that will trap for low disk space. In the meantime, we need to ask users who have setup failures if they fit this scenario. | The fix for this is in place for Beta 2 |
| The downloaded dbg_x86.msi file in the IE cache was corrupt. | Symptom: SDKSetup.exe correctly puts up the WinVerifyTrust UI dialog for the file after it fails trust checks. It's interesting to note that the corrupt file is the correct size and has an intact certificate. The corruption occurs towards the end of the file, so it is most likely failing CRC during WinVerifyTrust(). This is correct behavior and evidence that we are protecting users from compromised files. Still, we probably could do more to make the user experience better. Short-term work-around: FAQ the error on the web site. Tell users to clear their IE cache if they experience it. The error being messages like...12:14:57 AM Friday, February 24, 2006: [SDKSetup:Error] Config_Products_Configure: Configuration of Product Debugging Tools for Windows (failed): Signature of the file dbg_x86.msi could not be obtained. Possible unsigned file. Long-term fix: Tracking this issue with bug number 11403. Possible mitigation - if we can detect that a downloaded file is failing trust due to a CRC failure (vs. general cert check failure), we could try to clear that URL cache entry and re-download the file. Up to PM to spec the behavior. PM and Dev will be looking into it. I captured the file so I have a copy to play with. | This was hacked for Feb CTP - at the end of the cycle, Dev submitted the external MSIs for signing along with the rest of the content. He's working on a more permanent solution for future releases. |
| Corrupt CAB in the IE cache | Ask the user to purge their cache, then uninstall the SDK if it's still installed. Then retry the installation. | Dev is working on a retry scenario to resolve this.Expected behavior:User downloads a bad CABSetup removes the file from the cacheSetup retries downloading the fileIf succeeds, setup continues.If fails, loop one more time.If succeeds, setup continuesIf fails after the third try, setup errors out with a modal dialogue that contains the following message:"Setup has encountered a problem with downloading a file and needs to roll back. Please click OK to continue." |
Hope this helps; I'll keep you posted on where we are with posting, of course.
Please note that there's an update and an additional scenario listed at https://blogs.msdn.com/jsacks/archive/2006/04/11/573516.aspx