Home »
Windows
»
Windows Oddities
Read the article that everyone's commenting on.
Subscribe to the RSS Feed for comments on this article.
The post by Chad at January 15, 2008 07:00 AM worked ... Thanks a lot
Posted by: ak at June 6, 2008 5:46 AMI have been searching off and on for a solution to this directX problem for almost a year!!Finally I found this site and read these comments, Thanx Chad it worked perfectly. And thank you Leo for this great site!
Posted by: Shell at June 14, 2008 8:13 PMchads way worked for me just perfectly, thanks!
Posted by: Brandon at June 16, 2008 8:12 PMYou are the man!! Well done!! I did it!! FINALY
Posted by: Bole at August 14, 2008 8:52 AMI was havind the same problem installing DirectX 10. Followed Chad's advice and it worked like a charm. Thanks!!!
Posted by: Jim at September 9, 2008 5:31 PMfor windows vista, the direct x log is in c:/windows/logs
but an easier way instead of looking at the log, is just to delete all of the .cab files in the direct x folder, and reintalling direct x from the windows site. i had multiple crypt. issues, so i just erased them all and it worked fine!
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 PMTo post a comment on ""A Cabinet file cannot be trusted" - Why?", please return to that article's main page.