New
#1
sfcfix found 28 corrupt files
Hi,
I'm new to this forum. I've read quite a bit here relating to my problem (and thank you to everyone esp to Brink and Bare Foot Kid). I took the courage to try and replace some of the corrupt system files myself (locations included system32, syswow64, IE in Program Files (plain) and IE in x86.), but it was even worse, it resulted in a hash mismatch. Luckily I did a system restore and think I've got the old versions back. I ran sfc again in in cmd at boot - it showed that if found corrupt and fixed. I then ran it again in normal mode and it showed it was unable to fix some files. Below is attached my log with the bits that I thought relevant.
So my question is, besides the difference between 32bit and 64bit what other factor makes a certain version of a system file not be suitable for my machine and how to find out which one I need from looking at my CBS/sfcdetails log? If this is mentioned already somewhere else I'd appreciate just a link to that alone.
It all started when my supportAssist with Dell didn't work, which made me realise IE11 doesn't work which introduced me to the sfc /scannow command.
Now, I know I ought to anyway upgrade to micresoft 10 soon so is it better to first have my 7 fixed and then upgrade or can I upgrade with a slightly corrupt windows 7 too?
Whilst I'm at it, I did think of going for a Repair Install, though the problem is, I bought my windows 7 home premium from Dell and so micresoft's website wouldn't accept my key for downloading an ISO image and Dell says I'm out of warrant. Now I do have a windows 7 somewhere on an external HD but don't know if that matches mine or is legit and fear that after using that, I may not be able to upgrade to 10 anymore?
Sorry for my verbose message but I'm a newbee to all that cmd stuff, eager to learn though an would massively appreciate any help.
Thank you,
Nickk