Our company received a report that someone in another part of the world is seeing our customized Windows Autopilot enrollment page when setting up a very old desktop, roughly a first-generation Core i5 system. They claim Windows setup proceeds normally when a particular GPU is removed, but the company login prompt appears when that GPU is installed. We have never knowingly owned hardware this old or that specific graphics card. Could a motherboard or device hardware hash somehow be associated with our Autopilot tenant, or is the GPU connection more likely coincidental?
3 Answers
The most useful evidence would be the system serial number, motherboard details, the GPU model and serial if available, and screenshots of the enrollment screen. Check the device records and enrollment assignments in your tenant, then confirm whether the machine is actually registered there. If the serial does not match, it may have belonged to another company and the wrong tenant is being displayed or the device has been incorrectly associated.
The GPU by itself should not be an intended way to bypass or trigger Autopilot. The enrollment identity is calculated from multiple hardware attributes, and removing a component generally should not turn enrollment off. I would verify exactly what steps are being performed, whether Windows is actually being reinstalled each time, and whether the same machine is being tested both ways.
Autopilot enrollment is based on the device identity or hardware hash, not simply whether a particular graphics card is installed. A second-hand, warranty-repaired, or improperly decommissioned machine could still be registered to another organization. Getting the computer’s serial number and comparing it with your Autopilot inventory would be a good first step.
A motherboard replacement can also create confusing ownership problems if the replacement board was previously registered to a different organization. In cases like that, the manufacturer and Microsoft may need to help remove the device from the old tenant.
There have been reports of hardware-identity edge cases and possible hash collisions, but that would be unusual. The apparent GPU dependency could instead involve a different boot path, firmware behavior, driver initialization, or even two different machines being confused.