A cloud-based identity and access management service for securing user authentication and resource access
If the AADConnect installation trace reports an inconsistent or stale Azure AD Sync Engine product code, remove that specific MSI registration before running setup again; reinstalling without cleaning the installer state will repeat the “Service ADSync was not found” error.^1^
Confirm the stale product registration
- Start the Microsoft Entra Connect setup wizard and leave its first page open.
- Open:
%ProgramData%\AADConnect\ - Open the newest installation trace log.
- Search for:
-
GetInstalledPackagesByUpgradeCode -
stale product code -
needs to be upgraded -
Service ADSync was not found
-
- Record the ProductCode GUID associated with Azure AD Sync Engine.
This distinguishes an incomplete uninstall from a service that is installed but merely unable to start. Because ADSync is absent, changing its service account or permissions in services.msc is not applicable yet.
Remove only the product code identified in the log
Do not delete Entra Connect registry keys manually. Microsoft states that direct registry editing is unsupported and can cause serious problems.^1^
- Open Command Prompt as administrator.
- Substitute the exact ProductCode GUID found in the trace:
SET productcode={YOUR-PRODUCT-CODE-GUID}
SET /a counter=1
MSIEXEC /x %productcode% /qn /norestart /l*v "%ProgramData%\AADConnect\AADConnect_Uninstall-ForcedUninstall_%counter%.log" EXECUTE_UNINSTALL="1"
- Run the
MSIEXECcommand a second time, as specified in Microsoft’s procedure. If corrupted installer data generates prompts, select Yes. - Restart the server.
- Start Microsoft Entra Connect setup again and inspect the newest
%ProgramData%\AADConnect\trace. - Confirm that the inconsistent or stale ProductCode is no longer detected, then complete the installation. The ADSync service should be created during installation.
If the product code cannot be removed
Run Microsoft’s Program Install and Uninstall troubleshooter, selecting the Entra/Azure AD synchronization component when prompted. It can repair corrupted registry keys and incomplete uninstall information.^2^
Afterward:
- Restart the server.
- Start the Connect wizard.
- Recheck the newest trace for the stale ProductCode.
- Continue setup only after that entry is gone.
If it remains, Microsoft’s documented final fallback is reinstalling the Windows operating system because the Windows Installer database may be unrecoverable.^1^ An OS reinstall can remove applications, configuration, and data. Before considering it, escalate to Microsoft Support or an experienced Entra administrator, create and verify a full backup, document the existing Entra Connect configuration, and test the recovery procedure.
If the trace does not show a stale product code
The exact cause is not established by the missing-service message alone. Review the latest AADConnect installation trace and Event Viewer → Windows Logs → Application/System for the first installation failure. Event Viewer is the documented next diagnostic location for Entra Connect service failures.^3^
Do not apply LocalDB cleanup, SQL database deletion, service-account changes, or Group Policy changes unless those logs identify the corresponding failure.
References