Disable Autopilot?

D

darkroom4

New Member
Messages
5
Reaction score
1
What do I do to disable Autopilot while creating an image?

setting, registry setting, service disable, anything?

We've had couple of laptops in the past that were never deleted from Autopilot registry and during OOBE setup Autopilot enrolment popped up
would like to not have to deal with it
 
While NTLite allows you to remove the Autopilot component, I tried to see if that works for a modern W11 image (24H2). The short answer is no, OOBE gets stuck in ZDP and never proceeds past it.

The normally suggested "hacks" to defeat Autopilot include:
Dead company, let me keep PC but cant bypass Intune/Autopilot

1. Install Windows without any network access. But that doesn't work if your PC was previously imaged, and someone set the FORCED_NETWORK_FLAG. This embeds a new UEFI variable for Autopilot_Marker, and when OOBE detects this UEFI setting, it prevents OOBE from finishing as long as there's no network.

Michael Niehaus suggests disabling Secure Boot while installing Windows w/o a network.

2. Using the unattended file, force install Home edition (because Home doesn't have AP support), and then upgrade using a Pro activation key.

3. Defeat the HW hash by replacing at least one piece of important hardware, ie. swap boot drives btw two PC's.
 
thanks for suggestions; I'll look into it

do you thing HW hash can be defeated if you swap two modules between slots and or if single module, to the other slot?

Does Autopilot enrollment ever expire?
 
darkroom4 said:
do you thing HW hash can be defeated if you swap two modules between slots and or if single module, to the other slot?
Click to expand...
HW hash isn't dependent on DIMM locations, but I think the total number of DIMM's (and therefore max memory) is hashed.
Breaking down the Windows Autopilot hardware hash

darkroom4 said:
Does Autopilot enrollment ever expire?
Click to expand...
Technically no. Once your tenant registers a device, it goes into the global "every AP registered device in the world" database that's queried when OOBE reaches that stage. You're supposed to unregister devices yourself. Obviously if your company or IT org disappears, leaving no one with the admin rights to retire devices – sucks to be you.

MS could bulk remove PC's after tenant expiration but I don't think they want to get involved in mediating disputes. This is a huge problem for recycled PC's, where someone donates used gear but doesn't understand the whole AP situation. Or you're unwittingly buying stolen PC's off eBay.
 
garlin said:
While NTLite allows you to remove the Autopilot component, I tried to see if that works for a modern W11 image (24H2). The short answer is no, OOBE gets stuck in ZDP and never proceeds past it.
Click to expand...
i (sadly) can confirm this.
 
If you are talking about this component
Code: 
c>autopilot 'autopilot'</c>

I remove it in the image and no problem to install Windows
I use a "fully unattended" too (SkipOOBE, etc...)
 
Last edited:
You must log in or register to reply here.
Back
Top