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

    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
    • I think he means you haven't reviewed previous UFC games. Of course it doesn't matter... Every time you just report on something that involves the President even if just simply what happened you guys usually get accused of being anti-Trump. We live in fun times.
  • Recent Achievements

    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
    • Week One Done
      agatameier earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      77
  • Tell a friend

    Love Neowin? Tell a friend!