Cannot Reseal Windows 11 device while pre-provisioning

Rudy_Ooms_MVP , Bruce S So now I have 2 devices to test with. 1 device that is just not able to download a profile what so ever (Windows 11) and another device, that will download a profile but the reseal option is not shown. That is how this threat started. Here's one final update:

The device that could not reseal: 

First I tried to set the DMA and credential guard settings in the MDE security baseline to Not Configured on at a time and re-enrolled using pre-provisioning. That did not work. the Reseal option was still not showing. I ended up at the login screen like before. Strange enough though, when I reset the device from Intune, it would end up in the user  flow like it would, after resealing. 

I ended up with removing every policy assignment I had except for the update rings targeting users and still no reseal option.

Then I deleted the following registry key:

HKLM:\SOFTWARE\Microsoft\Provisioning\SyncML\RebootRequiredURIs\ManagePreviewBuild

started pre-provisioning again, and yes! A nice reseal button!

I'm somewhat disappointed that pre-provisioning is not working out of the box with Windows 11 and hope this will be fixed sometime soon.

Then for the device that can't find/load a profile:

Rudy_Ooms_MVP I did a fiddler trace and that one gave me a nice 807 - ZtdDeviceIsNotRegistered

The error description: The device being deleted or configured does not exist in the service.

Michael Niehaus has a nice https://oofhours.com/2019/07/07/what-happens-when-you-register-a-device-with-windows-autopilot/ explaining what might be the cause:  This would typically only happen if Intune and the Windows Autopilot deployment service are out of sync (e.g. you removed a device from Microsoft Store for Business, and then tried to remove it via Intune before Intune had noticed it disappeared).

Off-course I checked the store, made sure all is in-sync, waited a long long time, deleted every trace I could find for this device, re-installed windows 10, and still no luck here. It really seems like this device is no longer able to pre-provision.

So I'm trying to enroll the device without pre-provisioning and then I see a nice "How would you like to set up?" question.. LoL Rudy_Ooms_MVP I ended up at https://call4cloud.nl/2022/05/the-41-year-old-hardware-hash-who-knocked-up-autopilot-and-felt-superbad-about-it/ again. 

Up until now, I uploaded the hash using PowerShell -online from the OOBE. so I decided to give it one last try and upload the CSV manually. Still no luck... I did manage to collect the logs from the device again and will try to dive in again, but for today, I'm feeling beet-up by Autopilot 😄