[SOLVED] Win 10 Home does not boot

[amic_2023]

Hello,
I have a Toshiba Satellite S70-B-10U, Windows 10 Home, Update level 21H2 - 10.19044.1826 (July 2022).
On the 13th of July 2023 (‘disaster’ day ) during a long working session on the laptop, I interrupted work without shutting down.
Upon return to the laptop found it at Black Screen of Death with cursor on the top left corner.
I’ve powered it down and, after a while attempted to restart.
Result: boot process failed with a message saying something like ‘No Bootable device found’.
All subsequent attempts to repair and resume normal operation failed.

Actions
Repeated Automatic Repair attempts: failed (DISMRepairLogFile.txt created on ‎Thursday, ‎ July ‎13, ‎ 2023, ‏‎ 10:19:47 PM during the 1st attempt to repair the system and there is also a SrtTrace.log available generated sometime later)
Safe mode: failed to enter/activate
System Restore: 2 restore points available: both failed to solve the problem (the oldest one returned error 0x81000204)
Repaired boot partition: without formatting the FAT32 partition (100MB) => no improvement!
Media Creation Tool: created USB installation media (latest Windows 10 – 22H2), then executed:

• CHKDSK /R C: => finalized OK after ~6 hours of run
• SFC /SCANNOW /OFFBOOTDIR=N:\ /OFFWINDIR=C:\Windows /OFFLOGFILE=D:\Temp\SFC_log.txt => SFC_log.txt file is available
• DISM /Image:C: /Cleanup-Image /CheckHealth => OK
• DISM /Image:C: /Cleanup-Image /ScanHealth => Component store is repairable + DISM.log (31.07.2023)
• DISM /Image:C: /Cleanup-Image /RestoreHealth /Source:\sources\install.wim /Index:1 /LimitAction /ScratchDir:\temp => Source files could not be found + DISM.log (01.08.2023)

No new/recent Updates (packages) on Windows 10 Home were found!
No memory.dmp file was found.

Analyse
Event logs (from ‘disaster’ day): System, Security, Setup, Application, Error => found nothing!

SrtTrail.log:
3 errors reported

Root cause found:
---------------------------
Unspecified changes to system configuration might have caused the problem.
...
Repair action:
Result: Failed. Error code = 0x32
Time taken = 12797 ms

Repair action: System Restore
Result: Failed. Error code = 0x1f
Time taken = 84563 ms

Repair action: System files integrity check and repair
Result: Failed. Error code = 0x57
Time taken = 6562 ms

SFC_log.txt:
3 corruptions detected

2023-08-01 11:22:18, Info CBS Checking System Update Readiness.
2023-08-01 11:22:18, Info CBS
2023-08-01 11:22:18, Info CBS (p) CSI Manifest Corrupt amd64_microsoft-windows-wpfcorecomp_31bf3856ad364e35_10.0.19041.1_none_5a256215ddb70d16
2023-08-01 11:22:18, Info CBS Repair failed: Missing replacement manifest.
2023-08-01 11:22:18, Info CBS (p) CSI Payload Corrupt amd64_microsoft-windows-cloudfiles-filter_31bf3856ad364e35_10.0.19041.1806_none_14d97b5344d4570e\cldflt.sys
2023-08-01 11:22:18, Info CBS Repair failed: Missing replacement payload.
2023-08-01 11:22:18, Info CBS (p) CSI Payload Corrupt amd64_microsoft-windows-classpnp-minwin_31bf3856ad364e35_10.0.19041.1320_none_836941b8a283825b\Classpnp.sys
2023-08-01 11:22:18, Info CBS Repair failed: Missing replacement payload.

2023-08-01 11:22:18, Info CBS Summary:
2023-08-01 11:22:18, Info CBS Operation: Detect and Repair
2023-08-01 11:22:18, Info CBS Operation result: 0x800f081f
2023-08-01 11:22:18, Info CBS Last Successful Step: Remove staged packages completes.
2023-08-01 11:22:18, Info CBS Total Detected Corruption: 3
2023-08-01 11:22:18, Info CBS CBS Manifest Corruption: 0
2023-08-01 11:22:18, Info CBS CBS Metadata Corruption: 0
2023-08-01 11:22:18, Info CBS CSI Manifest Corruption: 1
2023-08-01 11:22:18, Info CBS CSI Metadata Corruption: 0
2023-08-01 11:22:18, Info CBS CSI Payload Corruption: 2
2023-08-01 11:22:18, Info CBS Total Repaired Corruption: 0
2023-08-01 11:22:18, Info CBS CBS Manifest Repaired: 0
2023-08-01 11:22:18, Info CBS CSI Manifest Repaired: 0
2023-08-01 11:22:18, Info CBS CSI Payload Repaired: 0
2023-08-01 11:22:18, Info CBS CSI Store Metadata refreshed: True
2023-08-01 11:22:18, Info CBS Staged Packages:
2023-08-01 11:22:18, Info CBS CBS Staged packages: 0
2023-08-01 11:22:18, Info CBS CBS Staged packages removed: 0

