Windows 7 taking too much space?

iRage

Member
Feb 11, 2011
46
0
0
Hey everyone, I had to install Windows Vista on my SSD in order to later do a clean install of Windows 7 Pro 64-bit. Now, after Windows 7 installed on my SSD, I only have 76.6 GB out of 111 GB available, is this accurate or is something going on? I didn't think Windows 7 would take 34.4 GB of space, otherwise I might have chosen a 250 GB SSD instead of 120.
 

Cerb

Elite Member
Aug 26, 2000
17,484
33
86
Page file size?
Hibernate file size?

If you have 8GB RAM (or more) and a typical several-GB page file, 30+GB is about right. You can disable hibernate and save a good bit, and either disable or manually reign in the page file.

Also, check under c:\ for leftover update directories (long alphanumeric directory names).

Finally, see how much space update uninstall files, and system restores, are taking. If taking up a good bit, remove some of the older ones (IMO, system restore is handy in Vista and 7, so I wouldn't go disabling it).

I have read that it's possible to get Win 7 under 20GB, but I haven't bothered trying to get it quite that small.

Oh, yeah, forgot about that: delete Windows.old.
 
Last edited:

aceO07

Diamond Member
Nov 6, 2000
4,491
0
76
On my Windows 7 Pro 64bit installation, the Windows folder only takes 8GB.

When you do an install over Vista, W7 will keep the old Windows folder (and Program Files folders?). It's renamed to be 'Windows.old', but it's hidden. Just change the explorer settings to show hidden folders/files and you'll see it.
 

docp

Senior member
Jul 4, 2007
206
0
76
i think of using vlite or something similar do we can get rid of windows media files,useless old drivers,language packs and what not to go even low on install folder.
i used to do for vista,have not tried for 7.
 

taltamir

Lifer
Mar 21, 2004
13,576
6
76
vlite wouldn't help much. as Cerb and aceO07 already mentioned, the OS directory itself is only 8GB... but there are gigs and gigs of other stuff hanging about.

8GB of RAM means 8GB pagefile and 8GB hibernate file by default. Those things add up. Even with 4GB of ram its 4 + 4 = 8 just for those 2 files. Add system restore...
just follow cerbs advice, if you must. Personally I just let windows take up that space. Its not like I need it. Seeing as you have 76.6GB of free space it doesn't seem like you need it either.
 

gevorg

Diamond Member
Nov 3, 2004
5,070
1
0
As already said, its probably due to 8GB RAM, so disable hibernation and reduce pagefile if you don't use it.

If you want to free a few gigs or so, use this (vlite doesn't support W7):

http://www.rt7lite.com/

You can also move the WinSxS folder, but its a pain.

This is mostly for folks with 40GB boot drives. I wouldn't bother with 120GB drive.
 

ahenkel

Diamond Member
Jan 11, 2009
5,357
3
81
um if he installed vista then 7 doesn't Vista leave it self behind. I believe you can delete the OLD OS install and that should gt you a big chunk of space
 

Binky

Diamond Member
Oct 9, 1999
4,046
4
81
A bare minimum Win7 32 bit install would take at least 15gb or so. A 64 bit install is slightly larger. I have an HTPC machine with a very minimal 64 bit Win7 installation and the entire C drive is about 26GB (7.4gb is pagefile and hibernate). That's probably a good indication of a minimum workable Win7 installation size with very little apps/stuff/crap installed.

Your 34GB install size doesnt seem very out of the ordinary.
 

techs

Lifer
Sep 26, 2000
28,559
4
0
fyi my Windows 7 Pro 64bit 4 Gb.RAM, which includes Office 2010 Pro, Avast Antivirus, the usual Adobe ReadeR, Java ,Shockwave, Flash, Firefox, Silverlight and VideoLan Player used about 17 gigs immediately after install.

However, I disable indexing, system restore and changed the Windows managed page file from 3 gigs to a set 2 gigs.

So, that should be a rule of thumb for you.
 

Voo

Golden Member
Feb 27, 2009
1,684
0
76
A bare minimum Win7 32 bit install would take at least 15gb or so. A 64 bit install is slightly larger.
Considering that my Windows folder (don't think there's any large stuff besides pagefile and hibernate outside that folder) on Win64bit Professional SP1 (installed since 7/2009 or something like that) is only 13gb - without using vlite or something -, I wager you can do with less (obviously that's without counting hibernate and pagefile but it's easy to get rid of those).
 

THizzle7XU

Junior Member
Mar 30, 2011
17
0
61
um if he installed vista then 7 doesn't Vista leave it self behind. I believe you can delete the OLD OS install and that should gt you a big chunk of space

Ya, it sounds like there could be a Windows.old folder sitting on the SSD. Even if it's a clean install, the previous OS folder is still kept around if you install it over an existing Windows install.
 

Drsignguy

Platinum Member
Mar 24, 2002
2,264
0
76
fyi my Windows 7 Pro 64bit 4 Gb.RAM, which includes Office 2010 Pro, Avast Antivirus, the usual Adobe ReadeR, Java ,Shockwave, Flash, Firefox, Silverlight and VideoLan Player used about 17 gigs immediately after install.

However, I disable indexing, system restore and changed the Windows managed page file from 3 gigs to a set 2 gigs.

So, that should be a rule of thumb for you.

Yup, I have the close to the same...Also to add, I have SP1 installed to and it shot it to grand total of 19gigs..

What I did was, I removed all drives except SSD (C300 128GB) added an older 160 Gb HDD with Xp installed on it and upgraded to a "custom" clean windows 7 install on the SSD. Went Perfect!
 

Auric

Diamond Member
Oct 11, 1999
9,591
2
71
If rolling back to pre-SP1 is not desir'd then run:

DISM /online /cleanup-image /spsuperseded

My W7-64 SP1 with gobs of proggies and their installers consumes 16GB. Of course pagefile is 16MB, and restore limited to 100MB. And yeah, hibernation is more appropriate for notebooks (if anything) rather than desktop where suspend with wee constant power is available.
 

catilley1092

Member
Mar 28, 2011
159
0
76
On my 32 bit notebook, Win 7 SP1 only uses 18GB of drive space, and that was after installing my programs, and NOD32.

Use CCleaner to get rid of what you don't need, there are many temp system files that you no longer need.

Cat
 

taltamir

Lifer
Mar 21, 2004
13,576
6
76
If rolling back to pre-SP1 is not desir'd

rolling back is not a good idea. you can recover space by cleaning up the files that would let you roll back.

or do a clean install with an SP1 integrated disk.
 

Drsignguy

Platinum Member
Mar 24, 2002
2,264
0
76
rolling back is not a good idea. you can recover space by cleaning up the files that would let you roll back.

or do a clean install with an SP1 integrated disk.


I agree. A clean install is always a much better plan.
 

Emulex

Diamond Member
Jan 28, 2001
9,759
1
71
you can use add/remove to get rid of features you don't need and disk cleaner and windirstat are you friend
 

Cerb

Elite Member
Aug 26, 2000
17,484
33
86
Considering that my Windows folder (don't think there's any large stuff besides pagefile and hibernate outside that folder) on Win64bit Professional SP1 (installed since 7/2009 or something like that) is only 13gb - without using vlite or something -, I wager you can do with less (obviously that's without counting hibernate and pagefile but it's easy to get rid of those).
A Windows install is not just the Windows folder. It's [total formatted space]-[free space after the install and updates], on a newly-formatted drive (not exactly a luxury for the OP). By the time it's all done, I'm usually in the low 20s (with all the update uninstall and system restore files still there). Windows installs at least a measurable amount in Program Files, too.
 
Last edited:

techs

Lifer
Sep 26, 2000
28,559
4
0
fyi my Windows 7 Pro 64bit 4 Gb.RAM, which includes Office 2010 Pro, Avast Antivirus, the usual Adobe ReadeR, Java ,Shockwave, Flash, Firefox, Silverlight and VideoLan Player used about 17 gigs immediately after install.

However, I disable indexing, system restore and changed the Windows managed page file from 3 gigs to a set 2 gigs.

So, that should be a rule of thumb for you.

Yup, I have the close to the same...Also to add, I have SP1 installed to and it shot it to grand total of 19gigs..

What I did was, I removed all drives except SSD (C300 128GB) added an older 160 Gb HDD with Xp installed on it and upgraded to a "custom" clean windows 7 install on the SSD. Went Perfect!

I should have mentioned I also have SP1 installed. So, yeah, the amounts are about even.
 

Voo

Golden Member
Feb 27, 2009
1,684
0
76
Windows installs at least a measurable amount in Program Files, too.
Just out of curiosity, what would that be? From a quick glance through both Program File Folders I can account for most stuff and the rest is a few 100mb at most.
 

Cerb

Elite Member
Aug 26, 2000
17,484
33
86
Off the top of my head, IE would be most of it, along with misc. driver utilities. Depending on optional updates, Windows Live stuff can take some room up in there, too. Doubtful it's anywhere near as much as is used for system restore (currently 7.22GB for mine, w/ default settings, and I'm pretty sure they're still stored in SVI) and uninstallable updates (haven't checked, but they usually end up in hundreds of MB, over time).
 

Auric

Diamond Member
Oct 11, 1999
9,591
2
71
If rolling back to pre-SP1 is not desir'd then run:

DISM /online /cleanup-image /spsuperseded

rolling back is not a good idea. you can recover space by cleaning up the files that would let you roll back.

That is the "recover space..." command. :hmm:

Theoretically, for that uber rare case where SP1 caused a problem it would be better to simply restore a previous image than rollback so I see no need to keep all that junk -.i.e. gobs of hotfixes later integrated into SP1, plus all the other duplication allowing rollback.

Can also run Disk Cleanup and optionally remove old restore points if any.
 

taltamir

Lifer
Mar 21, 2004
13,576
6
76
That is the "recover space..." command. :hmm:
No, rollback is the "uninstall critical security patches" command.
The recover space command is in disk cleanup called "Service Pack Backup Files"
disk cleanup said:
Windows saves old versions of files that have been updated by a service pack. If you delete the files, you won't be able to uninstall the service pack later.