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.
