Troubleshooting a crashing sequencer

Today I would like to highlight a blog post by @Packageologist and how it helped me solve a crashing sequencer problem.

In the beginning of december 2015 I was asked to sequence surveillance software for a customer. This software was marked as ‘not able to virtualize’ because, after the installation, the sequencer crashed when the application was launched for streaming optimisation. The sequencer generated the following error message.


When running some tests I discovered that the setup also did an unattended installation of VLC Media Player. Although this was not mentioned during the setup, it would later on be the cause of the problem. Followed by some more testing and research on the internet I came across this article, which helped me in finding a solution for this problem.

After reading the article, I immediately saved the package and extracted the invalid manifest file from the package as described. When I imported the package with Powershell I received the same error as written in the article.


Following the article, I opened the event log and enabled the manifest debug log for the App-V client. After importing the package again, an event was raised in de logging. According to this event, there was a ProgId entry missing. Subsequently I dived into the DeploymentConfig.xml and searched for missing ProgId’s.


I found a total of 17 missing ProgId’s in the DeploymentConfig.xml which where all related to VLC Media Player. As you can see in the screenshot below, the unattended installation of VLC Media Player added some registry keys into the .AAC key but the default value was still set to Windows Media Player 11.


Because VLC Media Player is launched from inside the application and I don’t want it to be the default program, I removed all the ‘shell’ keys after the installation for the following file types.

.ACC .asf .asx .avi
.m1v .m2v .m3u .mov
.mp2 .mp3 .mp4 .mpeg
.mpg .ts .wav .wma

When done I proceeded as normal and was able to launch the application during the streaming phase and save/deploy it properly. As said this article helped me get into the right direction and solve the problem. So check it out when you’re having problems with a crashing sequencer!


Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Disable Windows Defender in Windows 10

Windows Defender helps protect your PC against malware (malicious software) like viruses, spyware, and other potentially unwanted software. In Windows 10, Microsoft has disabled the ability to stop/disable the service through the services management console.

windefservice    windefsequence

When sequencing it’s best to disable this service because Windows defender can interfere during the creation of a package, by accessing files that need to be added to the virtual package, or adding extraneous data to the virtual package.

To disable Windows defender in Windows 10 I use the powershell command below. 

New-ItemProperty -Path “HKLM:\SOFTWARE\Policies\Microsoft\Windows Defender” -Name DisableAntiSpyware -Value 1 -PropertyType DWORD -Force


When you’ve executed the command a reboot is required. After the reboot… happy sequencing :-).



Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn