OSD Broke after updating to Dec 2024 ADK/PE and Configmgr 2503 - "Failed to initialize task sequence advertisement (Code 0x80004005)"

[Aurock]

Last week I updated from an old Win10 ADK to the Win11 December 2024 ADK and associated PE Package.  Then I installed the v2503 update for Configmgr.  After the upgrade, my OSD is completely broken.  I've tried creating new USB boot media based on WinPE 11 to run my Win11 TS, and also tried pxe booting an existing client to run my Old Win10 TS that was working prior to the upgrade.  Both fail, rebooting immediately after the task sequence background screen loads.  
Using the Win11 media, I can't seem to get the diagnostic cmd prompt to work for some reason, I did enable it in the boot media properties but spamming F8 as the background comes up does nothing.  On the Win10 boot media the TS progress dialog does come up for a moment, and on that one I'm able to pull up the cmd prompt.  I've collected the smsts.log and will attach it here, but the main error that I think looks relevant is "Failed to initialize task sequence advertisement CHC2010C (Code 0x80004005)", then later it says that there is no task sequence available to the computer.  

I've found virtually nothing on this error when searching online, and I'm kind of stumped on where to go next.  Anyone seen this before?  Or have suggestions at least on where I could find more detail than this one error in the SMSTS.log?  

smsts.log

[anyweb]

the last error in your provided log is "There are no task sequences available to this computer.. Please ensure you have at least one task sequence deployed to this computer.
Unspecified error (Error: 80004005; Source: Windows"

 

so.. make sure that whatever you are pxe booting actually is in a collection that is targeted by a task sequence

[Aurock]

It is in the collection.  The error higher up, "Failed to initialize task sequence advertisement CHC2010C (Code 0x80004005)", actually contains the Deployment ID for the deployment of the task sequence to the collection.  I interpret the error to mean that it is seeing the task sequence as advertised to the client, but for whatever reason it can't do something with it.  Then since no other TS are assigned to the client/collection, it ends up saying that there are no task sequences available and stopping there.  I'm open to other interpretations though if you don't think that's right.

[anyweb]

it could simply be corrupt task sequence policy, can you do a test and deploy the exact same TS to either the same collection or another collection that this device is in, and retry

 

I tested pxe boot just now in my 2503 lab and all is good, even in a fully PKI environment

[Aurock]

I deleted the deployment and recreated it, targeting the same collection, and am still getting the same result.  

Not surprised that it's working for you.  I don't think it's necessarily a problem with 2503, more likely just something wrong with my environment that was caused/triggered by having upgraded the ADK and configmgr. I'm considering restoring the server back to the backup before I installed the updates, and running the upgrade again, in case maybe something went invisibly wrong during the upgrade.  Maybe do a bit of cleanup first, reboot immediately before starting the upgrade this time, etc.  

[anyweb]

can you share your smspxe.log file with me and i'll take a look, it may reveal the source of the problem,