PXE Boot works, then restarts before task sequence choice

[xerxes2985]

Not sure what occurred, PXE boot is successful.

However, the Microsoft Configuration Manager background loads... sits for a couple seconds.. then the system reboots. I have attached part of the SMSPXE.log from the most recent attempt:

I have X'd out the IPs and what not. 
 

============> Received from client:	SMSPXE	8/24/2023 1:36:34 PM	4524 (0x11AC)
 Operation: BootRequest (1)  Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 0001E240
 Sec Since Boot: 65535 Client IP: x.x.x.x Your IP: 000.000.000.000 Server IP: x.x.x.x Relay Agent IP: 000.000.000.000
 Addr: a4:4c:c8:19:2e:40:
 Magic Cookie: 63538263
 Options:
  Type=93 Client Arch: EFI BC
  Type=97 UUID: 0044454c4c5a0010338054c8c04f424832
  Type=53 Msg Type: 3=Request
  Type=60 ClassId: PXEClient
  Type=55 Param Request List: 3c8081828384858687
  Type=250 0c01010d020800010200070e010105040000000aff	SMSPXE	8/24/2023 1:36:34 PM	4524 (0x11AC)
Looking for bootImage LIB003F7	SMSPXE	8/24/2023 1:36:34 PM	8596 (0x2194)
Prioritizing local MP https://servername.	SMSPXE	8/24/2023 1:36:34 PM	8596 (0x2194)
Using Management Point: https://servername	SMSPXE	8/24/2023 1:36:34 PM	8596 (0x2194)
SSL, using authenticator in request.	SMSPXE	8/24/2023 1:36:34 PM	8596 (0x2194)
In SSL, but with no client cert.	SMSPXE	8/24/2023 1:36:34 PM	8596 (0x2194)
SSL, using authenticator in request.	SMSPXE	8/24/2023 1:36:34 PM	8596 (0x2194)
In SSL, but with no client cert.	SMSPXE	8/24/2023 1:36:34 PM	8596 (0x2194)
============> REQUEST Reply to client ([x.x.x.x:68]) Len:447	SMSPXE	8/24/2023 1:36:34 PM	8596 (0x2194)
 Operation: BootReply (2)  Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 0001E240
 Sec Since Boot: 65535 Client IP: x.x.x.x Your IP: 000.000.000.000 Server IP: x.x.x.x Relay Agent IP: 000.000.000.000
 Addr: a4:4c:c8:19:2e:40:
 BootFile: smsboot\x64\bootmgfw.efi
 Magic Cookie: 63538263
 Options:
  Type=53 Msg Type: 5=Ask
  Type=54 Svr id: x.x.x.x
  Type=97 UUID: 0044454c4c5a0010338054c8c04f424832
  Type=60 ClassId: PXEClient
  Type=243 01515c534d5354656d705c323032332e30382e32342e31332e33312e30392e303030342e7b35353838433132432d333241452d344638352d423633322d3539433637353937313139367d2e626f6f742e766172
  Type=252 5c534d5354656d705c323032332e30382e32342e31332e33312e30382e30392e7b35353838433132432d333241452d344638352d423633322d3539433637353937313139367d2e626f6f742e62636400	SMSPXE	8/24/2023 1:36:34 PM	8596 (0x2194)
<============ REQUEST Reply (end)	SMSPXE	8/24/2023 1:36:34 PM	8596 (0x2194)

Things I have already done:

Rebuilt boot image and made it available to PXE distribution.
Restarted server
Restarted WDS
Ensured task sequence is advertised to a collection that the computer is a member of.

No luck and I can't seem to find any errors. 

[anyweb]

the reason for the reboot is it either can't see a task sequence or missing drivers, but we are not seeing that in this log,

is there anything further logged in smsts.log ?

[xerxes2985]

Unfortunately no. Each time it PXE boots this is all that shows up in the log. If need be, I can remove/reinstall the DP and any other components. 

[anyweb]

on the client, press f8 to bring up a cmd prompt, then click on your available task sequence, browse to x:\windows\temp\smstslog and find and download/attach the smsts.log file here please

 

[Sven2788]

Try a diskpart/select disk 0/ clean

Then reboot and try again.

I've seen this on a few machines when booting off a USB flash drive and it stumped me. The above disk part resolves it.

[xerxes2985]

@anyweb unfortunately pressing F8 (even though I have the box checked on my boot image) is not working.

[xerxes2985]

2 hours ago, Sven2788 said:

Try a diskpart/select disk 0/ clean

Then reboot and try again.

I've seen this on a few machines when booting off a USB flash drive and it stumped me. The above disk part resolves it.

Tried this as well. No luck.

[anyweb]

16 minutes ago, xerxes2985 said:

@anyweb unfortunately pressing F8 (even though I have the box checked on my boot image) is not working.

if you have enabled it on the boot image, then redistribute it to the distribution point(s) and try again

 

 

[xerxes2985]

28 minutes ago, anyweb said:

if you have enabled it on the boot image, then redistribute it to the distribution point(s) and try again

 

 

Same result. Should I contemplate removing the DP role and recreating the DP? 

[anyweb]

then something is not right, if you enable f8 command support then it should work, if it is not then you are working on the wrong boot image to the one in the console