Help others and share!

We are recently deploying an upgrade of Citrix Receiver 4.3. As part of the upgrade, we have to re-run the ‘vSyncRestorer.exe’ provided by Nuance to reinstall the .dll file into the Citrix ICA Client folder.

The problem we encountered during deployment is that a large number of devices would fail with a reboot pending error. From the dgnsetup.log file we would see:

Script Info: 10:39:54: Checking registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce
InstallShield 10:39:54: Invoking script function RebootPending
Script Info: 10:39:54: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce\NatSpeak=’cmd.exe /c rd /s /q C:\_NatSpeak_to_remove’ indicates pending OS reboot.
Script Info: 10:39:54: Checking registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce
Script Info: 10:39:54: Checking 64-bit parts of the registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce
Script Info: 10:39:54: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce\NatSpeak=’cmd.exe /c rd /s /q C:\_NatSpeak_to_remove’ indicates pending OS reboot.
Script Info: 10:39:54: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce\BrandClearStubs=’RUNDLL32 IEDKCS32.DLL,BrandCleanInstallStubs >{24F83562-A5B9-4DD8-808C-3C35FDE27A4A}’ indicates pending OS reboot.
Script Info: 10:39:54: Checking 64-bit parts of the registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce
Script Info: 10:39:54: UI Level: 2
Script Info: 10:39:54: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce\BrandClearStubs=’RUNDLL32 IEDKCS32.DLL,BrandCleanInstallStubs >{24F83562-A5B9-4DD8-808C-3C35FDE27A4A}’ indicates pending OS reboot.
Script Warning: 10:39:54: Reboot is pending
Script Info: 10:39:54: UI Level: 2
Script Info: 10:39:54: Cancelling installation because of pending reboot
Script Warning: 10:39:54: Reboot is pending
Script Info: 10:39:54: RebootPending() return code: -3
Script Info: 10:39:54: Cancelling installation because of pending reboot
Script Info: 10:39:54: RebootPending() return code: -3
InstallShield 10:39:54: CallScriptFunctionFromMsiCA() ends
CustomAction CA_RebootPending returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 10:39:54: CA_RebootPending. Return value 3.
Action ended 10:39:54: INSTALL. Return value 3.
MSI (s) (C4:14) [10:39:54:898]: Product: vSyncRestorer — Installation operation failed.

MSI (s) (C4:14) [10:39:54:898]: Windows Installer installed the product. Product Name: vSyncRestorer. Product Version: 12.51.202.093. Product Language: 1033. Manufacturer: Nuance Communications Inc.. Installation success or error status: 1603.

After weeks of digging and no response from the vendor, I found the solution by extracting the ‘vSyncRestorer.exe’ file using the -a command. Once the MSI was extracted, I used admin studio to look at the MSI properties. Within the MSI settings, Nuance is setting the “SKIP_PENDINGREBOOT_CHECK” flag to 0. This is what causes the MSI to check, and then fail the install due to a pending reboot.

The solution was to run the install like so:

vSyncRestorer.exe /s /v”/qn SKIP_PENDINGREBOOT_CHECK=1″

Help others and share!

One thought on “Nuance Dragon vSyncRestorer Fails Due to Pending Reboot – Resolved”

  1. Well this saved me 400 manual installs this weekend. Thank you! This is exactly what I was facing… well not as clear as it was wrapped in Deploy-application being pushed by SCCM, but this was the fix!!

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.