Obvisouly ...
You didn't pay attention to the tutorial or you would know the clean all or the clean command can't be run from within Windows to a "System" HDD / SSD it has to be booted to.
All you had to do after the clean all, use diskpart to create and format a single 20GB partition Step Two #2 to do the install to, then extend the Windows C: partition into the unallocated space on the SSD after the install completes and that would solve the 'size' issue.
And if you were paying attention to what I said. It was giving me the compression error when trying to boot to the drive. So I had to hook it up on another functioning machine and wipe it from there. It still worked the same...
... i get what you were saying broham. wipe it from dos.
Wasn't WORKING. OFF the os.
Hey, back once again to try and fix the same problem.
Bought a brand new packaged 120ssd, installed 7 ultimate.
Showing 30 gb full.
powercfg OFF this time, and it's still the same.
The problem isn't the drive needing to be wiped of data as all the people thought before. But what's taking up 30 gigs in a fresh 7 install???
Tried looking at all the properties of the drive and it's not showing anything abnormal.
Any suggestions?
Thanks.
Run WinDirStat. It will tell you what is on the disk. 30GB for a fresh inszall is rather steep.
How much ram do you have in your system? It's probable that the swap file is excessively large, and could be turned of to save space. Additionally disabling hibernation and deleting the hotfix/office installer could save additional space, personally I use a diskmax (DiskMax * Disk Cleanup and Windows Performance Optimization - Software - Koshy John) ccleaner (Redirecting...) solutions to clean off the fresh install junk that seems to accumulate after running thought windows updates, but to each his own.
Quote