CBS.log (on C:\Windows\Logs\CBS):
1. last records are from 2023-07-13 (‘disaster’ day)

DISM.log:
1. DISMRepairLogFile.txt (created on ‎Thursday, ‎July ‎13, ‎2023, ‏‎10:19:47 PM and copied to USB stick on 07.08.2023)
2. 2023-07-31 16:13:53
DISM /Image:C: /Cleanup-Image /ScanHealth => The component store is repairable.
3. 2023-08-01 10:57:35
dism /Image:C: /Cleanup-Image /RestoreHealth /Source:\sources\install.wim /LimitAccess /ScratchDir:\temp => Source files could not be found

The last two DISM logs are showing the same 3 errors/corruptions as above (SFC_log.txt).

Comment
These corruptions seem to be very old ones. They might be the reason for the message DISM is constantly outputting: “Source files could not be found” as I cannot exactly match the install.wim to the needed version/build number of the missing files. As a result I’m afraid this is not the real (root) cause of the problem with my laptop i.e. the boot failure.

Notes and Questions
1. I’m only able to execute SFC and DISM OFFLINE as I briefly presented in the Actions section. The collected logs are indicating the same issues/corruptions.
2. Is it possible to run SFCFix.exe and ComponentScanner.exe on disk C: from the recovery environment (WinPE) of the bootable USB installation media (X:\Sources) i.e. without GUI interface!?!
If the answer is Yes how do I specify the target volume? Simply using: ‘SFCFix.exe C:’ and ‘ComponentScanner.exe C:’ or somehow else?
3. Where the logs will be generated as I have no Desktop on display, and I don’t know what user account I’m logged in with WinPE? Would it be possible to redirect the log files to some different/desired folder?
4. What other action may I execute to collect more information about the status of my laptop?
5. If my assumption (see my Comment above) is correct, what additional steps/actions are necessary to further investigate and (hopefully) fix the problem.

Any help and advice would be great. Thank you.

 

[DR M]

Hello.

It's been a while since you asked for assistance. Have you solved the issue?

 

[amic_2023]

Hello,

Thank you for replying.

Unfortunately no, my laptop still won't load Windows 10 Home. The only clues about the state of the machine are, as presented, the errors in the SFC & DISM logs ("manifest and payload component corruptions") and the error (0x81000204) issued when trying a System Restore.

As DISM /Image:C: /Cleanup-Image /ScanHealth indicated that “The component store is repairable”, I tried to fix it by executing the DISM ... /RestoreHealth command OFFLINE (booting an USB installation media) using the image corresponding to Windows 10 Home update version 22H2 (last one available for download). This attempt failed with “Source files could not be found”.

I was hoping to get more information by running SFCFix.exe and ComponentsScanner.exe. But the instructions for using these programs seem to indicate the possibility to execute them only in the case of a bootable Windows (Desktop involvement). This is the reason behind questions 2 and 3 in my first message, for which I have no answer.

Again any advice is welcome.
Thank you.

 

[DR M]

So, you are still getting the No Bootable device found error?

If yes, try the 2 methods suggested here: Solution for No Boot Device Found on Windows 10

Do not download anything from the site, just read the 2 methods suggested.

 

[amic_2023]

Hello,
Read the suggested paper.
Executed the following steps:
1. Changed Boot Order: HDD/SSD, USB, …
2. Restarted - > after showing the Toshiba logo and rotating dots => blue screen with the following text:

Recovery
Your PC couldn’t start properly
After multiple tries, the OS on your PC failed to start so it needs to be repaired
Error code: 0xC0000001

You’ll need to use recovery tools. If you don’t have any installation media … (as I’ve indicated I have such an USB Installation media)

Press Enter to try again
Press F1 for enter Recovery Environment
Press F8 for Startup Settings
Press ESC for UEFI Firmware settings

3. Pressed F1 and entered Recovery Environment
4. Did not execute the 2nd Method as I’ve already done it (pls. see my initial message ‘Repaired boot partition’; I will provide step by step details of the executed procedure, if necessary)

Thank you.

 

[DR M]

Can you please provide a screenshot of the error you are getting when you start the computer? (no bootable device)

 

[amic_2023]

Hello,

I’m afraid there is a misunderstanding here, probably due to the fact that I’m not a native English speaking person.

In my initial message I tried to explain what happened when my laptop started to behave wrongly:

