Windows Folder is Huge-40GB

[richc46]

After you tried everything and are ready to give up, just use a system restore from before the change.
http://www.vistax64.com/tutorials/76905-system-restore-how.html

But I would use it as a last resort.

 

[jp07764]

Unhide your files as instruced and go to the windows folder
and in the search box type .old all the files with that should come
up in the search.
Also have you tried the build in disc cleaner?

Jimmy

 

[jp07764]

Found this in a google search
Windows Folder is Huge-40 GB - CNET Windows Vista Forums

It might help you.

Jimmy

 

[jefftate]

I downloaded TreeSize and found out that now "ManifestCache" is my largest file, coming in at over 30GBs. I have never been able to download Service Pack 1 (always an error) and I get the feeling that these two things are related. Thoughts?

 

[niemiro]

I downloaded TreeSize and found out that now "ManifestCache" is my largest file, coming in at over 30GBs. I have never been able to download Service Pack 1 (always an error) and I get the feeling that these two things are related. Thoughts?

Hello!

ManifestCache as a file? Do you mean the single .bin file in C:\Windows\winsxs\ManifestCache? What error are you getting when you try to install SP1? Thanks!

Richard

 

[jefftate]

Niemiro,

That's right...the file is under winsxs. I'm assuming service pack 1 would fix this glitch, since, I think, that other people have had this problem.

I don't know where this leaves me, because I can't even try to manually install service pack 1 now, since ManifestCache is taking up all the space. And I can't delete it.

...I might just have to buy a Mac.

 

[jp07764]

You could always backup your stuff and
do a clean install.

In less you really want to pay $1500.00
for a mac.

Jimmy

 

[Jody Thornton]

It's a log file for when you install or remove a feature using the Windows Add and Remove Features dialog. Sometimes the program errors out saying, "Not all selected components were able to be added and removed". In your event viewer right afterwards, you'd see that there are issues with setting installed packaged to an "installed" state. This is the error log file.

Should be able to delete it.