Today I wanted to sequence a new package with the Microsoft Application Virtualization (App-V) Sequencer Tool, but I had no success. I always got the following error when the installation should start:
“Cannot start service AppVMon on computer ‘.’.”
I then went through the event log and found this message:
The AppVMon service failed to start due to the following error:
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
With this error I found the post from Aaron Czechowski on TechNet (Link to Blog), which states, that this is a known error for the ADK 1703, and as solution, you should disable Secure Boot. After disabling Secure Boot, I was able to generate an App-V Package.
I hope MS will update the ADK soon.
11 thoughts on “App-V 1703 – Known issue with App-V Sequencer”
We are facing same problem in 1709 as well. Is this the only solution?
I don’t know, last time I had to use it was within a project.
worked for thanks man
This is still an problem in v1809, and disabling secure boot in the VM settings for my sequencer fixes the issue.
I can confirm that this issue persists in ADK 1903 , disabling secure boot still works for the workaround
Disabling Secure boot worked for me. Thanks a lot.
This is still an problem in v1903, and disabling secure boot in the VM settings for my sequencer fixes the issue.
This is still an problem in v20H2, and disabling secure boot in the VM settings for my sequencer fixes the issue.
Unbelievable that this issue still exists (or is a regression) with 20H2… Really, Microsoft — Really!?
Problem is fixed with ADK versions 10.1.22000.1 (MS clearly defines this one Windows 11 only) and 10.1.21382.1 (ADK Insider Preview – Build Revision 210511-1416).
However, when testing out 10.1.21382.1 on Windows 10 (I have checked version 20H2, 21H1, and even 21H2), and starting the Sequencer on those builds, you will get the error message: “The procedure entry point GetTempPath2W would not be located in the dynamic link library C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\Sequencer\APPVMANIFEST.dll” and after pressing OK, the error message: “The procedure entry point GetTempPath2W would not be located in the dynamic link library C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\Sequencer\Sequencer.exe”
Both above ADK versions of the Appman Sequencer do work with Windows 11 (in my case I used Windows 11 Version Dev (OS Build 22494.1000)) and Secure Boot on.
Issue finally has been fixed for Windows 10 2004 and up.
The fix can be downloaded directly from Microsoft via: https://support.microsoft.com/en-us/topic/kb5012894-update-for-microsoft-application-virtualization-app-v-sequencer-tool-and-microsoft-user-experience-virtualization-ue-v-template-generator-ccc1f1dd-dac9-4dc9-8319-54deae75dba2