How to fix broken security in Windows 2000?

In http://support.microsoft.com/default...b;en-us;293781 there is
the very interesting comment:

"As you may have noticed in the provided information, some of the
certificates have expired. However, these certificates are necessary for
backwards compatibility. Even if there is an expired trusted root
certificate, anything that was signed with that certificate prior to the
expiration date needs that trusted root certificate to be validated. As long
as expired certificates are not revoked, it can be used to validate anything
that was signed prior to its expiration."

Oh! *NOW* you [Microsoft] tell me. Just too bad the information wasn't
provided earlier.

Been wrestling with this problem for several weeks, and though I'm not
certain, I very strongly suspect that what happened is that I deleted a
required security certificate in the foolish belief that the expiration date
had some meaning. Quite trivial to do from IE: Tools menu -> Internet
Options command -> Content tab -> Certificates button -> Trusted Root
Certificates tab. Not certain because it happened a while ago and the
resulting problem is minor, though annoying. Some possibility it may have
been caused by a WindowsUpdate, possibly even one that was pushed onto my
machine by the corporate IT people.

The problem itself is that the computer complains about a new file version
that it can't check. It doesn't reveal what file, and it doesn't actually
say anything about a missing security certificate, but I'm pretty sure
that's what's going on. The SFC fails to run, which is apparently related.

I'm pretty sure that all of the root certificates have been restored, but
either there is a missing certificate somewhere else, or it is some kind of
chain reaction thing.

Anyone else having similar problems? Any suggestions about how to fix it?
Diagnostic steps to identify the missing certificate or even the affected
file?

I have read, and reread, you entire posting.
As far as I can tell, all that you have told us, aside from
your suspected cause, is
<quote>
The problem itself is that the computer complains about a new
file version that it can't check. It doesn't reveal what file
</quote>
That is not really very much to go on.
When does this happen for example.

--
Roger Abell
Microsoft MVP (Windows Security)
MCSE (W2k3,W2k,Nt4) MCDBA
"Shannon Jacobs" <> wrote in message
news:uH$rAxP$...
> In http://support.microsoft.com/default...b;en-us;293781 there is
> the very interesting comment:
>
> "As you may have noticed in the provided information, some of the
> certificates have expired. However, these certificates are necessary for
> backwards compatibility. Even if there is an expired trusted root
> certificate, anything that was signed with that certificate prior to the
> expiration date needs that trusted root certificate to be validated. As
long
> as expired certificates are not revoked, it can be used to validate
anything
> that was signed prior to its expiration."
>
> Oh! *NOW* you [Microsoft] tell me. Just too bad the information wasn't
> provided earlier.
>
> Been wrestling with this problem for several weeks, and though I'm not
> certain, I very strongly suspect that what happened is that I deleted a
> required security certificate in the foolish belief that the expiration
date
> had some meaning. Quite trivial to do from IE: Tools menu -> Internet
> Options command -> Content tab -> Certificates button -> Trusted Root
> Certificates tab. Not certain because it happened a while ago and the
> resulting problem is minor, though annoying. Some possibility it may have
> been caused by a WindowsUpdate, possibly even one that was pushed onto my
> machine by the corporate IT people.
>
> The problem itself is that the computer complains about a new file version
> that it can't check. It doesn't reveal what file, and it doesn't actually
> say anything about a missing security certificate, but I'm pretty sure
> that's what's going on. The SFC fails to run, which is apparently related.
>
> I'm pretty sure that all of the root certificates have been restored, but
> either there is a missing certificate somewhere else, or it is some kind
of
> chain reaction thing.
>
> Anyone else having similar problems? Any suggestions about how to fix it?
> Diagnostic steps to identify the missing certificate or even the affected
> file?
>

The problem occurs during booting. Unfortunately, the exact error message is
in Japanese, and though I could copy it for you, I'm doubtful it would be
very helpful... My Japanese is far from perfect, but I'll try to describe it
as well as I can. During the boot, a popup window appears. It says that it
is unable to check the validity of a file (or certify the appropriateness or
compatibility?), and it asks me to insert the Windows 2000 Professional CD
so that it can copy an earlier version. No hint as to which file or exactly
why it doesn't like the version it has found. (Of course I have run a
variety of virus and spyware checks, and I think I can rule out that
possibility.)

