New
#21
Glad to hear that you got them extracted.
But I am still perturbed that I cannot do option #3.
Is something wrong with my PC?...because I acquired this used two year old HP Pavilion three months ago (I always have some kind of trepidation buying used anything) and although it seems running properly (actually excellently), I wonder when I encounter something like this...the computer unable to execute what seems to be routine function.
Shawn, have you tried copy/pasting the same code you posted in the forum to your command prompt? Is it possible you might have posted a typo?
Yep, it works fine for me.
I must admit that I'm not sure why it's not working for you if you are not in safe mode and logged in to an administrator account when you run the command in an elevated command prompt.
I just realized that an icon sub-titled sfcdetails is shown aligned together with other desktop icons on Administrator (Home)account. Totally missed it. It shows an empty chkdsk pad.
It does not show on (Tony).
That's the correct one then. It's just empty since there are not SFC results in your CBS log.
How reliable are chkdsk and sfc /scannow scans?
I wonder because with Vista there were always some files that were needing repair(and most, not all were repaired). With this current used W7 laptop I acquired last December all I am getting is "no integrity violation" results. Nothing to repair?
That brings to mind, should these scans be done only when there seems to be wrong ...and not routinely as I always do? Is there a downside to over-scanning(like, weekly)?
Well, with any tool, there's no guarantee that they'll be able to repair everything unfortunately. They are a good first step to use though.
Chkdsk should be used around at least every couple of weeks.
SFC doesn't need to be used unless you suspect an issue with the system files.
Either way, it's not going to hurt anything to run them as often as you like.