How big is your windows folder?


Recommended Posts

so far, i do believe that i'm winning :D

http://oak.cats.ohiou.edu/~as243599/Images/windoze.png

if that pic turns into a red x, my windows folder is 610MB (588MB = size on disk), and i'm using xp pro w/sp1

Nice :p

What else did you delete?

everything that you did (though i kept IE for windowsupdate.com), except i also got rid of the ServicePackFiles folder (it's all backups), all the old C:\Windows\Installer info (i don't install much that i don't intend to keep) and i routinely go through and flush out about 75% of the *.log files on C:

gotta be careful with the .log files though - some are pretty important. most just get re-created as needed, though.

if you want something that'll help in your trimming-down pursuits, google for SequoiaView - it gives a graphical view of what's on your HD. it definitely helps you see what is taking up the most space, like this:

so far, i do believe that i'm winning :D

http://oak.cats.ohiou.edu/~as243599/Images/windoze.png

if that pic turns into a red x, my windows folder is 610MB (588MB = size on disk), and i'm using xp pro w/sp1

Nice :p

What else did you delete?

everything that you did (though i kept IE for windowsupdate.com), except i also got rid of the ServicePackFiles folder (it's all backups), all the old C:\Windows\Installer info (i don't install much that i don't intend to keep) and i routinely go through and flush out about 75% of the *.log files on C:

gotta be careful with the .log files though - some are pretty important. most just get re-created as needed, though.

if you want something that'll help in your trimming-down pursuits, google for SequoiaView - it gives a graphical view of what's on your HD. it definitely helps you see what is taking up the most space, like this:

I have gone thruogh all the log files and dont have a servicepackfiles folder because this is a slipstreamed install :p

that sequia view is one cool program. down to 719 also...any ideas with the inf files? or files from programs i dont have anymore, what should i look for?

btw, ive noticed my computers running quite a bit faster :D

Yeah, that program is nice, I am going to keep it :p

I have also noticed my computer being faster, with less files to keep track of, windows works better :p

that sequia view is one cool program. down to 719 also...any ideas with the inf files? or files from programs i dont have anymore, what should i look for?

btw, ive noticed my computers running quite a bit faster :D

you can get rid of the entire c:\windows\inf folder, if you don't add hardware very often.

personally, i don't upgrade very often, so i just deleted the entire folder. if you do that, though, have your xp cd ready whenever you add some new components.

After deleting dllcache.

I restarted the PC.

Then Windows needed a re-activation.

After that I discovered that the dllcache folder is rebuilt. :blink: :blink:

don't delete the dllcache folder

just the content of it, and files will be returning to it

Can someone post a list of the "safe-to-kill" folders identified so far?

if you're able to disable WFP (windows file protection), you can delete all this stuff:

*cut and pasted from another forum i moderate*

here's what i wipe out (but keep backed up on cd):

c:\windows\cursors\

c:\windows\downloaded installations\

c:\windows\driver cache\i386\

c:\windows\help\

c:\windows\inf\

c:\windows\installer\

c:\windows\media\

c:\windows\registeredpackages\

c:\windows\servicepackfiles\i386\

c:\windows\system32\dllcache\

c:\windows\system32\reinstallbackups\

c:\windows\system32\restore\

c:\windows\system32\usmt\

c:\program files\msn

c:\program files\netmeeting\

c:\windows\$Uninstall----$

the $uninstall----$ folders are used whenever you want to uninstall a windows update. i don't see any point in keeping them.

also, go through the start menu and find things you don't want (stuff in the Accessories folder) - find the programs those shortcuts link to and delete as necessary.

notes:

1) keep the directories - just delete/move the files inside

2) do this after you've installed *all* hardware, including webcams and virtual cd-rom drives, and updated all service packs/ updates.

i find little things here and there, but that's normally the stuff i go through and wipe out right after a fresh install.

Can someone post a list of the "safe-to-kill" folders identified so far?

if you're able to disable WFP (windows file protection), you can delete all this stuff:

*cut and pasted from another forum i moderate*

here's what i wipe out (but keep backed up on cd):

c:\windows\cursors\

c:\windows\downloaded installations\

c:\windows\driver cache\i386\

c:\windows\help\

c:\windows\inf\

c:\windows\installer\

c:\windows\media\

c:\windows\registeredpackages\

c:\windows\servicepackfiles\i386\

c:\windows\system32\dllcache\

c:\windows\system32\reinstallbackups\

c:\windows\system32\restore\

c:\windows\system32\usmt\

c:\program files\msn

c:\program files\netmeeting\

c:\windows\$Uninstall----$

the $uninstall----$ folders are used whenever you want to uninstall a windows update. i don't see any point in keeping them.

also, go through the start menu and find things you don't want (stuff in the Accessories folder) - find the programs those shortcuts link to and delete as necessary.

notes:

1) keep the directories - just delete/move the files inside

2) do this after you've installed *all* hardware, including webcams and virtual cd-rom drives, and updated all service packs/ updates.

i find little things here and there, but that's normally the stuff i go through and wipe out right after a fresh install.

Cool, that is about all that I deleted, but I left most of the INF stuff and the drive cache :p

just look inside them - if it looks like something critical to your computer (ie, lists of hardware, etc), leave it

inside the catroot2 folder, you'll see some called edb000001.log, edb000002.log, and they'll probably be exactly 5MB each - you can zap those, because they're just taking up space and will get recreated when they're needed

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
    • OpenAI is making Codex more useful in Chrome and the cloud by Pradeep Viswanathan OpenAI's Codex now has more than 5 million users, up nearly 4x from earlier this year. To further accelerate Codex's growth among developers, OpenAI today announced that it has agreed to acquire Ona, a company that builds secure cloud execution and orchestration technology for developers. Ona will enable developers to run Codex with persistent and controlled cloud infrastructure for long-running agentic workflows. Right now, most Codex execution happens locally on developers' laptops and PCs, and the agents work continuously for hours. Through Ona, OpenAI aims to make Codex agents keep working for days without being tied to a user’s local machine or an active session. This will be an important capability for enterprises that want to deploy AI agents in production while maintaining control over infrastructure, data, security boundaries, credential scope, logging, and review workflows. Like any acquisition, the deal is still subject to customary closing conditions, including regulatory approvals. Until the deal closes, OpenAI and Ona will continue to operate as separate companies. After closing, Ona’s team will join the Codex team to improve developer workflows. Alongside the Ona acquisition announcement, OpenAI today introduced a few Codex updates. Developers can now save Codex rate limit resets and use them later instead of losing them when they are not needed immediately. OpenAI is also adding a referral option where users can invite a friend to Codex and get a saved rate limit reset. OpenAI today also announced a developer mode for browser use in Chrome and the Codex in-app browser. With this mode, Codex can use the Chrome DevTools Protocol to debug web apps, inspect pages, and work more directly with browser-based development workflows. Developers can use this when they want Codex to profile JavaScript, inspect console output and network traffic, examine web page states including the DOM and applied styles, and more.
  • Recent Achievements

    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
    • One Year In
      slackerzz earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      509
    2. 2
      PsYcHoKiLLa
      186
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!