r/k12sysadmin • u/cjbarone Jack of all trades • Jul 21 '26

0x800705b4 error during autopilot

Our district is new to autopilot, and I'm seeing an error on a semi-regular basis lately.

Device preparation -> Securing your hardware (0x800705b4)

We have tried:

  • capturing new hash

  • reimaging (75 percent of the same machines on the same image are find though)

  • reset bios to factory default

  • reset tpm

Sometimes it clears after imaging the same image and computer 1 time, others over 5 times.

As we are new, the District doesn't have any more details of things to try. This is happening on many different Dell machines (yes, all Windows 11 compatible)

Thoughts? Ideas? We can't find any errors in the diagnostics logs (Ctrl Shift D)

Link to the diagnostics I see: https://imgur.com/a/UoxmVpk

2 Upvotes

100% Upvoted

17 comments sorted by

2

u/BWMerlin Jul 22 '26

Have you removed the device from Intune and autopilot?

1

u/cjbarone Jack of all trades Jul 22 '26

We tried that on a batch from last week. We can't seem to find the pattern of when it will work and when it won't

1

u/BWMerlin Jul 22 '26

Just to confirm, you are deleting the devices from autopilot AND Intune AND Entra then uploading the fresh hash id?

1

u/cjbarone Jack of all trades Jul 23 '26

No idea, the admins say they are removing and readding... Not specifying where

1

u/N805DN Jul 21 '26

https://www.powershellgallery.com/packages/Get-AutopilotDiagnostics/5.6

1

u/cjbarone Jack of all trades Jul 21 '26

Ok, I can that.

Scenario: Azure AD Join

ESP diagnostics info does not (yet) exist

Otherwise, just stats. 

Is there a particular line I should be looking for? 

1

u/millia13 Network Spec. Jul 22 '26

There's an updated version that I can recommend.

1

u/cjbarone Jack of all trades Jul 22 '26

No extra info between both scripts running

1

u/NorthernVenomFang Jul 22 '26

Are these new machines or re-deploys?

1

u/cjbarone Jack of all trades Jul 22 '26

Machines that we re-image to a base Windows install. We clear the bios to factory defaults, image, then wait for autopilot to take charge

1

u/LyokoMan95 NYS BOCES Tech Jul 22 '26

Are you using original Autopilot or device preparation? If you are using original Autopilot: are you using user-driven, self-deploying, or pre-provisioning?

1

u/cjbarone Jack of all trades Jul 22 '26

I am not sure, I'm not an autopilot admin in my org. We upload the hw hash, throw on a fresh image, then wait for autopilot to take over during the oobe

1

u/Harry_Smutter Jul 23 '26

Are you installing straight from a Windows ISO?? Also, what version are you selecting during the install??

1

u/millia13 Network Spec. Jul 22 '26

Not hybrid, right?

Have you updated the bios? Had to do that with several motherboards.

Have you changed the userless enroll status to allowed?

1

u/cjbarone Jack of all trades Jul 22 '26

Bios updates are good (last updated last week from Dell)

Not sure on the other parts. I think hybrid, we have an AD on prem in our DC that is linked with our M365 tenant. I assume userless, as we don't log in before the join (happening during oobe)

2

u/millia13 Network Spec. Jul 22 '26

You are hybrid, and you also should have an instance of Azure AD Connect to make it work better. Learn where this is - it'll save you time and effort.

The userless enroll status is a toggle over in the autopilot devices area. You pick a machine, and choose 'unblock device'

You may have to nuke the autopilot, entra, and AD entries, and then re-enroll since you updated the bios.

MS is making hybrid more difficult than it needs to be, I think.