Forum Discussion
Autopilot error 0x80280009 when testing in Hyper V.
Thanks for your reply.
Does anyone know if attestation will work in the future for vm's? Because its an more efficient way for testing purposes, so you do not have to use a psychical test system.
well, if you happen to have a screenshot of that error.. i am writing “something” about it and whats coming 😛
- Hi Rudy,
I will add a screenshot soon to this post. Im testing now with a laptop but still getting some other error codes when testing autopilot. One of them is 0x80180005 during registering the device for mobile management. I deleted the device from Endpoint Manager before starting autopilot. What i didnt test was also deleting the device serialnumber from the autopilot devices, and re-upload the hardware hash. I was thinking about testing that too as my next step.- Hi.. thanks.. well that error you mentioned could be a lot.. one of them could be this one https://call4cloud.nl/intune-device-enrollment-errors-mdm-enrollment/#9_0x80180005
Regular autopilot enrollment or selfdeploy/prepro ? as that error could also mean thedevice wasn't allowed for prepro/self deploy based on the settings in the ap profile
https://call4cloud.nl/autopilot-0x80180005-preprovisioning-disabled/I readed the first link, by deleting the file c:\windows\servicestate\wmansvc\AutopilotDDSZTDFile.json.
I tested this but no success for me. When i scan the QR code after the autopilot failed, see below the output i'm getting. Normally the pre-provision doesn't take longer than 30 minutes, so i've changed the value of Show an error when installation takes longer than specified number of minutes from 60 back to 30, in the Enrollment Status Page.
{"Version":"1.0.0","Id":"c5399367-77c9-40a6-a28e-077dc08c69f1","ZtdId":"da788b00-7aa5-495c-9264-c9a627318710","PKID":"","SerialNumber":"","SequenceBlockNumber":1,"TotalBlocks":1,"Result":"Failure","ElapsedTimeMilliseconds":3683857}
The Deployment Mode of the Autopilot profile is User-Driven and the option Allow pre-provisioned deployment is set to Yes.
Also when i try again after pre-provisioning failed, the first step succeeded, but the 2th step everything failed and at the Apps part it says it needs a reboot. But the reboot doesnt help either. When i just log into the machine with my email adres, it looks fine. Some apps are installed and the rest is installing after logging in.