Linked by Thom Holwerda on Fri 19th Oct 2012 20:07 UTC
Permalink for comment 539218
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/20/13 6:17 UTC, submitted by MOS6510
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
More News »
Sponsored Links



Member since:
2006-11-19
Of course 12GB is too much, but it's actually better than other choice: not having a Windows ARM version at all.
I've checked my current Windows 7 installation with TreeSize (great utlity btw). I have 64 bit windows, Office 2010 + 2013 Beta + Visual Studio, and a bunch of other things.
This is the breakdown:
28GB Windows
- 8.5G Installer files
- 8GB WinSxS (backwards compatibility)
- 3.6GB System32
- 2GB Assembly (.net native images for v2 and v4 for both 32 and 64 bits)
- 1.2GB temp
- 1.2GB SysWOW64 (32 bits compatibility)
- 1GB Software Distribution
- 1GB Microsoft.Net
- 500MB Fonts
- and the rest totals less than 1GB
10GB System Volume Information (shadow copies and system restore)
1.3GB MSOCache (Office setup files)
I've skipped over program files, and user data
Out of these system files, at least 32GB of ~40GB is redundant and useless stuff (for example I don't need 4 different versions of .Net).
Even if we included Office in this mix (it usually takes ~2GB installation space), we'd still have a total of 10-11GB actual useful non-redundant resources.
That means Microsoft has not actually done much to reduce this clutter, except for porting the code to ARM (which is important by itself).