The installation when NOT packaging, goes as follows on both XP or Windows 7:

1)      Install main application

a.       Upon completion of the installation, it prompts for a reboot

2)      Reboot

3)      Run a Hot Fix utility that is created on c:\Programs Files\.... as a result of the previous installation

I have successfully packaged this application for Windows XP using Sequencer version 4.5 as noted below:

When the main application installation completes and I am prompted to reboot I would:

1)       select: No I will reboot later

2)      Stop monitoring

a.       It would indicate it was processing the reboot tasks

3)      Begin Monitoring

4)      Launch the Hot Fix utility

5)      Continue through the packaging and deployment tasks

When attempting to package on Windows 7 64bit using Sequencer I am not sure how to properly deal with the installation’s reboot request:

I have tried:

1)      Select: No I will reboot later

2)      Launch the hot fix utility

a.       I receive an error from the Hot Fix install utility that it can’t load a DLL and fails.

I also tried:

1)      Select: Yes to the reboot request

2)      The Sequencer intercepts and prevents the reboot

3)      Launch the hot fix utility

a.       I receive an error from the Hot Fix install utility that it can’t load a DLL and fails.



So if I install my main application on Windows 7 64bit without running the sequencer, and allow a real reboot, I am able to launch the Hot Fix utility and successfully complete the installation.


If I run it with the 4.6 Sequencer, I don’t know how to get past the reboot request correctly so that all of the install files are “in order” so that I can successfully run the Hot Fix utility without getting the DLL error below:


This error appears to be generated from my Hot Fix utility not from AppV:


Aspect Hit Fix Utility


Warning:  Exception caught in Main(). Exception:

System.DllNoFoundException: Unable to load DLL

‘WfBrandingAPI.dll’: The specified module could not be found/

(Exception from HRESULT ; 0x8007007E)



Duration, UInt32 behavior, String companyName, String

productName, String productVers, String componentName, String



Aspect.UnifiedIP.Install.AspectHotfixUtility .AspectHotfixUtilityPro

Gram.Main(String[] args in


HotFixUtility\AspectHotFixUtilityProgram.cs:line 63


I am reluctant to call the software vendor for support since if I install the application without the AppV sequencer and allow the reboot before running the Hot Fix utility, it will run and install successfully.


Any suggestions on how to handle the reboot request while packaging so that the Hot Fix will run?


0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



I run with a two-step strategy on these applications: First create a msi package as most repackagers are not so picky on reboots. Then test the msi to see if the bugger works. 


If the msi is OK I create the AppV from there.

Answered 12/17/2013 by: EVEEN
Green Belt

  • Have you tried to sequence this on a 32bit Win7 machine?

    +1 Eveen comments, I would try to create a MSI package then try to sequence that.
Please log in to comment