Quote Originally Posted by saaya View Post
have you never trimmed down windows before?
you can cut down windows from 1.2gb to 0.5gb and still have everything you need working. depending on what you do with your pc you can even cut it down to 0.2gb

And youd be surprised how little code is actually beeing used when you run your pc. Let say you have 1 file which is 100kb in size. 100.000 letters... you can change quite a lot of them withint having any serious issues
again, depending on what you do...

and on the other hand, for a 100kb file to be corrupt you only need to have 1 BIT wrong. so if its single bit errors you guys are getting here then that could explain why so many files are corrupt.

But i think its not single bit errors, sounds more like several chunks of data are missing or wrong from what ive heard.
I see what you mean.
Still based on % of corrupted files vs % of files actually vital to the system, the probability that I should encounter crashes is quite high in my opinion.

I would really like sfc to log what files are corrupt so that I can actually check them by myself.