Windows 10: Windows 10 suddenly unable to boot after word reported error

Got a "Word has run into an error that's preventing it from working correctly" pop up with repair button and stuff, clicked repair button, nothing happens, decides to reboot to see if that solves the problem, windows 10 goes into auto repair loop.


Repair fails, SrtTrail says can't determine cause. Strangely, no restore points probably corrupted with the other things?


Looked up solution online, in recovery CMD, tried using BCDboot to repair BCD, cannot find BCD template


Tried SFC, exits immediately, unable to perform requested operation


Tried DISM, either access denied or store corrupted, can't remember.


Disabled auto repair through BCDedit. Reports ACPI.sys 0xc000000f.


Installed another copy of windows 10 and attempting repair there. Copied over missing sys files in System32\drivers one by one. Normal mode stuck after balls stops spinning. Want to enable verbose booting, tried both BCD setting and the registry key, still no verbose message. Copied over all sys files present in newly installed windows 10 over to the old installation. critical service failed, then 0xc000021a. could revert the copying, then it goes back to stuck after balls stop spinning


Tried DISM repair on offline image. Looking at DISM log, reported COMPONENTS access denied. Loaded hive in regedit and changed permissions. realized components store is empty and only 8KB. Also System32\SMI\store\machine\schema.dat is missing too. realized BCD-Template is also missing, copying over from the new system resulted in successful BCDboot but still can't boot DISM reports corrupted. Desperate, copied COMPONENTs over from the new system. DISM continues to 86%.


