"A Cabinet file cannot be trusted" - Why?

All these ways of evading "cannot be trusted" are
for Windows XP. But I have Windows 2000 Pro, and in trying to install Google Earth, where DirectX 9.0 is required, I get the "Cannot be trusted -- Download failed" msg. 2000 has no Cryptographic Services link, so that first procedure can't work.
What now, brown cow? If Leo or someone else can tell me, I'll gladly buy Leo a Latte! DavidK

Actually many of the steps work, or have equivalents, on Windows 2000. Admittedly not all, but most.

Actually, the Download of DirectX 9.0 was entirely successful. It's the INSTALLATION that failed because "A cabinet file necessary for installation cannot be trusted." No one seems to offer a solution I can try. Remember, I'm using Win 2000 Pro, not XP. 2000 has no "cryptographic
services" to click on, so that's out. Leo, I still have your Latte waiting. David K.

I've not been able to lcoate anything Win2000 specific ... this is the closest: http://support.microsoft.com/kb/281458/

I recently down loaded DirectX 9.0 and now cannot load most of my game rooms, especially pogo. When trying the computer does nothing but lock up. Microsoft is of no help at all.

Hey iggy
Thanks a bunch .I tried the other suggestions like running scandisk,sfc /scannow but it didn't work until i re-registered the files. Thanks for the post

Hey

At first I was getting the cabinet file cannot be trusted when attempting to upgrade from 9.0b to 9.0c. I eventually fixed that, but now I'm being told that ati2dvag.dll is not digitally signed. I've attempted to fix the .dll drivers in command prompt but this didn't not fix it. Help?

Iggy,

thank you a thousand times, and then a thousand times again.
Directx finally installed...
thank you :) (that's 2001 times now :) )

Pepz

Hi

I tried loading Need for Speed undergound Most Wanted and Ive tried evrything mentioned above nothing worked on my Windows, i tried MS site and apparently it gave me some problems complaining about the MS Version i had, i then decided to roll back my dxdiag to a previous version and then update that never worked to. I finally fixed the problem by Loading Service pack 2 for windows.

Iggy,

Thank you so much, I have been trying to fix this for some time and I even skimmed this article to no avail. I looked at the comments today and it worked.

Thanks again.