I’m running into something odd and hoping someone here has seen this before. I just disenrolled a Windows device, and everything seemed to complete fine. But when I try running the setup package again, it refuses and says the device is already associated. Any idea what might be hanging around?
Disenrolled the device but some settings are still stuckSolved
Replies (4)
Yeah, that does sound familiar. Windows sometimes holds onto parts of the previous management setup. Before trying anything else, check whether the old work account is still linked under the Access work or school section in Settings. If it’s there, disconnecting it usually helps. That alone has fixed it for me a few times.
Just checked, and the account was still there. Removed it, but the setup is still getting blocked. Looks like something deeper is sticking around.
Hey @tomas . This usually happens when the device keeps leftover enrollment data in the registry, even after it is removed from the console. Clearing those entries should fix it.
Here’s what you can do: open Registry Editor and then,
- Remove old management profiles.
Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Provisioning\OMADM\Accounts. Delete every folder you see inside Accounts. These are leftover management profiles.
- Remove previous enrollment data.
Open HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Enrollments. Delete all folders under Enrollments. These are the records that tell Windows that the device is still enrolled.
Once both locations are cleared, Windows should no longer think the device is managed.
Best Regards,
Isabel Lora
Hexnode UEM
Cleared both sets of entries, and that finally solved it. The setup went through without any errors. Thanks a lot for the help!