Hi guys!
Been a long time since I needed some help but not sure what to do...
I was setting up a new installation of Windows 7 Ultimate...had got to stage where everything was installed and created a backup of the drive....
I installed Windows 7 on a new Intel5 SSD 256GB harddrive...I usually use Samsung Pro or Evo but the latest harddrive had firmware problems with amd controller....hence Intel...
I usually setup cmd without uac because I use it often for different projects....just used " sfc /scannow" as a test to see if I had added the elevated command....BUT when the sfc had finnished I had an error and even sfcfix couldn't repair....I will point out didn't feel that the program accessed my cdrom drive with windows 7 to repair the damaged file...
So the only reason for me being here is sfcfix didn't fix the nagging file...
I am attaching the CBS.log and SFCFix.txt
Been a long time since I needed some help but not sure what to do...
I was setting up a new installation of Windows 7 Ultimate...had got to stage where everything was installed and created a backup of the drive....
I installed Windows 7 on a new Intel5 SSD 256GB harddrive...I usually use Samsung Pro or Evo but the latest harddrive had firmware problems with amd controller....hence Intel...
I usually setup cmd without uac because I use it often for different projects....just used " sfc /scannow" as a test to see if I had added the elevated command....BUT when the sfc had finnished I had an error and even sfcfix couldn't repair....I will point out didn't feel that the program accessed my cdrom drive with windows 7 to repair the damaged file...
So the only reason for me being here is sfcfix didn't fix the nagging file...
I am attaching the CBS.log and SFCFix.txt