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 No comments

61 answers

Sort by: Oldest
  1. Anonymous
    2021-10-25T05:25:25+00:00

    So, what to try first, and what second?

    First

    If you do the "Disable driver signature enforcement" I wrote, & it boots to Windows, it might be easier to work on intelpep.sys there.

    Second

    They'll likely say to try the folders you do have. I guess it's worth a try. The copy command will fail if the folder(s) don't have intelpep.sys in them.

    Like this ^^^...?

    Because i have two folders, if both having the referred file, which folder to choose/copy file from?

    C:\Windows\WinSxS>dir | find "amd64_dual_intelpep"

    10/23/2021 07:44 AM <DIR> amd64_dual_intelpep.inf_31bf3856ad364e35_10.0.19041.1263_none_323b6105e61edd03

    10/23/2021 07:44 AM <DIR> amd64_dual_intelpep.inf_31bf3856ad364e35_10.0.19041.662_none_9b54f10e8fd0ede1

    C:\Windows\WinSxS>

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-10-25T05:33:29+00:00

    Your BCD looks generally OK, but I hate the look of your Firmware Boot Manager...

    Firmware Boot Manager


    identifier {fwbootmgr}

    displayorder {34cac3ad-b95a-11eb-a6b3-e6b8d4f912b2} <<<USB drive

    {bootmgr} <<<Windows Boot Manager

    {34cac3aa-b95a-11eb-a6b3-e6b8d4f912b2} <<<PLDS DVD-RW DH16AFSH

    {34cac3ab-b95a-11eb-a6b3-e6b8d4f912b2} <<<Another PLDS DVD-RW DH16AFSH

    {34cac3ae-b95a-11eb-a6b3-e6b8d4f912b2} <<<Another USB drive

    {27574ef5-1eda-11ec-9fea-ecb1d7406573} <<<CT1000MX500SSD1

    {70b3589b-1400-11ec-9fe5-806e6f6e6963} <<<SanDisk Ultra II 960GB

    {c5cfe03b-c3ba-11eb-9fc7-ecb1d7406573} <<<HL-DT-ST DVDRAM GH24NSD1

    {34cac39f-b95a-11eb-a6b3-e6b8d4f912b2} <<<Startup Menu

    {34cac3a0-b95a-11eb-a6b3-e6b8d4f912b2}

    {34cac3a1-b95a-11eb-a6b3-e6b8d4f912b2}

    {34cac3a2-b95a-11eb-a6b3-e6b8d4f912b2}

    {34cac3a3-b95a-11eb-a6b3-e6b8d4f912b2}

    {34cac3a4-b95a-11eb-a6b3-e6b8d4f912b2}

    {34cac3a5-b95a-11eb-a6b3-e6b8d4f912b2}

    {34cac3a6-b95a-11eb-a6b3-e6b8d4f912b2}

    {34cac3a7-b95a-11eb-a6b3-e6b8d4f912b2}

    {34cac3a8-b95a-11eb-a6b3-e6b8d4f912b2}

    {34cac3a9-b95a-11eb-a6b3-e6b8d4f912b2}

    {261f1c0a-2b25-11ec-9ff1-806e6f6e6963}

    timeout 0

    Have you been in BIOS & did you activate all of those boot items? Many are duplicates. We need to study the situation & deal with it -- it can't be right like that. At least we should get rid of the duplicates. But for now, let's just move the {bootmgr} to be on top of the Displayorder list. That will mean it will try to boot first where now it looks for a USB drive first. This will do it...

    BCDEdit /Enum {fwbootmgr}

    BCDEdit /Set {fwbootmgr} displayorder {bootmgr} /Addfirst

    BCDEdit /Enum {fwbootmgr}

    The second /Enum should show {bootmgr} on top of displayorder. Try to boot to Windows. How nice if it gets there.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-10-25T05:43:00+00:00

    (a) Try the BCDEdit commands I wrote above first. It should be done, but I doubt it fixes the boot problem.

    (b) Next try "Disable driver signature enforcement". I expect the computer will then boot. Then it will probably be easier to deal with Intelpep. Here is what my own file looks like...

    ![Image](https://learn-attachment.microsoft.com/api/attachments/a764da28-9dce-4d78-bdfb-c586bdf49f70?platform=QnA

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-10-25T06:30:28+00:00

    (a) tried but the same thing

    see screenshots attached at the end below

    (b) can not find Startup Settings, well? Booted from DVD Windows 10 21H1 / the PC is 20H2

    Is it near Safe Mode? Can not find how to enter Safe mode... currently...well?

    In the last screenshot exist F8 = Startup Setting, but I think I pressed F8 but nothing done... retry???

    ===================

    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.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-10-25T06:34:11+00:00

    above

    In the last screenshot exist F8 = Startup Setting, but I pressed F8 and

    next, I try "Disable driver signature enforcement".

    getting

    what about:

    1

    Method 1: Rebuild the Boot Configuration Data
    https://appuals.com/how-to-fix-boot-error-0xc000000e-on-windows-10/

    or

    2 https://www.tenforums.com/general-support/186730-loop-prepare-automatic-repair-diagnosing-your-pc-error-6.html#post2317967 Because I have two folders if both have the referred file, which folder to choose/copy the file from?

    C:\Windows\WinSxS>dir | find "amd64_dual_intelpep"

    10/23/2021 07:44 AM <DIR> amd64_dual_intelpep.inf_31bf3856ad364e35_10.0.19041.1263_none_323b6105e61edd03

    10/23/2021 07:44 AM <DIR> amd64_dual_intelpep.inf_31bf3856ad364e35_10.0.19041.662_none_9b54f10e8fd0ede1

    C:\Windows\WinSxS>

    Was this answer helpful?

    0 comments No comments