A cloud-based identity and access management service for securing user authentication and resource access
The ADSync Windows service is created and configured by the Microsoft Entra Connect (Azure AD Connect) synchronization engine MSI during installation. If the service is missing but setup still thinks an old sync engine is present, the Windows Installer database is usually inconsistent and holding on to a stale Azure AD Sync Engine product code.
In this state, the Entra Connect setup tries to run an upgrade instead of a clean install, then fails when it checks the service status and cannot find ADSync:
ServiceControllerProvider: verifying ADSync is in state (Running) … Service ADSync was not found on computer '.'
To get the ADSync service installed again, the inconsistent sync engine entry must be cleaned from Windows Installer so that Entra Connect can perform a fresh installation of the synchronization service.
Use the following approach:
- Confirm the stale Azure AD Sync Engine product code
- Start the Microsoft Entra Connect wizard and wait for the first page.
- Open
%ProgramData%\AADConnect\and open the latest installation trace log. - Search for
GetInstalledPackagesByUpgradeCodeand identify the Azure AD Sync Engine product entry that setup believes is installed.
- Fix Windows Installer issues (if KB3139923 is present)
- Check installed hotfixes via Settings > Windows Update > Update history or with PowerShell:
Get-Hotfix | Select-Object HotFixID, InstalledOn, Description, InstalledBy | Sort-Object –Property InstalledOn –Descending | Out-File –FilePath ".\$env:COMPUTERNAME-HotFixes.txt" - If KB3139923 is installed, uninstall it and restart the server.
- Install KB3072630 and restart again.
- Check installed hotfixes via Settings > Windows Update > Update history or with PowerShell:
- Force‑uninstall the stale Azure AD Sync Engine product code
- From the trace log, copy the problematic product code GUID for Azure AD Sync Engine.
- Open an elevated Command Prompt.
- Set the product code variable (replace with the actual GUID):
SET productcode={<12345678-0000-abcd-0000-0123456789ab>} - Run the forced uninstall (this may show errors because the MSI state is already broken; accept prompts):
SET /a counter+=1 & MSIEXEC /x %productcode% /qn /norestart /l*v "%ProgramData%\AADConnect\AADConnect_Uninstall-ForcedUninstall_%counter%.log" EXECUTE_UNINSTALL="1" - Restart the server.
- Verify that the stale product code is gone
- Start the Entra Connect wizard again and wait for the first page.
- Open
%ProgramData%\AADConnect\and check the latest installation trace log. - Confirm that the inconsistent product code no longer appears.
- If it is gone, proceed through the wizard; the installer should now perform a clean install and create the Microsoft Azure AD Sync (ADSync) service.
- If the product code persists, repair Windows Installer
- Run the Program Install and Uninstall troubleshooter from Microsoft to repair MSI and registry issues.
- Restart the server.
- Start the Entra Connect wizard again and re-check the trace log.
- If the stale product code still appears after using the troubleshooter, the Windows Installer database is considered unrecoverable; the documented guidance is to reinstall the Windows operating system before attempting Entra Connect again.
Once the MSI can run a clean installation without seeing the stale sync engine entry, it will install the synchronization service binaries and register the ADSync Windows service automatically; there is no separate manual service creation step.
References: