What's new 
A Windows laptop was disenrolled from Hexnode and both the UEM app and remote assist app were uninstalled. The device no longer appears as enrolled in the Hexnode console, but when trying to reinstall the Hexnode app after a reboot, the installer still says the device needs to be unenrolled first. Has anyone seen this after a Windows device was removed from management? Looking for a way to clean up whatever is blocking the reinstall.
11 Views
Replies (3)
Marked SolutionPending Review
Hexnode Expert
1 day ago
Jun 22, 2026
Marked SolutionPending Review
This can happen if Windows still has stale MDM enrollment records from the previous enrollment, even though the device has already been disenrolled from the Hexnode console. On the affected Windows device, try the following with administrator privileges:
- Open Settings > Accounts > Access work or school.
- If the old work or school management account is still listed, select it and choose Disconnect.
- Open Registry Editor using regedit.
- Check and remove leftover enrollment-related entries under these registry paths:
– HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Provisioning\OMADM\Accounts
– HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Enrollments - Restart the PC.
- Run the Hexnode installer again.
The installer message usually clears once the old Windows enrollment records are removed.
Marked SolutionPending Review
Participant
21 hours ago
Jun 22, 2026
Marked SolutionPending Review
Clearing the stale entries from Access work or school and those registry locations fixed it. After rebooting, the Hexnode app installed normally again.
Marked SolutionPending Review
Hexnode Expert
17 hours ago
Jun 22, 2026
Marked SolutionPending Review
Good to know. For anyone else running into this, the key point is that the Hexnode console may show the device as disenrolled, but Windows can still retain local MDM enrollment artifacts. Removing those local records allows the device to be enrolled again cleanly.
Save