In response to the error window, I can either insert the CD or cancel. If I
insert the CD, it apparently copies some file and the popup goes away. (The
newer "incorrect" version of the file is apparently restored from somewhere
at the time of the next boot.) If I cancel, then it gives me a confirmation
window where I can insist that it use the newer version, but still no
indication about the newer version of what.

I have tried various diagnostic measures such as getting a boot log (no
hints found) and reading all sorts of typically irrelevant pages on the
Microsoft Web sites. I had hoped that the SFC would identify the problem
(which is supposed to be the purpose of that program), but, as already
noted, it also refuses to run, and based on some of the information I read
on the Microsoft Web site, I believe that this is a related problem. The
error code is 0x000006ba, which will doubtlessly lead you to the same pages
I visited, but I followed the various recovery instructions without success,
which makes me think the real problem is some other file in a critical chain
is also missing. (Or based on the comment below, it is also possible that
this machine originally had a different version of a key root certificate.)

Perhaps this is a helpful diagnostic, but I think it is just a metric that
shows the problem is not so serious. Whatever file is failing to load, it
does not actually stop the boot. The machine continues booting, and I have
not noticed any crucial services that are disabled prior to getting rid of
the error message. I have also been unable to detect any difference between
using the CD or using the unverified newer file.

Roger Abell wrote:
> I have read, and reread, you entire posting.
> As far as I can tell, all that you have told us, aside from
> your suspected cause, is
> <quote>
> The problem itself is that the computer complains about a new
> file version that it can't check. It doesn't reveal what file
> </quote>
> That is not really very much to go on.
> When does this happen for example.
>
>> In http://support.microsoft.com/default...b;en-us;293781
>> there is the very interesting comment:
>>
>> "As you may have noticed in the provided information, some of the
>> certificates have expired. However, these certificates are necessary
>> for backwards compatibility. Even if there is an expired trusted root
>> certificate, anything that was signed with that certificate prior to
>> the expiration date needs that trusted root certificate to be
>> validated. As long as expired certificates are not revoked, it can
>> be used to validate anything that was signed prior to its
>> expiration."
>>
>> Oh! *NOW* you [Microsoft] tell me. Just too bad the information
>> wasn't provided earlier.
>>
>> Been wrestling with this problem for several weeks, and though I'm
>> not certain, I very strongly suspect that what happened is that I
>> deleted a required security certificate in the foolish belief that
>> the expiration date had some meaning. Quite trivial to do from IE:
>> Tools menu -> Internet Options command -> Content tab ->
>> Certificates button -> Trusted Root Certificates tab. Not certain
>> because it happened a while ago and the resulting problem is minor,
>> though annoying. Some possibility it may have been caused by a
>> WindowsUpdate, possibly even one that was pushed onto my machine by
>> the corporate IT people.
>>
>> The problem itself is that the computer complains about a new file
>> version that it can't check. It doesn't reveal what file, and it
>> doesn't actually say anything about a missing security certificate,
>> but I'm pretty sure that's what's going on. The SFC fails to run,
>> which is apparently related.
>>
>> I'm pretty sure that all of the root certificates have been
>> restored, but either there is a missing certificate somewhere else,
>> or it is some kind of chain reaction thing.
>>
>> Anyone else having similar problems? Any suggestions about how to
>> fix it? Diagnostic steps to identify the missing certificate or even
>> the affected file?

It seems to me this is not exactly a Microsoft or Windows problem, because
if you deleted your root certificates on any OS, you would have problems
with those certificates. What are you doing deleting root certificates
anyways? If you don't know exactly how it works, don't delete it.
Microsoft cannot possibly write an article about every single file and
object telling you not to delete it.

Anyways, I would try restoring those certificates and possibly rebooting.
See the "Method 8" section of this KB article.

http://support.microsoft.com/default.aspx/kb/822798?

It is generally not a good idea to cross-post to multiple groups, because
then your answer gets answered repeatedly in multiple groups.

--
regards,

Karl Levinson, MS MVP, CISSP
Microsoft Security FAQ:
http://securityadmin.info


