Error 1722 usually means the installer script could not finish, often because files are locked or a custom action failed. Stop other installs, close the app, retry from an elevated command prompt if the vendor documents one.
If the product half-exists, forced uninstall can clear the listing so you can patch or reinstall cleanly. Always capture a restore point on production PCs.
Collect the MSI log path Windows shows in the error dialog; attach it when you open a ticket with the software vendor so they can see which custom action failed.
Turn on verbose logging before the second attempt. From an elevated command prompt you can rerun the same MSI with /l*v C:\Temp\product.log (path writable by admins). The tail of that log usually names the custom action DLL or script that returned a non-zero code right before error 1722.
Check the Windows Installer service is running and that no other setup is mid-flight. Concurrent installs are a common reason custom actions fail even though the MSI itself is healthy.
If Add/Remove Programs offers “Repair,” run it once before “Uninstall” when the product is half-broken but still partially registered. Repair can re-register COM servers that rollback left dangling; only then use forced uninstall tools if the entry still will not clear.
Look for pending file rename operations: a reboot clears HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations entries that block DLL replacement. Skipping that reboot guarantees the next install attempt hits the same wall.
When you escalate, include OS build, bitness, elevation level, antivirus product, and whether the machine is domain-joined. Those five facts narrow vendor support answers faster than another screenshot of the same dialog.
MSI transforms and MST files matter. If IT deployed the product with a transform, the uninstall path may differ from the default vendor MSI. Attach the original deployment command line (from inventory or SCCM/Intune) so support can reproduce the same transform stack.
Corrupted installer caches under C:\Windows\Installer can surface as 1722 even when the MSI on disk is fine. Let Windows Installer repair its cache via supported vendor steps—do not delete random .msi stubs you do not recognize.
When rollback partially completes, compare the product’s advertised version in registry uninstall keys with the version on the vendor download page. Mismatched builds are a frequent trigger for custom actions that only target one branch.
After a clean removal, seed a quick health check: reinstall the latest redistributables the app lists, reboot, then install fresh. Pair that with Ghost install entries cleanup if Control Panel still disagrees with reality.