each time after start windows normally pc gets restarted....

Can you navigate to that location to see if the file actually exists?

sushmit said:

marsmimar said:

See option three. Also contained in my first post.

SFC /SCANNOW Command - System File Checker

dude i have gone through the link u have posted
the problem is that when i type either sfc /scannow or sfc /verifyonly i get this...
There is system repair pending which requires reboot to complete. Restart window and try running sfc again

then i tried option three running this command....

findstr /c:%windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

and got this as result...
system cannot find the path specified.

is there another way to see/open CBS.log file?

It appears you ran the command incorrectly. It should be:

Code:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

Open an Elevated Command Prompt, highlight the code above, right click, select copy, right click inside the elevated command prompt, select paste.

hi, and thanks for helping but i typed the command correctly and the same massage appears....

specifies path not found...

and somehow i accesed the path but there were only two files with extention .cab but no log file found....
but when i run sfc /scannow /offbootdir=D:\ /offwindir=D:\windows
it says that log file is created as mentioned earlier............ i don't no whats going on its so confusing...

finally i decided to reinstall my window but this time new prob..
it says no sriver found.... during installation trying to install it from usb flash drive.

Please post a screenshot of the input and output of the command. Maybe we can spot something.

sorry dude but how can i take screen shot without log in in window...

ok.... these are the what i am getting
when i run sfc /scannow
i get this - There is system repair pending which requires reboot to complete. Restart window and try running sfc again.
and when i run findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
i get this - the system cannot find the path specified.
if there is another way to open log file then please tell me... getting frustrated now...

A pic from a digital camera may suffice.

Are you able to navigate through the folders to see if the file itself actually exists? Sounds like it may not, but I would try to see for myself...

ok i just now run chkdsk /f and at 2nd stage it corrected error in index $130 for file 22594 and recovered so many orphaned file (unindexed file)

at stage 3
correcting errors in the master file table's <MFT> BITAMP attribute.
correcting errors in the volume bitamp
windows has made correction to the file system.

40856575 kb total disk space.
19014032 kb in 88010 files.
51304 kb in 15243 indexes.
8 kb in bad sector.
......
.... ans so on...
Failed to transfer logged message to the event log with status 50

F5ing said:

A pic from a digital camera may suffice.

Are you able to navigate through the folders to see if the file itself actually exists? Sounds like it may not, but I would try to see for myself...

i think u r right that file does not exist actually but when i run
sfc /scannow /offbootdir=f:\ /offwindir=f:\windows

it says file CBS.log is created...