2020-01-24 01:45:07, Info CSI 00000005 Warning: Unable to repair manifest for component [l:92 ml:140]'amd64_6dd3779dc5ee4280d66fff51454d87c5_31bf3856ad364e35_10.0.18362.327_none_e776ecd6f4cf5ba8' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:07, Info CSI 00000006 Warning: Unable to repair manifest for component [l:92 ml:140]'amd64_c4531351bea01b4c7825169515cb4dcd_31bf3856ad364e35_10.0.18362.327_none_746f081547f8e304' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:07, Info CSI 00000007 Warning: Unable to repair manifest for component [l:92 ml:140]'amd64_d214d17159dc3dc417b339446320f425_31bf3856ad364e35_10.0.18362.327_none_5a9b286c39d4981e' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:16, Info CSI 00000008 Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_hyperv-hypervisor-o..oyment-languagepack_31bf3856ad364e35_10.0.18362.1_zh-cn_baec99c4ea8fd5fb' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:17, Info CSI 00000009 Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_hyperv-worker-oneco..oyment-languagepack_31bf3856ad364e35_10.0.18362.1_zh-cn_f6fd71fdabcbff7e' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:20, Info CSI 0000000a Warning: Unable to repair manifest for component [l:100 ml:140]'amd64_microsoft-windows-1..-payload-deployment_31bf3856ad364e35_10.0.18362.387_none_34d955405e81db4c' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:23, Info CSI 0000000b Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-i..oyment-languagepack_31bf3856ad364e35_10.0.18362.1_zh-cn_00cc423cadcd11be' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:23, Info CSI 0000000c Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-g..oyment-languagepack_31bf3856ad364e35_10.0.18362.1_zh-cn_0c6d9de4cb5064d0' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:23, Info CSI 0000000d Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-d..oyment-languagepack_31bf3856ad364e35_10.0.18362.1_zh-cn_3434b2e84e695514' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:23, Info CSI 0000000e Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-p..oyment-languagepack_31bf3856ad364e35_10.0.18362.1_zh-cn_4dbba6e0483da526' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:23, Info CSI 0000000f Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-p..oyment-languagepack_31bf3856ad364e35_10.0.18362.1_zh-cn_66a7e0da9be5739e' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:23, Info CSI 00000010 Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-g..oyment-languagepack_31bf3856ad364e35_10.0.18362.1_zh-cn_6b02f8391394c01e' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:24, Info CSI 00000011 Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.18362.1_zh-cn_c31c3e533877794a' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:25, Info CSI 00000012 Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-c..equired-deployment0_31bf3856ad364e35_10.0.18362.1_zh-cn_1e3944b9c3bc68ee' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:25, Info CSI 00000013 Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-c..eatures-deployment0_31bf3856ad364e35_10.0.18362.1_zh-cn_8f763ef1184ed41d' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:25, Info CSI 00000014 Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-c..d-wow64-deployment0_31bf3856ad364e35_10.0.18362.1_zh-cn_ec230fc20bad26e4' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:27, Info CSI 00000015 Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-c..res-deployment00100_31bf3856ad364e35_10.0.18362.1_zh-cn_0c21490396281c8e' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:28, Info CSI 00000016 Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-c..res-deployment00110_31bf3856ad364e35_10.0.18362.1_zh-cn_0c22494d962735e5' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:30, Info CSI 00000017 Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-c..red-deployment01100_31bf3856ad364e35_10.0.18362.1_zh-cn_e81dcf2d5aa7c084' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:30, Info CSI 00000018 Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-c..red-deployment01110_31bf3856ad364e35_10.0.18362.1_zh-cn_e81ecf775aa6d9db' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:30, Info CSI 00000019 Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-c..red-deployment01120_31bf3856ad364e35_10.0.18362.1_zh-cn_e81fcfc15aa5f332' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:31, Info CSI 0000001a Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-c..red-deployment01130_31bf3856ad364e35_10.0.18362.1_zh-cn_e820d00b5aa50c89' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:36, Info CSI 0000001b Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-c..wow64-deployment000_31bf3856ad364e35_10.0.18362.1_zh-cn_625afbb28bdf8338' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:36, Info CSI 0000001c Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-c..uired-deployment000_31bf3856ad364e35_10.0.18362.1_zh-cn_7960f53e9b2017c0' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:37, Info CSI 0000001d Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-c..uired-deployment010_31bf3856ad364e35_10.0.18362.1_zh-cn_79d27c6c9ad71c47' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:37, Info CSI 0000001e Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_microsoft-windows-c..tures-deployment020_31bf3856ad364e35_10.0.18362.1_zh-cn_5f6d4469e3e1c299' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:41, Info CSI 0000001f Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_multimedia-mfcore-d..oyment-languagepack_31bf3856ad364e35_10.0.18362.1_zh-cn_9a1cc4390d880075' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:41, Info CSI 00000020 Warning: Unable to repair manifest for component [l:98 ml:140]'amd64_windows-defender-am..initions-deployment_31bf3856ad364e35_10.0.18362.1_none_ac3cef6ce5082e32' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:41, Info CSI 00000021 Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_windows-defender-am..oyment-languagepack_31bf3856ad364e35_10.0.18362.1_zh-cn_1a7e4b601eeb3f2a' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-24 01:45:41, Info CSI 00000022 Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_windows-defender-am..oyment-languagepack_31bf3856ad364e35_10.0.18362.1_en-us_baf7e0f237c96518' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.


2020-01-24 01:45:41, Info CBS Repr: The system configuration is not qualified for Windows Update download, skip WU.




Also tried swapping WinSxS from the new system, DISM runs to 96% in that case


2020-01-23 20:57:55, Info CSI 00000005 Warning: Unable to repair manifest for component [l:98 ml:140]'amd64_windows-defender-am..initions-deployment_31bf3856ad364e35_10.0.18362.1_none_ac3cef6ce5082e32' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-23 20:57:56, Info CSI 00000006 Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_windows-defender-am..oyment-languagepack_31bf3856ad364e35_10.0.18362.1_zh-cn_1a7e4b601eeb3f2a' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.

2020-01-23 20:57:56, Info CSI 00000007 Warning: Unable to repair manifest for component [l:99 ml:140]'amd64_windows-defender-am..oyment-languagepack_31bf3856ad364e35_10.0.18362.1_en-us_baf7e0f237c96518' from backups directory with disposition 2. A backup file may not exist or may be corrupt. Falling back to WU.


