Can NOT start up my PC: HP Z440: Prepare Automatic Repair - Diagnosing your PC

Anonymous
2021-10-23T05:26:32+00:00

Can NOT start up my PC: HP Z440

When booting up:

Prepare Automatic Repair - Diagnosing your PC

I see always

I have tried

1

Safe Mode, Uninstall the latest quality update, Restore back to point 18-10-2021 :

same symptom

2

Troubleshoot> Advanced options > Startup Repair:

same symptom

Status

Today in the morning I turn ON PC, I was offline[no cable ethernet], and while working prompt for an update[while was dis-connected], after this connected - checked some Gmail, etc. and after 30-min press UPDATE & RESTART,

And got this problem on startup...

well...?

I have a backup of C:/ with Acronis... I think of October 2021

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

61 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-10-25T02:41:22+00:00

    I reply from mobile device

    I again ERROR but used another forum post cmd

    I WILL TRY AGAIN YOUR COMMANDS ABOVE

    OK

    SEE BELOW

    I can NOT proceed , well?

    Microsoft Windows [Version 10.0.19041.928]
    (c) Microsoft Corporation. All rights reserved.
    X:\Sources>notepad
    X:\Sources>Bcdedit /enum | find "osdevice"
    osdevice partition=C:
    X:\Sources>Sfc /Scannow /OFFBOOTDIR=C:\ /OFFWINDIR=C:\Windows
    Beginning system scan. This process will take some time.
    There is a system repair pending which requires reboot to complete. Restart,Windows and run sfc again.
    X:\Sources>

    ==================
    Microsoft Windows [Version 10.0.19041.928]

    (c) Microsoft Corporation. All rights reserved.

    X:\Sources>notepad

    X:\Sources>Bcdedit /enum | find "osdevice"
    osdevice partition=C:

    X:\Sources>mkdir C:\scratch

    X:\Sources>DISM /Image:C:\ /Cleanup-Image /RevertPendingActions /ScratchDir:C:\Scratch

    Deployment Image Servicing and Management tool

    Version: 10.0.19041.746

    Image Version: 10.0.19042.1263

    Reverting pending actions from the image...

    Error: 0x800f082f

    An error occurred reverting the pending actions from the image.
    For more information, review the log file.

    The DISM log file can be found at X:\windows\Logs\DISM\dism.log
    X:\Sources>

    ====
    ATTACHED log FILE https://www.tenforums.com/general-support/186730-loop-prepare-automatic-repair-diagnosing-your-pc-error-6.html

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-10-25T02:32:09+00:00

    Thank you for guidance

    I will try soon...

    You say

    (2) I'm puzzling over why D: has become C: now in your recovery environment

    I THINK BECAUSE DISCONNECTED A SATA CABLE OF THE 4TB HDD MY DATA DRIVE SO HAVING ONLY ONE DRIVE... my SSD 1TB...

    THIS DONE TO NOT TOUCH THIS HDD BY ERROR...

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-10-25T02:05:00+00:00

    (1) This is it...

    DiskPart

    List Vol

    Exit

    DISM /Image:C:\ /Cleanup-Image /RestoreHealth

    SFC /ScanNow /OffBootDir=C: /OffWinDir=C:\Windows

    That presumes your Windows partition is still C:...

    Volume ### Ltr Label Fs Type Size Status Info

    Volume 0 C System NTFS Partition 930 GB Healthy <<<Windows

    Volume 1 FAT32 Partition 100 MB Healthy Hidden <<<EFI

    Volume 2 D NTFS Partition 502 MB Healthy Hidden <<<Recovery

    Volume 3 E USB DISK FAT32 Removable 57 GB Healthy

    After that, try to boot to Windows. If it fails, then...

    (a) "Troubleshoot > Advanced Options > Startup Settings".

    (b) Click the "Restart" button that is there.

    (c) Select "Disable driver signature enforcement" by entering its number.

    See whether you can boot to Windows. Then, we'll have to discover why it didn't like IntelPep.sys. That's a legit file under normal circumstances. I've got one myself.

    (2) I'm puzzling over why D: has become C: now in your recovery environment. Did you change that yourself? Or did you use the DVD for the first time instead of your EFI partition? That could do it. But the bigger puzzle is that SrtTrail.txt is now saying...

    Session details

    System Disk = \Device\Harddisk0 <<<Your first one said ...Harddisk1

    Windows directory = C:\Windows <<<Your first one said D:\Windows

    I don't know how/why the Harddisk changed. Let's see...

    DiskPart

    List Disk

    === Note the number of each disk listed, & ===

    === use each one instead of x in the following ===

    Select Disk x

    List Part

    === Then exit DiskPart ===

    Exit

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-10-24T17:34:56+00:00

    After, Searching error codes online,...

    1
    So, is NOT A problem use a DVD 21H1 Windows 10, in a 20H2 PC ...? TRUE / FALSE

    2
    RUN **from X: or C:?**3
    run just the:
    sfc /scannow
    without parameters???

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-10-24T16:20:25+00:00

    I ran:

    BCDBoot C:\Windows

    I got a Success message

    but when went boot getting an error: // DVD boot from was 21H1 but OS is 20H2, is it matters? Following is the Log file,...well?

    Image

    when went to repair getting:

    Image

    Logfile:

    Startup Repair diagnosis and repair log

    Last successful boot time: ‎10/‎12/‎2021 6:25:29 AM (GMT)

    Number of repair attempts: 40

    Session details

    System Disk = \Device\Harddisk0

    Windows directory = C:\Windows

    AutoChk Run = 0

    Number of root causes = 1

    Test Performed:

    Name: Check for updates

    Result: Completed successfully. Error code = 0x0

    Time taken = 0 ms

    Test Performed:

    Name: System disk test

    Result: Completed successfully. Error code = 0x0

    Time taken = 0 ms

    Test Performed:

    Name: Disk failure diagnosis

    Result: Completed successfully. Error code = 0x0

    Time taken = 0 ms

    Test Performed:

    Name: Disk metadata test

    Result: Completed successfully. Error code = 0x0

    Time taken = 671 ms

    Test Performed:

    Name: Disk metadata test

    Result: Completed successfully. Error code = 0x0

    Time taken = 16 ms

    Test Performed:

    Name: Target OS test

    Result: Completed successfully. Error code = 0x0

    Time taken = 16 ms

    Test Performed:

    Name: Volume content check

    Result: Completed successfully. Error code = 0x0

    Time taken = 93 ms

    Test Performed:

    Name: Boot manager diagnosis

    Result: Completed successfully. Error code = 0x0

    Time taken = 0 ms

    Test Performed:

    Name: System boot log diagnosis

    Result: Completed successfully. Error code = 0x0

    Time taken = 0 ms

    Boot manager generic failure 0xc000000e

    Test Performed:

    Name: Event log diagnosis

    Result: Completed successfully. Error code = 0x0

    Time taken = 32 ms

    Test Performed:

    Name: Internal state check

    Result: Completed successfully. Error code = 0x0

    Time taken = 0 ms

    Test Performed:

    Name: Check for installed LCU

    Result: Completed successfully. Error code = 0x0

    Time taken = 3922 ms

    Test Performed:

    Name: Check for installed driver updates

    Result: Completed successfully. Error code = 0x0

    Time taken = 1312 ms

    Test Performed:

    Name: Check for pending package install

    Result: Completed successfully. Error code = 0x0

    Time taken = 2750 ms

    Root cause found:

    A recently serviced boot binary is corrupt.

    Repair action: Abort pending update installations

    Result: Failed. Error code = 0x82f

    Time taken = 4109 ms

    Session details

    System Disk = \Device\Harddisk1

    Windows directory = D:\WINDOWS

    AutoChk Run = 0

    Number of root causes = 1

    Test Performed:

    Name: Check for updates

    Result: Completed successfully. Error code = 0x0

    Time taken = 0 ms

    Test Performed:

    Name: System disk test

    Result: Completed successfully. Error code = 0x0

    Time taken = 0 ms

    Test Performed:

    Name: Disk failure diagnosis

    Result: Completed successfully. Error code = 0x0

    Time taken = 0 ms

    Test Performed:

    Name: Disk metadata test

    Result: Completed successfully. Error code = 0x0

    Time taken = 735 ms

    Test Performed:

    Name: Disk metadata test

    Result: Completed successfully. Error code = 0x0

    Time taken = 15 ms

    Test Performed:

    Name: Target OS test

    Result: Completed successfully. Error code = 0x0

    Time taken = 16 ms

    Test Performed:

    Name: Volume content check

    Result: Completed successfully. Error code = 0x0

    Time taken = 78 ms

    Test Performed:

    Name: Boot manager diagnosis

    Result: Completed successfully. Error code = 0x0

    Time taken = 0 ms

    Test Performed:

    Name: System boot log diagnosis

    Result: Completed successfully. Error code = 0x0

    Time taken = 0 ms

    Test Performed:

    Name: Event log diagnosis

    Result: Completed successfully. Error code = 0x0

    Time taken = 31 ms

    Test Performed:

    Name: Internal state check

    Result: Completed successfully. Error code = 0x0

    Time taken = 0 ms

    Root cause found:

    Startup Repair has tried several times but still cannot determine the cause of the problem.

    Session details

    System Disk = \Device\Harddisk1

    Windows directory = D:\WINDOWS

    AutoChk Run = 0

    Number of root causes = 1

    Test Performed:

    Name: Check for updates

    Result: Completed successfully. Error code = 0x0

    Time taken = 0 ms

    Test Performed:

    Name: System disk test

    Result: Completed successfully. Error code = 0x0

    Time taken = 0 ms

    Test Performed:

    Name: Disk failure diagnosis

    Result: Completed successfully. Error code = 0x0

    Time taken = 0 ms

    Test Performed:

    Name: Disk metadata test

    Result: Completed successfully. Error code = 0x0

    Time taken = 734 ms

    Test Performed:

    Name: Disk metadata test

    Result: Completed successfully. Error code = 0x0

    Time taken = 16 ms

    Test Performed:

    Name: Target OS test

    Result: Completed successfully. Error code = 0x0

    Time taken = 16 ms

    Test Performed:

    Name: Volume content check

    Result: Completed successfully. Error code = 0x0

    Time taken = 93 ms

    Test Performed:

    Name: Boot manager diagnosis

    Result: Completed successfully. Error code = 0x0

    Time taken = 0 ms

    Test Performed:

    Name: System boot log diagnosis

    Result: Completed successfully. Error code = 0x0

    Time taken = 0 ms

    Test Performed:

    Name: Event log diagnosis

    Result: Completed successfully. Error code = 0x0

    Time taken = 16 ms

    Test Performed:

    Name: Internal state check

    Result: Completed successfully. Error code = 0x0

    Time taken = 0 ms

    Root cause found:

    Startup Repair has tried several times but still cannot determine the cause of the problem.

    Was this answer helpful?

    0 comments