Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING An error 0xc000000f occurs during the execution of the Task Sequence step (Restart in Windows PE).

  • Thread starter Thread starter Gruvz
  • Start date Start date
  • Replies Replies 0
  • Views Views 825

Gruvz

New Member
Messages
1
Reaction score
0
Points
1
Colleagues, good afternoon!
I've been struggling with an issue for a week now, and I would like to ask for your help in resolving it.
Thank you in advance!
The task at hand is quite straightforward: to reinstall Windows 11 Enterprise LTSC 24H2 on a computer that already has Windows 11 Enterprise LTSC 24H2 installed.

After I launch this task through the Software Center, the task sequence progresses to the "Restart in Windows PE" step, at which point a general error (0x80004005) occurs, and the computer does not restart because the step was not completed.
If the computer is restarted after the error occurs, a boot error 0xc000000f appears during startup. This error is relatively easy to resolve by repairing the boot using the command BOOTREC /REBUILDBCD. The error is attached in the file named "error 0xc000000f".

While examining the smsts.log file, I see the following lines:

SMSTS 80004005.png

Based on the log file and a thorough review of all similar issues found online (I have repeatedly studied all the topics on all forums), I have taken the following steps:
  1. Created new Task Sequences.
  2. Set "Restart in Windows PE" as the first step.
  3. Reinstalled the operating system on the problematic computers using a clean image downloaded from Microsoft.
  4. Added drivers to WinPE.
  5. Disabled Secure Boot and SCM in BIOS.
  6. Updated BIOS.
  7. Updated SCCM to the latest version 2409 build 5.0.9132.100.
  8. Updated ADK to the latest available version.
However, none of these steps yielded any results. I decided to narrow down the problem to better understand which side the issue originates from, and here's what I found:

The problem occurs on two different computer models:

  1. MSI PRO DP10 13M (MiniPC)
  2. Custom-built computer from 2024 (with modern hardware)
I decided to try these steps on other modern computers and virtual machines, and I was quite surprised, but the problem with passing the "Restart in Windows PE" step did not occur. They were able to reboot the computer and start the OS installation. Here are the computers that did not experience the issue:

  1. HP EliteBook 840 G10 laptop
  2. Acer d18w3 (MiniPC)
  3. Custom-built computer from 2024
  4. Virtual machine in VMware
After examining all the computers, I confirmed that they all use UEFI BIOS and GPT disk partitioning. Moreover, on the computers where everything works fine, the Secure Boot setting in BIOS is even enabled.
If you look at the two smsts files, one with a successful installation and the other with an unsuccessful one, you can also notice a strange error listed below in the screenshot. However, considering that this error did not affect the successful installation on the HP EliteBook 840 G10 laptop, I think it can be ignored.

Igrore warrning.png

I will also attach the successful smsts log file; perhaps it can shed some light on the error.

I honestly admit that I'm at a dead end and I ask for your help in solving my problem. If logs or any additional information are needed, I will be happy to provide them. I would even be relieved if someone tells me that the issue is with the hardware and cannot be solved in my case, because this problem has been stuck in my head, and I would gladly be rid of it.
 

Attachments

  • error 0xc000000f.png
    error 0xc000000f.png
    67.7 KB · Views: 4

Forum statistics

Threads
7,135
Messages
27,868
Members
18,157
Latest member
rajkumarkrishnan
Back
Top