Great. Taking you at your (poorly written) word, you are technically
competent and polite, and claim to have read and understood all of this
discussion. Therefore it was obviously an oversight that you forgot to
answer the technical question:

How can missing security certificates be identified (and replaced)?

I forgive you your unfortunate lapse, and look forward to your enlightening
answer. We're heard the talk, now let's see the walk.

By the way, the problem is rather more serious than I initially thought.
Turns out that all of the other Windows 2000 machines I was able to test
also have the problem (of apparently missing security certificates). I gave
up counting after 30 unverified files on the last one. The Windows XP
machines don't reveal the problem when running SFC, so I'm not really sure
what it means, apart from the obvious inability to know if the Windows 2000
is running valid files or has been hacked. That isn't a very large sample,
but perhaps this post may elicit some other reports?

For the moment, I suspect this is a typical Microsoftian
security-by-obscurity-whoops problem. That explains why the visiting
Microsoftian had no technical contribution to the thread. He probably knows
the answer, but he doesn't want to talk about it in public. Or perhaps it's
just yet another example of Microsoft's forced migration/upgrade strategy?
We can even dream that one of this week's numerous security patches will fix

Yet again by the way, I find your (Mr. Dilley's) projection on the "lack of
maturity" issue so funny that I'm reposting this reply in a few other forums
for wider amusement. Given the state of the newsgroups these days, I have
little hope of a technically accurate answer, but at least you're
entertaining. Your advice to the project managers is especially hilarious
and amusingly timed, but I'm not actually interested in playing your pro/ad
hominem games.

[And how about using a spelling checker? I'm not making an issue of it, but
it's yet another matter of politeness to the readers.]

Rick Dilley wrote:
> Shannon,
> I have read this entire thread with great interest.
> Unfortunately I find you lacking in class, maturity, and common
> courtesy...possible technical competence as well.
> I did not see any mention of your technical background and level of
> responsibility for your "own" computer, but you did mention that
> your company's IT department MAY have caused or contributed to the
> problem.
> In every installation that I have consulted at over the last 23
> years and the preceeding 12 years in corporate IT, there were
> always users that wanted to delve deeply into technical problems
> and assist in the solutions.
> Unfortunately those same pseudo-technologists had other corporate
> responsibilities that they ignored to "fiddle" with their
> computer...
> SO.... in my , occasionally humble, opinion you probably should
> have had the corporate IT department fix your self-created problem
> and gone about selling life insurance or whatever it is that you do
> to create profit for your company.
> Your drum-beat of criticism of the MVP's personally and as a group
> is NOT shared by the MSNG community.
> As in all things published here, a reader MUST:
> 1. read
> 2. understand
> 3. formulate a plan
> 4. provide a fall-back option
> 5. finally, implement at you own risk
> I believe that my 35 years in this IT merry-go-round qualifies me
> to say that you did not follow any of those 5 steps.
> Stand up, be a man , and take your messed up and
> really do not seem qualified to be doing anything but USING a
> computer....
> If you were on any of the networks that I currently support, your
> desktop would be "locked-down" tight specifically because you seem
> to think a lot of your abilities.
> To the MS NG community, I humble appologize for Shannon and the
> rest of us mere mortals, I have personally used the MS news groups
> for many and varied issues and am very pleased with the information
> I receive here.
> Please continue to receive our stupid posts and be patient with the
> loud-mouth idiots like Shannon.
> RickD
> "Shannon Jacobs" wrote in message
> news:eBqjHEp$EHA.3592@TK2MSFTNGP09.phx.gbl...
>> Actually I read so many of Microsoft's articles that I cannot
>> swear for certain whether or not I read that particular one.
>> However, I do remember doing the steps that were recommended
>> there, though they may have been from another similar article. I
>> did find a solution, though not from Microsoft. Here it is:
>> As already noted, I can only congratulate Microsoft for their
>> success in destroying yet another free support resource (the MVP
>> program of some years ago) and I continue to wish I had the option
>> the abandon Microsoft.
>> Phillip Windell wrote:
>>> "Shannon Jacobs" wrote in message
>>> news:O3y3iGc$EHA.1260@TK2MSFTNGP12.phx.gbl...
>>>> 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.
>>>> 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?