sfc /scannow runs completely then disappears

I'm trying to scan my system to find out why I keep getting the infamous "has stopped working" message. I'll post that separately. But my problem with the scan is that the window comes up and the scan runs all the way to 100% and then the window closes. Actually I can only see it to 99% because of that automatic closing.

From all I've read, I'm supposed to get information from that window even if it doesn't find any problems.

So not *it* seems to be a problem.

Suggestions, as always, most welcome and received with thanks.

"G"

What antivirus do you use? Make sure you're computer is not infected.

Run these tools and delete anything they may find:

• Anti-rootkit utility TDSSKiller

ESET online scanner:

• Free Online Virus Scanner | ESET

• Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer

I use ESET Nod 32 AV and run Malwarebytes Anti-Malware - both up to date.

I ran TDS SKiller and nothing was detected. The report is l-o-n-g so I've attached it as a text file. Hope that's okay.

I know I have to go through a number of steps to maybe find the right one. Thanks much for helping with that.

"G"

Try SFC /SCANNOW : Run in Command Prompt at Boot

check this info ,
SFC /SCANNOW Command - System File Checker

I'm having the devil of a time actually getting to a boot command prompt. I made a windows repair disk but can't get my machine to boot to it even though I changed the order of boot devices in my bios. I'll figure it out but right now I'm limping by with what I've got because I have some things (such a surprise!) that have to be attended to. I'll post again when I can.

Thanks for the help. And patience.

"G"

Can you attempt SFC scan in safe mode? Are you able to upload the CBS log file?

sfc when it finishes will close the command window. it's results are in a log file that is hidden away in a folder somewhere in the system log files (see below for location).

i wrote a batch command file to filter the relevant log file lines into a root file, then open that filtered log in the editor so it can be reviewed. it will also keep the command window open until you close the editor. the sfcdetails.txt file stays in the root in case you want to see it again. the batch file clears the logs before running sfc. i created the batch file in the root also so when i want to run it, i open a cmd prompt, type startsfc & hit return.

batch file 'startsfc.cmd' contents:

@echo off
rem delete old files
del /q %windir%\logs\cbs\cbs.log
del /q c:\sfcdetails.txt
rem run sfc
sfc /scannow
rem filter out non essential junk from the cbs.log
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >c:\sfcdetails.txt
rem open details in notepad
notepad c:\sfcdetails.txt
rem optional command to shut down & restart pc after running. this may be needed if
rem sfc replaces some critical files. uncomment (remove the 'rem') to activate.
rem shutdown -r
exit

I'm paying attention. Just can't dig deeper for a couple of days. Since the system's working, albeit with a few quirks, I'm not messin' with it for now. The quirks are what started this but they're stable. Hmm. Can quirks actually BE stable?

Anyway, I will attend to the suggestions a post back. Promise!

Continued thanks.

G