"Shannon Jacobs" <> wrote in message
news:uH$rAxP$...
> In http://support.microsoft.com/default...b;en-us;293781 there is
> the very interesting comment:
>
> "As you may have noticed in the provided information, some of the
> certificates have expired. However, these certificates are necessary for
> backwards compatibility. Even if there is an expired trusted root
> certificate, anything that was signed with that certificate prior to the
> expiration date needs that trusted root certificate to be validated. As
long
> as expired certificates are not revoked, it can be used to validate
anything
> that was signed prior to its expiration."
>
> Oh! *NOW* you [Microsoft] tell me. Just too bad the information wasn't
> provided earlier.
>
> Been wrestling with this problem for several weeks, and though I'm not
> certain, I very strongly suspect that what happened is that I deleted a
> required security certificate in the foolish belief that the expiration
date
> had some meaning. Quite trivial to do from IE: Tools menu -> Internet
> Options command -> Content tab -> Certificates button -> Trusted Root
> Certificates tab. Not certain because it happened a while ago and the
> resulting problem is minor, though annoying. Some possibility it may have
> been caused by a WindowsUpdate, possibly even one that was pushed onto my
> machine by the corporate IT people.
>
> The problem itself is that the computer complains about a new file version
> that it can't check. It doesn't reveal what file, and it doesn't actually
> say anything about a missing security certificate, but I'm pretty sure
> that's what's going on. The SFC fails to run, which is apparently related.
>
> I'm pretty sure that all of the root certificates have been restored, but
> either there is a missing certificate somewhere else, or it is some kind
of
> chain reaction thing.
>
> Anyone else having similar problems? Any suggestions about how to fix it?
> Diagnostic steps to identify the missing certificate or even the affected
> file?
>

This is exactly the level of "support" I have come to expect from MVPs. Does
Microsoft have some sort of incentive program that requires you to say
something even if you have no idea what you are talking about?


Karl Levinson, mvp wrote:
> It seems to me this is not exactly a Microsoft or Windows problem,
> because if you deleted your root certificates on any OS, you would
> have problems with those certificates. What are you doing deleting
> root certificates anyways? If you don't know exactly how it works,
> don't delete it. Microsoft cannot possibly write an article about
> every single file and object telling you not to delete it.

I have already confessed my culpability for being stupid enough to believe
that the expiration date on a security certificate had any meaning. Well,
actually it should have a meaning because the concept of security is
fundamentally linked to time. However, if Microsoft chooses to ignore or
reassign meanings and just redefine things, that's the new de facto
standard, isn't it? My bad, mea culpa, and I admit I was a fool to trust
Microsoft. Are you satisfied now?

(However, I'm still not certain that this is the cause of the problem, nor
even certain exactly what the problem is.)


> Anyways, I would try restoring those certificates and possibly
> rebooting. See the "Method 8" section of this KB article.
>
> http://support.microsoft.com/default.aspx/kb/822798?

Done that. Didn't work. "Possibly rebooting." Damn. Why didn't I think of
that? Especially with regards to a boot-related problem. Shucks, still
didn't work.

Any more trivially obvious suggestions? Dare I say, trivially obvious to the
most casual observer?


> It is generally not a good idea to cross-post to multiple groups,
> because then your answer gets answered repeatedly in multiple groups.

No, you are incorrect again, but par for the current MVPs. Please read the
relevant RFC and the NNTP standards. The only notable exception is Mozilla,
which is well known to be handling cross-posting incorrectly, and which is
not even a Microsoft product.


> "Shannon Jacobs" <> wrote in message
> news:uH$rAxP$...
>> In http://support.microsoft.com/default...b;en-us;293781
>> there is the very interesting comment:
>>
>> "As you may have noticed in the provided information, some of the
>> certificates have expired. However, these certificates are necessary
>> for backwards compatibility. Even if there is an expired trusted root
>> certificate, anything that was signed with that certificate prior to
>> the expiration date needs that trusted root certificate to be
>> validated. As long as expired certificates are not revoked, it can
>> be used to validate anything that was signed prior to its
>> expiration."
>>
>> Oh! *NOW* you [Microsoft] tell me. Just too bad the information
>> wasn't provided earlier.
>>
>> Been wrestling with this problem for several weeks, and though I'm
>> not certain, I very strongly suspect that what happened is that I
>> deleted a required security certificate in the foolish belief that
>> the expiration date had some meaning. Quite trivial to do from IE:
>> Tools menu -> Internet Options command -> Content tab ->
>> Certificates button -> Trusted Root Certificates tab. Not certain
>> because it happened a while ago and the resulting problem is minor,
>> though annoying. Some possibility it may have been caused by a
>> WindowsUpdate, possibly even one that was pushed onto my machine by
>> the corporate IT people.
>>
>> The problem itself is that the computer complains about a new file
>> version that it can't check. It doesn't reveal what file, and it
>> doesn't actually say anything about a missing security certificate,
>> but I'm pretty sure that's what's going on. The SFC fails to run,
>> which is apparently related.
>>
>> I'm pretty sure that all of the root certificates have been
>> restored, but either there is a missing certificate somewhere else,
>> or it is some kind of chain reaction thing.
>>
>> Anyone else having similar problems? Any suggestions about how to
>> fix it? Diagnostic steps to identify the missing certificate or even
>> the affected file?

