Windows 10: Win10 not booting after power outage, sfc scannow does not work, chkdsk finds no errors

Hello,


I've had a power outage today when my Windows10 computer was running and now it won't boot anymore.
When booting normally and in safe mode it BSOD's with description "Critical Process Died".
Automatic repair does not work.
Sfc Scannow in offline mode from recovery command prompt shows the following output:
"
Beginning system scan. This process will take some time.


Windows Resource Protection could not perform the requested operation.
"
Note that there is no line indicating the verification phase progress!
The sfc logfile has 3 lines
"
...\wcp.dll : got STATUS_OBJECT_PATH_NOT_FOUND
...\wcp.dll : got STATUS_SUCCESS
... WcpInitialize: wcpdll version 10.0.18362.710 WinBuild.160101.0800
"

Running chkdsk does not find any errors.

I do not have a backup or registry backup.

Is there any way to recover my system?

Help would be much appreciated :

:)

 

SFC scannow not working but verify only is working

there is no problem in chkdsk I've checked When I select command prompt and sfc scannow from f8 and repair.. it shows that a reboot is required for pending repair and pending renames folder in winsxs is full of files.. what should I do??

 

Chkdsk and sfc /scannow

Thanks. That's very useful.

This then makes logic of what is illogical in Windows!

When I was running Windows XP chkdsk would come up frequently and it took ages to wait for the on screen post booting process to complete. It is quite quick within Windows 10 through the user interface. It looks like the procedure or/and code behind it has changed from Windows XP & 7 to Windows 10.

This looks like it. I only used sfc /scannow this week and had never used it previously in Windows 10. In some posts which I cannot now find some users had complained that their operating system was performing worse i.e. with more errors after using it. This concerns me a little and also that sfc /scannow may create additional issues?

In fact knowing when to use chkdsk and sfc /scannow isn't always obvious. I guess if the explanation is correct I'm still not sure of the difference between file system errors and Windows System errors.

Perhaps in the event of a crash it's best to go to the Event Viewer first and see if the problem can be researched and resolved from there and then run chkdsk first and only sfc /scannow if there is no obvious solution to the error?

 

Windows 10 running slow after power outage


Chance is your HD was corrupted or even damaged due to power outage. Open Admin command prompt:

1. Run: chkdsk /r C:
2. then Run: dism /online /cleanup-image /restorehealth&sfc /scannow&pause

NOTE: You can copy and paste the above to the command line then run.