"A Cabinet file cannot be trusted" - Why?

Dear 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

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!!

Jenna, 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

Found 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
if 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!

This 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

you are agoddess jenna even for a noob like me i was able to perform the repair,would really like to show my appreciation by sending you a gift card you save me time and money,seriously,ive set up a temporary emai,elcapitan3395 on yahoo,its only fair that you be rewarded and to show my appreciation

thanks a lot. i manage to install the directX in my laptop. the info here really help a lot.

Thanks to the Comment from "iggy". That was exactly, what helped to fix the problem in just 2 Minutes (after trying to find a solution for a few days)...... Thanks a lot !

Chad's comment is truly right and correct!! :D
To go to logs Click Start, then Click run, and type logs!