"Shannon Jacobs" <> wrote in message
news:O3y3iGc$...
> This is exactly the level of "support" I have come to expect from MVPs.
Does
> Microsoft have some sort of incentive program that requires you to say
> something even if you have no idea what you are talking about?
>
>

You can find more about the MVP title here:
http://mvp.support.microsoft.com/def...;EN-US;mvpfaqs

/Fredrik

On Tue, 18 Jan 2005 16:41:24 +0900, "Shannon Jacobs"
<> wrote:

>The problem occurs during booting. Unfortunately, the exact error message is
>in Japanese, and though I could copy it for you, I'm doubtful it would be
>very helpful... My Japanese is far from perfect, but I'll try to describe it
>as well as I can. During the boot, a popup window appears. It says that it
>is unable to check the validity of a file (or certify the appropriateness or
>compatibility?), and it asks me to insert the Windows 2000 Professional CD
>so that it can copy an earlier version. No hint as to which file or exactly
>why it doesn't like the version it has found. (Of course I have run a
>variety of virus and spyware checks, and I think I can rule out that
>possibility.)

Actually, you can't. This is a relatively recent spyware issue, and
easily resolved. Open the Task Manager and choose the processes tab.
Stop all processes you don't know, there aren't many that are required
and if you stop the wrong one you can always restart the system to
recover.

Once these are stopped, run the registry editor (regedt32 or regedit)
and find the key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Run

Remove all strange entries. You should recognize most of them anyway.
Once removed, restart the system. Also run through the Add/Remove
Programs dialog and clean out unrecognized or unwanted stuff.

Keep in mind that making changes to the registry can screw up your
system. If you're at all uncomfortable with this, call your IT
department (If they're security conscious they'll have prevented you
from editing the registry anyway...).

I haven't found a spyware removal tool that has fixed this issue, but
I've cleaned a half dozen systems in the last few days of his.

Disclaimer: If you're foolish enough to try suggestions from the
internet without verifying them, then you deserve whatever happens if
this hoses your system. Don't blame me since I'm specifically warning
you not to do what I suggest.

That said, you can easily figure out how to reach me and verify
credentials.

Jeff

