| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 139737 | 2015-06-18 23:29:00 | sfc /scannow on Win7 | B.M. (505) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1403161 | 2015-06-18 23:29:00 | I am trying to run sfc /scannow on a Win7 machine of a friend but it seems I must run it as Administrator. Problem is, friend has no idea what the Admin password is and it could have been set by the Vendor at time of purchase. Admin or admin are said to be incorrect so what now????? Any thoughts? :thanks |
B.M. (505) | ||
| 1403162 | 2015-06-18 23:56:00 | So just checking, if you search 'cmd' in the start menu, then right click and 'run as administrator', it asks you for a password? | wratterus (105) | ||
| 1403163 | 2015-06-19 01:06:00 | So just checking, if you search 'cmd' in the start menu, then right click and 'run as administrator', it asks you for a password? Not quite. I can get to the command prompt ok but if I then type sfc /scannow I get the message: You must be an administrator running a console session in order to run the sfc utility. |
B.M. (505) | ||
| 1403164 | 2015-06-19 01:11:00 | Yes - have you actually tried running command prompt as admin though? That's what it's asking you to do - when you open a standard command prompt, it does not have admin privileges. | wratterus (105) | ||
| 1403165 | 2015-06-19 02:04:00 | Yes - have you actually tried running command prompt as admin though? That's what it's asking you to do - when you open a standard command prompt, it does not have admin privileges. Yes, but it would seem right clicking and running as administrator wasn’t registering as I restarted the computer and then got to run sfc. This type of behaviour is the reason I was trying to run sfc in the first place. Anyway, I now get the following message. Verification 100% complete. Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.log So now I’m off to check the CBS.log if I can find it. :D It has given examples of where to look so I’ll get back on what’s there. |
B.M. (505) | ||
| 1403166 | 2015-06-19 02:05:00 | Edited: Happy reading, its will be long :) | wainuitech (129) | ||
| 1403167 | 2015-06-19 02:35:00 | , it will be long :) and confusing... sfc often comes up with that message, even on PC's that seem to run OK. try this support.microsoft.com |
1101 (13337) | ||
| 1403168 | 2015-06-19 03:54:00 | So I find the subject Log file and get "Access Denied" :mad: when trying to open it even though it chose Notepad to do the business. Anyway, I'm now downloading the 539meg :eek: fix that 1101 suggested might be worth trying. |
B.M. (505) | ||
| 1403169 | 2015-06-19 03:56:00 | System readiness tool I assume? Worth a go, for sure. Is there a specific issue you are having with this PC, or is it just being odd in general? | wratterus (105) | ||
| 1403170 | 2015-06-19 04:26:00 | if you "really" want to have a look at the cbs log, open a command prompt as Admin, type ( or copy/paste) this exactly as is: notepad c:\windows\logs\cbs\cbs.log Notepad will open, it will load, may take a few seconds as it reads the log then you can then save it if you wish. Also have a read of make-cbs-log-useable (www.sevenforums.com). |
wainuitech (129) | ||
| 1 2 | |||||