Windows device says already enrolled during Hexnode re-enrollmentSolved

This can happen if Windows still has orphaned MDM enrollment entries in the registry, even when no work or school account appears in Settings. On the affected Windows device, check the following registry locations:

1. Open Registry Editor and go to: HKLM\SOFTWARE\Microsoft\Provisioning\OMADM\Accounts. If any folders are present under Accounts, delete them. If required, the entire Accounts folder can also be removed.
2. Then go to: HKLM\SOFTWARE\Microsoft\Enrollments. In this location, Windows may keep a couple of default system folders that cannot be deleted. Leave those as they are. Delete any other non-default folders present under Enrollments.

After clearing these leftover enrollment records, download the latest Hexnode Windows installer from the enrollment page of your Hexnode portal and run that installer. Avoid using an older installer that was downloaded previously.

We tried checking Access work or school first and there was nothing listed. The device had also been reformatted, so we assumed there couldn’t be anything left. The error still showed up until our IT team checked the registry paths.

The key part is that a reformat or account removal does not always clear every MDM enrollment artifact Windows uses during enrollment. If the Hexnode installer detects those stale OMADM or enrollment records, it can treat the device as already enrolled. Make sure all entries under HKLM\SOFTWARE\Microsoft\Provisioning\OMADM\Accounts are removed, and that only the default system folders remain under HKLM\SOFTWARE\Microsoft\Enrollments. Once that cleanup is complete, use a freshly downloaded Hexnode installer for re-enrollment.

Confirmed this fixed it for us. After IT deleted the leftover registry entries and used the latest installer, the Windows desktop enrolled successfully.