Unbootable Windows 7, can't read SFC logs

[daishogun]

Hi everybody,
As the title states, my Windows 7 install won't boot (not even Safe Mode!) In an attempt to rectify the situation, without a fresh install, as the amount of programs that need to be downloaded and re installed will devour my Internet quota for the month, I've run Startup Repair to no avail. I then ran SFC through CMD, and it found corruption but was unable to fix it. Now I have the CBS.log, except I can't read it very well, and the usual findstr command doesn't work when using CMD from Startup Recovery. So I need to know how to get that file out of there using CMD onto a USB or something, so I can find the corrupted files, and get to fixing them. If anyone has any other ideas on how to solve the problem (why can't I just do an Upgrade install without booting >.>) it'd be much appreciated.

P.S: Sorry about the lack of situational info, the thing is, I haven't done anything wrong. The PC hung on Shutdown last night, and hasn't booted since. No new programs, no new updates, just an ordinary day.

Cheers

 

[scrooge]

i read in another post that you may have to run SFC 3 times to fix the corrupted files.
try it and post back.


scrooge

 

[daishogun]

Well I've gotten the CBS.log off the computer, and I've run SFC at least 5 times now, so it's done all it can. I've attached the log, if anyone can shed some light on what to do next it'd be much appreciated.

 

[Kaktussoft]

how did you run sfc command from "recovery environment"? Please post the command you typed. If you typed it right it doesn't create cbs.log

Did you try "system restore" and go back a few days?

 

[Kaktussoft]

if running sfc from recovery environment it DOESN'T log in cbs.log!! to force it to create a logfile:

set WINDOWS_TRACING_LOGFILE=C:\TEMP\CBS.log

Before running sfc. Also the recovery console doesn't have findstr, but you can easily use find instead to extract relevant entries from the log, like so:

find "[SR]" C:\TEMP\CBS.log > C:\TEMP\sfcdetails.txt

 

[daishogun]

I see, never realised about having to tell it to log, only because CMD kept telling me it was logging it there. I'll give it a shot and post back if I can't find which files need to be replaced.