2020-01-23 20:57:57, Info CBS Repr: The system configuration is not qualified for Windows Update download, skip WU.


Why is it not downloading from windows update?


How did this happen? Why did many sys files in System32/drivers go missing, BCD-Template gone and COMPONENT hive went empty? I migrated the system from another SSD to a more spacious one, and did two reboots to check it indeed works, and formatted the original SSD. Recently I have installed a Russian language pack. Otherwise I don't recall anything in particular that could lead to this.


Is there a way for me to do an upgrade install without the ability to boot into the corrupted system? Some way to manually perform a similar action to upgrade install by using DISM? I really don't want to reinstall all the applications...


Image Version: 10.0.18362.592 as reported by DISM, so I guess version 1903.

:)

 

Unable to boot the device with error: 0xc0000428 on Windows 10

Hi Vuk,

Thank you for posting in Microsoft Community and being part of Windows 10.

I understand the inconvenience you are facing in booting the device with 0xc0000428 error. We will help you with this issue.

Do let us know the following to assist you better with this issue:

• What is the make and model of your device?
• What is the complete error message along with the error code of this issue?
• From when are you facing this issue?
• Have you make any hardware/ software changes to your device prior to this issue?

I would like to inform that when you attempt to start a Windows 10 system, the system fails to start normally and you receive an error:
0xc0000428 for the signed driver dlkmdldr.sys. Do confirm us if you are facing the same issue.

Try the below and check if it helps.

Step 1: I suggest you to remove all the external devices except mouse and keyboard, hard reboot the device and check if the issue persists.

Step 2: I suggest you to boot the device by choosing the "Disable Driver Signature Enforcement" mode from the advanced boot menu, you would be able to boot the system to the desktop.

• Try to boot the device to Windows Recovery Environment
• Click on Advanced options, Startup Settings
  and Restart.
• Once the computer restarts, press F7 key to start he device on
  Disable Driver Signature Enforcement mode.
• Check if the computer boot successfully.

Step 3: I suggest you to install the pending updates on your device after restarting the computer.

Steps:

• Connect to the internet.
• Press Windows key and type
  updates.
• Click on Check for updates.
• Under Windows Updates, click on
  Check for updates.
• Try to install the updates being shown.

Hope it helps. Try the above an update us the status of this issue to assist you further accordingly.

 

Unable to boot the computer.

Hi Samid,

Thank you for posting your query on Microsoft Community.

Before we proceed, we would require more information to assist you further.

• 
  What is the make and model of your computer?
  

I suggest you check if you are able to boot into Windows Recovery Environment using installation media. Follow the steps provided below and check.

• • Insert the installation USB and boot Windows 10 from it.
  • In the ‘Windows setup’ page select the ‘language to install’, ‘Time and currency format’ and the ‘keyboard or input method’ and click on ‘next’.
  • Click on ‘Repair your computer’ and select ‘Troubleshoot’.

Check if you are able to boot to this window. If you are unable to boot to this window, I suggest you to contact the manufacturer and check.

Hope this information is helpful. Reply us with this information to assist you further.

Thank you.

 

Where's the Windows 10 compatibility report?

Hi,

Thank you for contacting Microsoft Community.

I understand that you are unable to get the compatibility report.

I will certainly help you with this.

Please provide the below information.

1. From which operating system you upgraded to Windows 10?

2. Did you check the desktop screen for the report?

I would suggest you to go through the below steps:

Steps: If you are unable to find the file on desktop, you can try to check in the system drive.

• 
  Press Windows key+E.
  
• 
  Double click on C: drive (default system drive).
  
• 
  On the top right corner in the search bar, type the compatibility file name and search
  

Please post back with the status of the issue and we will be glad to assist you further.