Summary: There are many things that can lead to the error "A Cabinet file cannot be trusted". I'll review the steps I'd take to track down the problem.
|
"A Cabinet file cannot be trusted" - Why? |
"A Cabinet file necessary for the installation cannot be trusted" is actually the full message, and it results most commonly when folks are attempting to download DirectX 9.0c for use with a new game, commonly "The Sims 2".
Wow. Forget all the business uses of computers ... just don't get in between a person and their game. Lots of questions, and no shortage of emotion to be found on this topic.
•
Unfortunately, in my research I've not been able to find the One True Answer. But the problem seems to be reasonably well understood, and there are a ton of things to try. Unfortunately, many of them are not simple.
The problem arises out of Microsoft's attempts to improve the security of Windows. The software is attempting to use digital signatures to verify that what you're installing is what you think it is and not some virus, trojan horse, or other malware.
When it fails, here are things to try, in the order that I would try them:
Re-download the component you're attempting to install, from a trusted source. For example go to Microsoft's site for the latest DirectX download.
I know you're tired of hearing it, but it applies here also: scan for spyware and scan for viruses. Make sure that the databases you use for each tool are as up-to-date as possible. There have been reports of this kind of problem being related to spyware or viruses.
Under Windows XP, ensure that the Cryptographic Services are enabled and running:
- Right-click on My Computer
- Click on Manage
- Expand Services and Applications
- Click on Services
- Right-click on Cryptographic Services
- Click on Properties
- Set the Startup type to Automatic
- OK and close your way back out.
Ensure that you are up-to-date with Windows Service Packs. There are apparently specific fixes in the service packs that relate to the cryptography service and could result in its failure. I recommend enabling Automatic Updates as well.
Run chkdsk or scandisk on your Windows drives. Certain types of file corruption can result in this problem.
Run the System File Checker under Windows XP to detect and repair any corruption or system irregularities.
On Windows 9x (95, 98 and Me), hit Start, Run, and run the command "scanreg.exe /fix".
Review the two Microsoft Knowledgebase articles listed below. They have a long list of steps that may help resolve the issue.
Perform a Repair installation of Windows, as outlined in How to Perform a Windows XP Repair Install.
Some resources I encountered and from which some of the suggestions above were gleaned:
A comprehensive guide on fixing Cryptographic Service Errors
Microsoft Knowledgebase: Detecting Digital Signing Issues in Windows XP
Microsoft Knowledgebase: You cannot install some updates or programs
This thread on DirectX and SP2 problems out on ntcompatible.com
A thread in microsoft.public.directx.misc entitled "The cabinet file cannot be trusted (DirectX 9.0)/Service Pack2"
A thread in microsoft.public.directx.misc entitled "cabinet file cannot be trusted"
The bottom line is that yes, this is a royal pain, and no, it shouldn't have to be this way. As I said at the outset, there's apparently no One True Solution, no simple tweak, that will make this problem go away. I've prioritized the steps I'd take above so that hopefully your issue will get resolved after a few easy steps.
Take your time and try not to get frustrated (OK, try not to get too frustrated).
Good Luck!
Related:
-
Ask Leo! - How can I uninstall DirectX 9?
-
Ask Leo! - Why can't I get The Sims 2 to work on my machine?
-
Ask Leo! - What's the best Pop-Up Blocker? Anti-Virus Software? Anti-Spyware Software?
Article C2277 - February 6, 2005
If you still have trouble with Cryptographic services go to:%systemroot%\system32\directx folder and delete Websetup folder and that is it!! I did everything and the services were running fine but I still couldn't start a game, and when I deleted that folder it worked like a charm!!
Posted by: Jonji at October 15, 2008 2:35 PMIt Works...!!! Thanks
Posted by: Leonard at December 8, 2008 9:54 AMI actually had this problem installing DirectX 10 on on Windows Vista. After trying everything listed here (except the repair) and still no dice, I did one more google search and figured out my problem and it was alot simpler than I thought...
I didn't have internet access (well kinda). I was installing it on a machine inside my corporate network. In order for any machine to gain access to the internet while on my network, you must authenticate with the firewall. For most users this automatically happens when you go to a website because the machine is added to the domain and the Windows account on the computer is authenticated against the domain controller. However, in this case, I had not connected to the internet by going to a website so the computer techically did not have access to the internet.
Had I been doing a search on the internet for the problem from the machine that was experiencing the problem, I would have been prompted to authenticate and I wouldn't have seen the problem, but I was searching the internet for the problem from my machine since the machine experiencing the problem was only a test machine and hadn't been added to my domain yet. I got lazy and did one last final search but this time from the computer with the problem (because I didn't want to go back to my computer) and when prompted to log into the firewall, it hit me.
So why did the machine need access to the internet? This was because the DirectX setup file is actually a 200 KB (approx) file that then connects to the internet to download the rest of the setup files.
So if anyone comes across the post later, I figured I would share my experience and give one other thing to check, just in case it is something silly like that I ran into.
Hope it helps!!
Sean
Posted by: Sean Lannigan at December 20, 2008 10:48 AMI did what Chad suggested, because so many other people had said it worked for them. But every time I re-ran the DirectX install, the corrupt files that I deleted were equally un-trustful...
So I ended up deleting the same file like 100 times only to have it re-installed :(...
Anyone know what I might doing wrong?
Posted by: Andrew at January 10, 2009 4:01 PMDear Leo,
I've had my computer for 6 years and never ever once in all those years have I ever had usde any space at all on my D drive.
Just about 3 weeks ago after I defragged which I usually do once every week and always have I noticed NOW my D Drive is filled up to 31 percent.
My question is how did that happen?
My C Drive is filled up to 32 percent but the C drive is the one that's always been full over the 6 years with some sort of percentage.
I'm wondering how do I find out what is on my D Drive for why just recently it had became full 0f 31 percent of what ever is on there. Is there a way to find out what is on my D Drive at all?
and should I or could I delete the space percentage and make it go back to 0 like it was for many years? How would I be able to do this?
Thank You very much for your time and consideration.
I hope you are able to answer my few questions in my time ofneeded help!
Sincerely,
Carolyn
16-Jan-2009
This error plagued me through a reformatting, safe mode, and everything else I could think of. I went through everything on the list aside from repairing Windows.
What finally worked: Do a search for "DirectX" and go under the log file. Scroll all the way down, and towards the end it will tell you what exact file is not being verified. Then, go to C drive, WINDOWS, System32, DirectX. Go to Tools, Folder Options, and View and show your hidden files. Go to websetup. Find the file that cannot be verified, as stated in the Log. MOVE it to an empty folder made on your desktop (right click, new, folder). Don't delete anything in System!!! Just move it out of the folder, and try again. DirectX DL will automatically replace the lost file.
I got another error. Turns out I had another bad file. I moved it to the other folder as well, and tried again. And it finally worked!!
Posted by: Jenna at March 17, 2009 5:33 PMJenna, you are the bomb!!!! i'm been trying to install this for a least a week. your method worked the first time around Thanks and may God be with you!!!1
Posted by: Karl Gordon at May 19, 2009 7:52 PMFound this somewhere.
Download directx websetup here (March 2009) http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3
1. navigate to \Windows\System32\directx\ or \Windows\SysWow64\directx
Posted by: Imran Arif at June 7, 2009 6:40 AMif you have vista x64.
2. Click on "organise" file menu, then "folder and search options" then
in the "View" tab check "show hidden files and folders" and then "ok"
3. websetup folder will be visible now. go in there and delete all
contents.
4. run "dxwebsetup" again.
Works for me under Vista 64bit.
Thanks Jenna!!! Your method really worked and I had no trouble following your clear instructions for a newbie like me, although I had to delete 4 bad files before I am able to download DirectX 10. Thanks once again!
Posted by: Jingle Yew at July 17, 2009 8:09 AMThis worked great! Thanks Jenna
This error plagued me through a reformatting, safe mode, and everything else I could think of. I went through everything on the list aside from repairing Windows.
What finally worked: Do a search for "DirectX" and go under the log file. Scroll all the way down, and towards the end it will tell you what exact file is not being verified. Then, go to C drive, WINDOWS, System32, DirectX. Go to Tools, Folder Options, and View and show your hidden files. Go to websetup. Find the file that cannot be verified, as stated in the Log. MOVE it to an empty folder made on your desktop (right click, new, folder). Don't delete anything in System!!! Just move it out of the folder, and try again. DirectX DL will automatically replace the lost file.
I got another error. Turns out I had another bad file. I moved it to the other folder as well, and tried again. And it finally worked!!
Posted by: Jenna at March 17, 2009 5:33 PM
Posted by: Gabriel at September 24, 2009 8:23 AM