Setup fails to access MicrosoftRootAuthority.crl - by Dmitry Mashkov [MSFT]

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 352140 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 6/20/2008 6:35:28 AM
Access Restriction Public


During the installation of RC0, setup reported that computer is not connected to Internet.
1. This is incorrect. Moreover, there's NO way to make such decision. A failure to reach some URL is not an indication that there's no Internet access. You should choose the correct wording and report just a failure to reach specific URL *and* report exact error (Winsock error code or fully Proxy response - whatever you got).
2. In this particular case, the detection itself was incorrect. The URL is accessed correctly, under the same account on the same machine.
Sign in to post a comment.
Posted by Microsoft on 6/20/2008 at 2:30 PM
We agree that this should be fixed unfortunately its too late for this release. We already have a work item tracking removing this rule for our next major release so I have closed your bug.


Amy Lewis