App-V Sequencer 21H1 Broken

UPDATED FYI,

It seems that in the latest version of the ADK (21H1) requires an OS build that is newer than 21H1.  It isn’t very clear in the documentation, but, at least for the sequencer, that version of the ADK requires an insider’s build (currently) for Windows 11 (and possibly Windows 10 21H2).  ADKs traditionally run on older OSs, and we saw a similar issue with the 2004 ADK.

If you try installing the 21H1 ADK on 21H1 OS, you will find that the sequencer is hopelessly broken, whether you use the GUI, CMD line sequencer, or AutoSequencer:

  • The cmdlet New-AppVSequencer  in the 20H1 version of the Windows ADK is broken.  One of the cmdlet dlls has a missing dependency when run on the 20H1 OS.  I tried a bunch of the VC Runtimes, but still have the issue. 
 The cmdlet New-AppVSequencerPackage fails with message: ‘A procedure imported by “Microsoft.AppV.Modernizer.ManagedCpp.dll” could not be imported.’
  • The GUI Sequencer produces an error upon launch

"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"

If you run into this, just fall back to the prior version.

 

By Tim Mangan

Tim is a Microsoft MVP, and a Citrix CTP Fellow. He is an expert in App-V and MSIX.