Error 0xc000014c

Please run the following commands with only the NVMe connected and post the results:
Code:
bcdedit /enum
bootrec /scanos
 
bcdedit /enum>

Windows Boot Manager
---------------------------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {default}
resumeobject {087af714-cc5b-11ef-a37b-9590941426b7}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
--------------------------------------
identifier {default}
device partition=C:
path \Windows\system32\winload.efi
description Windows 10
locale en-us
inherit {bootloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {087af714-cc5b-11ef-a37b-9590941426b7}
nx OptIn
bootmenupolicy Standard


bootrec /scanos>

Examining all disks for Windows installations.

Please wait, this process may take a while...

Successfully scanned Windows installations.
Total identified Windows installations: 0
The operation completed successfully.
 
This looks like if you have run these commands from Windows itself as it seems! This because the result of the Recovery Environment should be different.

So please let us know if you can boot normally now? If so we can start fixing the the remaining issues.
 
I executed it via Windows RE with only the hard drive experiencing boot issues connected.

Strange, since it reported "Total identified Windows installations: 0." In this case, wouldn't it mean it's not detecting Windows? Another thing, every time I repair the same system with scandisk, when I boot into Windows, it shows the blue screen attached (it only displays this message once, and it doesn't happen again on the next reboot). After this screen, the error message:

"Logon process initialization failed: Interactive logon process initialization has failed."





 

Attachments

  • rec1.webp
    rec1.webp
    128.5 KB · Views: 7
Hmm, then I can only recommend to backup al your important and personal data and reinstall Windows 10. I would also suggest to check the NVMe afterwards with a tool like SeaTools 5 or the manufacturer's toolkit. And to avoid such problems in the future - I would also make regular backups / system images and don't rely on Windows System Restore points because they can become broken as well.
 
I was thinking, this SSD was cloned from an old HD. I used it for a long time. If I try to copy the system32 files and also copy the boot partition, could it start normally?
 
Unfortunately, that won't work and may cause even more issues. So I would reinstall Windows 10 after making a backup.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top