>In response to the error window, I can either insert the CD or cancel. If I
>insert the CD, it apparently copies some file and the popup goes away. (The
>newer "incorrect" version of the file is apparently restored from somewhere
>at the time of the next boot.) If I cancel, then it gives me a confirmation
>window where I can insist that it use the newer version, but still no
>indication about the newer version of what.
>
>I have tried various diagnostic measures such as getting a boot log (no
>hints found) and reading all sorts of typically irrelevant pages on the
>Microsoft Web sites. I had hoped that the SFC would identify the problem
>(which is supposed to be the purpose of that program), but, as already
>noted, it also refuses to run, and based on some of the information I read
>on the Microsoft Web site, I believe that this is a related problem. The
>error code is 0x000006ba, which will doubtlessly lead you to the same pages
>I visited, but I followed the various recovery instructions without success,
>which makes me think the real problem is some other file in a critical chain
>is also missing. (Or based on the comment below, it is also possible that
>this machine originally had a different version of a key root certificate.)
>
>Perhaps this is a helpful diagnostic, but I think it is just a metric that
>shows the problem is not so serious. Whatever file is failing to load, it
>does not actually stop the boot. The machine continues booting, and I have
>not noticed any crucial services that are disabled prior to getting rid of
>the error message. I have also been unable to detect any difference between
>using the CD or using the unverified newer file.
>
>Roger Abell wrote:
>> I have read, and reread, you entire posting.
>> As far as I can tell, all that you have told us, aside from
>> your suspected cause, is
>> <quote>
>> The problem itself is that the computer complains about a new
>> file version that it can't check. It doesn't reveal what file
>> </quote>
>> That is not really very much to go on.
>> When does this happen for example.
>>
>>> In http://support.microsoft.com/default...b;en-us;293781
>>> there is the very interesting comment:
>>>
>>> "As you may have noticed in the provided information, some of the
>>> certificates have expired. However, these certificates are necessary
>>> for backwards compatibility. Even if there is an expired trusted root
>>> certificate, anything that was signed with that certificate prior to
>>> the expiration date needs that trusted root certificate to be
>>> validated. As long as expired certificates are not revoked, it can
>>> be used to validate anything that was signed prior to its
>>> expiration."
>>>
>>> Oh! *NOW* you [Microsoft] tell me. Just too bad the information
>>> wasn't provided earlier.
>>>
>>> Been wrestling with this problem for several weeks, and though I'm
>>> not certain, I very strongly suspect that what happened is that I
>>> deleted a required security certificate in the foolish belief that
>>> the expiration date had some meaning. Quite trivial to do from IE:
>>> Tools menu -> Internet Options command -> Content tab ->
>>> Certificates button -> Trusted Root Certificates tab. Not certain
>>> because it happened a while ago and the resulting problem is minor,
>>> though annoying. Some possibility it may have been caused by a
>>> WindowsUpdate, possibly even one that was pushed onto my machine by
>>> the corporate IT people.
>>>
>>> The problem itself is that the computer complains about a new file
>>> version that it can't check. It doesn't reveal what file, and it
>>> doesn't actually say anything about a missing security certificate,
>>> but I'm pretty sure that's what's going on. The SFC fails to run,
>>> which is apparently related.
>>>
>>> I'm pretty sure that all of the root certificates have been
>>> restored, but either there is a missing certificate somewhere else,
>>> or it is some kind of chain reaction thing.
>>>
>>> Anyone else having similar problems? Any suggestions about how to
>>> fix it? Diagnostic steps to identify the missing certificate or even
>>> the affected file?

"Shannon Jacobs" <> wrote in message
news:O3y3iGc$...
> This is exactly the level of "support" I have come to expect from MVPs.
Does
> Microsoft have some sort of incentive program that requires you to say
> something even if you have no idea what you are talking about?

Hey, you came here looking for free support. I spent a fair amount of time
looking for the KB article, only to have you complain about my "level of
support" and say you had already tried that. If you already tried it, tell
us what you've already tried so we don't waste our time and yours. I'm not
psychic.

> actually it should have a meaning because the concept of security is
> fundamentally linked to time.

No. When someone uses a PKI cert to sign a PGP email or a Windows 2000
file, that is not linked to time.

> However, if Microsoft chooses to ignore or
> reassign meanings and just redefine things, that's the new de facto
> standard, isn't it?

No. You still need certificates after they expire. This is true of many
PKI solutions including PGP, so it has nothing to do with Microsoft. Your
PGP emails, Windows 2000 files, etc. were signed with a cert that is now
expired, and the only way to verify the signing is to keep access to the old
certs. Not a MIcrosoft thing.

> My bad, mea culpa, and I admit I was a fool to trust Microsoft.

No, your mistake was to start deleting core OS stuff for no real reason I'm
aware of, without knowing how it works, then coming here and blaming MS,
saying MS should have warned you not to delete your root certificates
haphazardly, and that MS publishing a KB article on the subject is not
sufficient warning.

> Done that. Didn't work. "Possibly rebooting." Damn. Why didn't I think of
> that? Especially with regards to a boot-related problem. Shucks, still
> didn't work.
>
> Any more trivially obvious suggestions? Dare I say, trivially obvious to
the
> most casual observer?

No, I meant the MS article doesn't tell you this, but after using the KB
article to restore the certificates, you may possibly need to reboot. I
didn't think that rebooting would solve your problem, but that rebooting
might be necessary to see whether your problem was fixed... which is of
course a true statement, since the problem occurs at boot time. I hardly
think finding an article on how to restore your root certificates is a
trivially obvious suggestion. I'm not sure I believe you when you say that
you already tried restoring your root certificates using the KB article I
posted. If you had, the problem would probably be fixed. I suspect you
misunderstood the part about "possibly rebooting" and blew up before trying
out the KB article.