• After a break during a long working session I found the laptop with a black screen and a message saying something like “No bootable device”. Unfortunatelly I took no photo of the screen at that time, but instead I’ve powered down the laptop.
• After waiting for 3-5 minutes I powered it on and it entered the sequence of recovery, never reaching the black screen again, never outputing the above message again, but also never being able to successfully complete the boot process.
• I have also summarized (to the best of my possibilities) the actions I’ve executed in my subsequent attempts to bring back my laptop to normal operation and my findings during these attempts. No need to say, I guess, that all my efforts where in vain: my laptop does not boot!

In my previous message I’ve reproduced the Recovery blue screen that the laptop was displaying today after an attempt to boot Windows 10 Home. Photo attached.

Thank you.

 

[DR M]

You said that you tried Safe mode, System Restore, Startup repair.

I'm not sure if you tried the above using the Bootable Usb.

If not:

1. Boot your computer from the Windows installation media.
2. Press Next at Language options screen.
3. Choose Repair your computer.
4. Then choose Troubleshoot -> Advanced Options –> Start-up Repair.
5. Follow the onscreen instructions to fix your computer.

Result?

 

[amic_2023]

Hello,

1. Booted from the Windows USB installation media and launched … Startup Repair.
2. “Diagnosing your PC”. (rotating dots)
3. “Checking disk for errors. This might take over an hour.” (rotating dots)
4. Startup Repair blue screen: "Startup Repair couldn’t repair your computer. …”

Screen photo and SrtTrail.txt log file attached.

Please note that a previous attempted execution of Startup Repair generated a SrtTrail.txt log file that highlighted some error codes as presented in my initial message.

 

[DR M]

You said that you tried Safe mode, System Restore, Startup repair.

I'm not sure if you tried the above using the Bootable Usb.

Can you please confirm that you tried the above using the installation media, without any success?

 

[amic_2023]

Hello,

As I cannot 100% remember if I also tried these procedures using the USB installation media I will execute them today and post back the results.

Thank you.

 

[amic_2023]

Hello,

Using Windows 10 USB Installation Media (W10UIM) test results:

• As indicated in my initial message, two System Restores are available on my laptop (dated June 2023 and July 2023). It was possible to attempt System Restore from W10UIM, but all 4 attempts failed (Jun23 – it gave an error message: it asks to execute chkdsk /R – see 1st photo attached, Jul23 – this one says nothing but returns to the initial System Restore screen (!?!), Jul23, Jun23)
• Entering Safe Mode from W10UIM is NOT possible because there is NO Startup Settings option in Advanced options (pls. see attached photo). So it seems I did not attempted this before (for obvious reasons). Please advise how this procedure has to be executed.

Note: As an alternative I might try to force Safe Mode if it is acceptable and successful.

Thank you.

 

[DR M]

I have the impression that the screenshot with the Advanced options leads to an older Windows 10 version. Are you sure you created the Installation Media from here?

Note: As an alternative I might try to force Safe Mode if it is acceptable and successful.

You said that you tried and it failed to enter/activate. That is why I asked you to use the installation media.

 

[amic_2023]

Hello,

I have downloaded MediaCreationTool22H2.exe on 17.07.2023 from https://www.microsoft.com/en-us/software-download/windows10/.
I have screen captures taken during the entire USB Media Creation/Installation carried on 17.07.2023. Pls. see the attached capture.

Attached are also the photos of the laptop after checking the version of the install.esd located on the USB installation media at D:\sources.

As for the request to try entering Safe Mode from the USB Installation Media I’m a little bit confused: doing so wouldn’t it mean that the OS going to Safe Mode will be the one booting from the USB? How will this help in diagnosing my laptop with Windows 10 Home on the C: drive? Am I missing something?

Thank you.

 

[DR M]

1. Using the installation media, go to the Advanced options, as you did before, and choose Command prompt.
2. When the command line appears, enter the following command and press Enter to execute it: bcdedit /set {default} safeboot network
3. Once the operation successfully completes, close the command prompt and select Continue to exit and boot into Safe Mode.

Result?

 

[amic_2023]

Hello,
Booted USB installation media and did:
1. Advanced options, Command prompt:

bcdedit /enum
bcdedit /set {default} safeboot minimal

2. Turned laptop off, removed USB installation media, restarted laptop which ended at Recovery – Your PC Couldn’t start properly … blue screen. Photo attached.
3. Pressed F8 -> Startup Settings
4. Pressed F4 -> ended at the same blue screen; same happened when F5 and F6 were pressed!
5. Rebooted USB installation media, Advanced options, Command prompt:

bcdedit /set {default} safeboot network

6. Same steps where executed, with the same results.
Same as my post #7.
Thank you.

 

[DR M]

3. Pressed F8 -> Startup Settings

What happens when you do this?

 

[amic_2023]

3. Pressed F8 -> Startup Settings

A 9 (nine) item menu was displayed on a blue screen. Each item can be activated by pressing the corresponding function key (Fn). Photo attached.

 

[DR M]

Here you are!

Have you tried pressing F4 OR F5?

 

[amic_2023]

Please read my post #16, item 4.