Scanning and repairing drive (C) stuck on 39% complete
- Thread starter Becky6319
- Start date
viveknayyar007
Splendid
- Apr 25, 2013
- 3,372
- 36
- 28,640
Hello Becky6319
Can you please elaborate the issue? Such as, when did the scanning start, did you start the scanning and repairing manually or it was auto-started by the operating system, did the operating system have any error, or did the OS behave obnoxiously, etc.?
In any case, 24 hours is way too long time for the process, especially when it is stuck at the same state.
You should power off and restart the computer and initiate the scanning process manually to rectify the issue. You can Use the SFC /SCANNOW Command to Scan and Repair Your Operating System.
Hope this helps.
Can you please elaborate the issue? Such as, when did the scanning start, did you start the scanning and repairing manually or it was auto-started by the operating system, did the operating system have any error, or did the OS behave obnoxiously, etc.?
In any case, 24 hours is way too long time for the process, especially when it is stuck at the same state.
You should power off and restart the computer and initiate the scanning process manually to rectify the issue. You can Use the SFC /SCANNOW Command to Scan and Repair Your Operating System.
Hope this helps.
viveknayyar007 :
Hello Becky6319
Can you please elaborate the issue? Such as, when did the scanning start, did you start the scanning and repairing manually or it was auto-started by the operating system, did the operating system have any error, or did the OS behave obnoxiously, etc.?
In any case, 24 hours is way too long time for the process, especially when it is stuck at the same state.
You should power off and restart the computer and initiate the scanning process manually to rectify the issue. You can Use the SFC /SCANNOW Command to Scan and Repair Your Operating System.
Hope this helps.
Can you please elaborate the issue? Such as, when did the scanning start, did you start the scanning and repairing manually or it was auto-started by the operating system, did the operating system have any error, or did the OS behave obnoxiously, etc.?
In any case, 24 hours is way too long time for the process, especially when it is stuck at the same state.
You should power off and restart the computer and initiate the scanning process manually to rectify the issue. You can Use the SFC /SCANNOW Command to Scan and Repair Your Operating System.
Hope this helps.
Sure, it started approximately 6 am on December 24. It was started automatically when I restarted my computer. I don't know of any particular error. It was a Windows 7 that I upgraded to Windows 10 a couple of months ago.
I'll give your tip a try. Thanks
viveknayyar007 :
Hello Becky6319
Can you please elaborate the issue? Such as, when did the scanning start, did you start the scanning and repairing manually or it was auto-started by the operating system, did the operating system have any error, or did the OS behave obnoxiously, etc.?
In any case, 24 hours is way too long time for the process, especially when it is stuck at the same state.
You should power off and restart the computer and initiate the scanning process manually to rectify the issue. You can Use the SFC /SCANNOW Command to Scan and Repair Your Operating System.
Hope this helps.
Can you please elaborate the issue? Such as, when did the scanning start, did you start the scanning and repairing manually or it was auto-started by the operating system, did the operating system have any error, or did the OS behave obnoxiously, etc.?
In any case, 24 hours is way too long time for the process, especially when it is stuck at the same state.
You should power off and restart the computer and initiate the scanning process manually to rectify the issue. You can Use the SFC /SCANNOW Command to Scan and Repair Your Operating System.
Hope this helps.
Well, I followed the directions. it says "Verification 2% complete" on one line. The next line says "Windows Resource Protection could not perform the requested operation". I'm guessing that's a bad thing.
Windows Resource Protection is the SFC function. What it means is that one file is very corrupted and stopping sfc /csannow.
Here's a bunch of info, some work some don't:
https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&es_th=1&ie=UTF-8#q=Windows+Resource+Protection+could+not+perform+the+requested+operation%22&es_th=1
Your probable in for a System Restore (to a point before the crises began) at the least, and a reinstall at the worst.
Bill
Here's a bunch of info, some work some don't:
https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&es_th=1&ie=UTF-8#q=Windows+Resource+Protection+could+not+perform+the+requested+operation%22&es_th=1
Your probable in for a System Restore (to a point before the crises began) at the least, and a reinstall at the worst.
Bill
TRENDING THREADS
-
Question No POST on new AM5 build - - - and the CPU & DRAM lights are on ?
- Started by Uknownflowet
- Replies: 13
-
-
-
-
Facebook
Twitter
Instagram