Hi,
I am trying to repair PDFCreator professional in command prompt but its getting failed with error code 1602. I have ensured that application is closed before starting the repair.
This issue started from the version 6.1.0.
Command used-msiexec.exe /f {EA0260EB-9F54-4DC0-B5B6-D307E9CA1012} /qn
Environment-win11 virtual machine.
Is repair not supported from version 6.1.0.? Or any solution to resolve this issue?
Thanks.
Hi Meta,
Thank you for the details. You are correct that behavior regarding the MSI repair function changed starting with version 6.1.0 due to updates in our installer framework (WixSharp/WiX 4 migration).
The Cause:
The standard MSI repair switch (/f) triggers a specific "Repair" sequence. In version 6.1.0+, certain Custom Actions (specifically those checking the licensing service and printer drivers) fail when run in a strict "Repair" context in silent mode (/qn), resulting in Error 1602 (System Cancelled/User Cancelled).
The Solution:
Instead of using the /f (repair) flag, you should use the Reinstall method. This achieves the exact same result (fixing missing files/registry keys) but uses the Installation sequence which correctly initializes the Custom Actions.
Please change your command to:
codeCmd
msiexec.exe /i {EA0260EB-9F54-4DC0-B5B6-D307E9CA1012} REINSTALL=ALL REINSTALLMODE=vomus /qn
Breakdown of the command:
/i: Runs the installation sequence (instead of repair).
REINSTALL=ALL: Tells the MSI to reinstall all features.
REINSTALLMODE=vomus: Forces the rewrite of the Local Machine registry, files, and user data, regardless of version (Standard heavy repair).
If this still returns 1602, please run the command with logging enabled so we can see exactly which Custom Action is blocking the process:
msiexec.exe /i {GUID} ... /qn /l*v "C:\Path\To\repairlog.txt"
Best regards,
Vusi Nkosi
PDFCreator Support Team
Hi Vusi ,
Thank you for reply.
I tried the command you have provided but still giving 1602 error code.
PFA for repair logs.
repair.txt (86.7 KB)