Wednesday, December 28, 2011 9:32 AM
i have something problem with my server and the solution is running "sfc /scannow" in command prompt, which need administrator privilege to use it. but i faced a new problem, which i still cannot use sfc /scannow eventhough i login as administrator, its always show me
"C:\Documents and Settings\Administrator>sfc /scannow
You must be an administrator running a console session in order to use the Windows File Checker utility."
any suggestion ?
Wednesday, December 28, 2011 9:44 AM
Rightclick cmd.exe and select "Run as administrator". For more information check this link please: http://windows.microsoft.com/en-US/windows-vista/Command-Prompt-frequently-asked-questions.
Also, if you're connecting through a remote desktop services client, try running the command locally.
- Edited by Pascal Verhaegen Wednesday, December 28, 2011 9:56 AM
Wednesday, December 28, 2011 10:14 AM
Kndly check this post step by step how to used SFC and read Log file with photo
Mohamed Abd Elhamid Abd Elaziz Microsoft System Administrator My blog: http://Mabdelhamid.wordpress.com/
- Edited by M.Abdelhamid Wednesday, December 28, 2011 11:34 AM
- Edited by M.Abdelhamid Wednesday, December 28, 2011 11:35 AM
- Proposed As Answer by MYousufAliMicrosoft Community Contributor Wednesday, December 28, 2011 12:43 PM
- Marked As Answer by Clarence ZhangModerator Tuesday, January 03, 2012 7:29 AM
Wednesday, December 28, 2011 11:01 AM
you need elevated permissions to run the sfc/scannow
- Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
- Type the following command, and then press ENTER:
sfc /scannowThe sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions.
Wednesday, October 24, 2012 5:07 AM
Worked like a charm, so thank you! But there were still some corrupted files that were not fixed. I will reboot my computer to see if running the command again will fix the remaining corrupted files. This leads me to ask you about the real issue at hand.This whole mess of certain programs not working came about as a result of my installing
a RAMdisk. It's called RAMdisk Plus from Superspeed that actually uses the unmanaged portion of memory between 3 GB and 4 GB in my 32 bit version of Windows 7 Professional. I made it a fixed-size of 900 MB (the utility stated I had about one gig of unmanaged memory available) and configured a fixed-size 500 MB system paging file in it, as well as the Temporary Internet Files folder managed by Internet Explorer 9. It gives you the option of saving an image of the RAMdisk to a hard drive whenever the system is shut down. I believe my mistake was not choosing this option and letting the RAMdisk get "zeroed out" upon shutdown and repopulated upon next system startup. That and the fact that I took the paging file off of the C drive and put it in the RAMdisk. Two other drives have paging files that I created according to the Virtual Memory guidelines offered by Windows 7.
TheRAMdisk utility appears to work fine in my PAE-enabled environment. I just think I've got it improperly configured. When my system timed out and turned off there was a whole pile of index recovery operations that occurred upon startup. The RAMdisk was also nowhere to be found. I've changed the configuration to put a 400 MB fixed size paging file on my C drive, a variable-size paging file of 300 MB-600 MB along with the Temporary Internet Files on a re-created RAMdisk of 800 MB and a system-managed paging file on a another drive with lots of room. Another concern I have is with my antivirus software. Is this approach going to cause a problem with my Norton antivirus webpage-monitoring? It certainly has done so at the time of this writing as I'm unable to get antivirus and network monitoring working. Maybe antivirus software is incapable of accessing a RAMdisk.
I may have to give up this whole idea of using a RAMdisk. ( I was hoping to add another four gigs of memory for the RAMdisk if I can get the current configuration working. )
Your comments are welcome! Sorry about all the detail, but I think it will help you in giving me informed advice.