Share via

SCCM - Loop running PXE task sequence

SccmSerg 5 Reputation points
2025-06-12T06:25:22.7733333+00:00

Good morning everyone.

A constant loop occurs when trying to deploy a new machine using PXE.

This occurs after upgrading from version 2409 to 2503. Previously, we were able to deploy new machines successfully.

In the SMSTS.log file, we see the following error:

memcmp(pNetworkPassword, m_bNetworkPasswd, cbNetworkPassword)==0, HRESULT=80004005 (..\pxecrypt.cpp,175)
passwd.ExtractPassword(bVariableKey, DhcpOptions.VariableKeyLen), HRESULT=80004005
PxeGetPxeData failed with 0x80004005

Seems related with network password ... But I don't know ...

Regards and TIA!

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments

4 answers

Sort by: Most helpful
  1. Henrik Thilander 15 Reputation points
    2025-06-26T17:13:35.86+00:00

    Had the exact same problem and had to solve it by reinstall and set password for PXE. Hope this bug gets fixed with a hotpatch very soon!!

    Was this answer helpful?

    3 people found this answer helpful.

  2. muels7 5 Reputation points
    2025-07-07T18:24:49.31+00:00

    Having the same issue. Looks like adding a password to the DP solves the issue. No where in the release notes did MS say this was a requirement now.

    Not a huge deal, but now I need to get this info out to all my helpdesk techs across the org for when they need to image a device. In our environment, a password isn't really necessary.

    Was this answer helpful?

    1 person found this answer helpful.

  3. Chris 5 Reputation points
    2025-06-18T14:53:57.49+00:00

    Hi,

    we had the exact same issue with the same error message after the upgrade to 2503.

    The DP was set up without a PXE password.

    We disabled, PXE on the DP, enabled PXE again and set a PXE password. That fixed it for us.

    Best regards

    Was this answer helpful?

    1 person found this answer helpful.

  4. Rüegger Jasmin 0 Reputation points
    2025-12-15T15:29:07.6666667+00:00

    This was fixed for us with the hotfix for 2503. But there was a new error with client certificate selection, so we rolled back to 2409.

    Tested 2509 today and experienced the same pxe problem with this version also. It works when I set a pxe password, but that's not something we will take into production.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.