The KB article states that even though you deleted the root certificates
from your Windows certificate store, they are still contained in files on
your hard drive and can be restored from there.

> No, you are incorrect again, but par for the current MVPs. Please read the
> relevant RFC and the NNTP standards. The only notable exception is
Mozilla,
> which is well known to be handling cross-posting incorrectly, and which is
> not even a Microsoft product.

RFC 1855 says very little about cross-posting, and it is now at least nine
years old.

If you have such little respect for MVPs, why are you here looking for
support from them?

Anyways, if you haven't yet, try doing what I actually suggested:

http://support.microsoft.com/default.aspx/kb/822798?

Method 8: Verify the status of all certificates in the certification path
and import missing or damaged certificates from another computer
To verify certificates in the certificate path for a Windows or Internet
Explorer product update, follow these steps:
Step 1: Verify Microsoft certificates
1. In Internet Explorer, click Tools, and then click Internet Options.
2. On the Content tab, click Certificates.
3. On the Trusted Root Certification Authorities tab, double-click
Microsoft Root Authority. If this certificate is missing, go to step 2.
4. On the General tab, make sure that the Valid from dates are
1/10/1997 to 12/31/2020.
5. On the Certification Path tab, verify that This certificate is OK
appears under Certificate Status.
6. Click OK, and then double-click the NO LIABILITY ACCEPTED
certificate.
7. On the General tab, make sure that the Valid from dates are
5/11/1997 to 1/7/2004.
8. On the Certification Path tab, verify that either This certificate
has expired or is not yet valid or This certificate is OK appears under
Certificate Status.

Note Although this certificate is expired, it will continue to work.
The operating system may not work correctly if the certificate is missing or
revoked.

For additional information, click the following article number to view
the article in the Microsoft Knowledge Base:
293781 Trusted root certificates that are required by Windows 2000,
Windows XP, and Windows Server 2003
9. Click OK, and then double-click the GTE CyberTrust Root
certificate. You may have more than one of these certificates with the same
name. Check the certificate that has an expiration date of 2/23/2006.
10. On the General tab, make sure that the Valid from dates are
"2/23/1996 to 2/23/2006."
11. On the Certification Path tab, verify that This certificate is OK
appears under Certificate Status.

Step 2: Import missing or damaged certificates
If one or more of these certificates are missing or corrupted, export the
missing or corrupted certificates to another computer, and then install the
certificates on your computer. To export certificates on another computer,
follow these steps: 1. In Internet Explorer, click Tools, and then click
Internet Options.
2. On the Content tab, click Certificates.
3. On the Trusted Root Certification Authorities tab, click the
certificate that you want to export.
4. Click Export, and then follow the instructions to export the
certificate as a DER encoded Binary x.509(.CER) file.
5. After the certificate file has been exported, copy it to the
computer where you want to import it.
6. On the computer where you want to import the certificate,
double-click the certificate.
7. Click Install certificate, and then click Next.
8.
Click Finish, and then click OK.


[... and then possibly you may need to reboot for the changes to fully
take effect. The MS article didn't say this, so I added it.]

It is true that there is relatively new malware on the Internet that deletes
or inhibits your access to your root certificates. If you didn't delete any
of your root certificates that pertain to Windows file checking, this may be
the problem. The article I posted tells you how to check to see whether the
root certificates related to Windows file checking are missing.


"Jeff Cochran" <> wrote in message
news:...

> Actually, you can't. This is a relatively recent spyware issue, and
> easily resolved. Open the Task Manager and choose the processes tab.
> Stop all processes you don't know, there aren't many that are required
> and if you stop the wrong one you can always restart the system to
> recover.

"Shannon Jacobs" <> wrote in message
news:O3y3iGc$...
> This is exactly the level of "support" I have come to expect from MVPs.
Does
> Microsoft have some sort of incentive program that requires you to say
> something even if you have no idea what you are talking about?

The incentive is that we get to do this for free and get the benefit of
putting up with a thankless public in the process.

> > Anyways, I would try restoring those certificates and possibly
> > rebooting. See the "Method 8" section of this KB article.
> >
> > http://support.microsoft.com/default.aspx/kb/822798?
>
> Done that. Didn't work. "Possibly rebooting." Damn. Why didn't I think of
> that? Especially with regards to a boot-related problem. Shucks, still
> didn't work.

Did you actually read the article?

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com