Forum Discussion
Sync cannot be initialized 0x80190194
I have one device which cannot be synced since 2 month.
I am getting the message: Sync cannot be initialized 0x80190194
Any idea about this?
Best regards,
Miguel
m_kroneI found a solution, hopefully this helps you
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EnterpriseResourceManager\Tracked\[guid]
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Enrollments\[some guid which has the enrolment information]
- removed both reg paths above
- ran dsregcmd /leave
- reboot device
- ran AAD connect to provision device back into Azure AD
- device now Hybrid joined again and registration date is todays date and time / MDM set to none
- dsregcmd /status shows information is being pulled down, waiting for MDM URLs to populate
- Info button on settings / user accounts has now disappeared
- Rebooted device again after 10 minutes
- Upon reboot the MDM URLs now populated
- Event logs show device enrolled
- Info button now available and sync status is successful
- Intune policies applying
20 Replies
Although slightly delayed, I am experiencing the identical issue described above. The affected device has been recently reinitialized following removal from its previous domain environment and is currently running Windows 11 Pro, version 24H2. The system appears unable to upgrade to version 25H2 for undetermined reasons. During the Out-of-Box Experience (OOBE) phase, the process consistently fails with the same error previously reported. In the meantime, I have physical access to the device, and will run the commands listed by you soon.
- Is this a device you have access to?
Thijs Lecomte yes, sorry for the late response.
I also rejoined it already but its still not syncing.
Getting an evententry: MDM Session: OMA-DM client stopped with status: (Not found (404).).
m_kroneDid anyone get a resolution for this? I'm having same issue but no joy so far
Getting the same evententry: MDM Session: OMA-DM client stopped with status: (Not found (404).).
