App-V 5.1 sequencer and earlier doesn't work on windows 10 version 1607

When trying to install App-V 5.1 and earlier version of sequencer in windows 10 version 1607, it fails with the below error.

Solution: You would need to download the latest SDK for windows 10 version 1607 which has sequencer along with it. Using this sequencer you can proceed virtualizing apps.

Exploring App-V & Ue-V in Windows 10 Anniversary update 1607

As all would have heard about the inbuilt App-V and Ue-V available with Windows 10 Anniversary update 1607 which has been released on August 2nd 2016.It is available only with the Windows Enterprise and Education editions. They will also be included in-box in Windows Server 2016 Standard and Datacenter. If you are using Windows 10 Professional or earlier and plan to upgrade to the Windows 10 Anniversary release, you will need to deploy the Enterprise edition to use App-V and UE-V on those devices.

I have already blogged about this in my previous post when I tested App-V and Ue-V in windows 10 build 14316 and some common issues found. You can have a look here in the below link.

By default App-V and Ue-V are disabled in the OS. You need to enable it to use them. It can be done by enabling in services,GPO or using Powershell commands.

Open services.msc from run command and enable the App-V client service.

GPO-  go to Computer Configuration > Administrative Templates > System > App-V
Run Enables App-V Client and then select Enabled. Restart the machine.

To know list of available commands for App-V in powershell, follow the below step.

To enable App-V ,Open elevated powershell x86 or x64 and type Enable-Appv.This will enable the App-V client and show the output as successfully enabled.

To know the status of App-V, type in the below command.This will show the status of App-V client enabled or not and whether there is any reboot required.

To test bulk App-V 5.0 or App-V 5.1 packages use the below powershell command.

To disable App-V, type in Disable-AppV. This will require a reboot.

Also when checked for App-V version we can see that it is 5.2.

Tested by installing the .MSI file generated by the sequencer and it seems to fail which also earlier failed in build 14316.

For now removing the Launch condition from the MSI worked. To know more check here.Hope Microsoft will rectify this issue soon.

UPDATE (10/08/2016) - Microsoft has provided a official workaround for this issue. Check here for information.

UPDATE (19/10/2016) - When following the above solution provided by Microsoft, there was still an issue stating that the Msidb.exe could not be located.To resolve this issue kindly look into the below useful links.

To know list of available commands for Ue-V, follow the below step.

Open elevated powershell and type Enable-Uev.This will require a reboot.This can also be enabled via enabling in services.msc.

You can also use GPO to enable UEV.Goto Computer Configuration > Administrative Templates > Windows Components > MicrosoftUser Experience Virtualization.Run Enable UEV. Restart is needed.

To know the status of Ue-V, type in the below command.This will show the status of Ue-V enabled or not and whether any reboot required.

To disable Ue-V, type the below command.

Use WMI to list published virtual packages - App-V 5.0 & 5.1

Recently I read an article from David Falkus as how to use WMI to list App-V applications published to the machine.You can use this method if not able to access Powershell and also this method can help in basic troubleshooting. I experimented this and it seems to be very useful. Below are the steps as how to use WMI to list published applications and connection groups.

1. Open Run and type wbemtest.

2. Select Connect button.

3. Enter root\appv and click connect.

4. Click Enum Instances.

5. Enter AppvClientPackage and click ok. Also you can use AppvClientConnectionGroup to list the published Connection Groups.

6. This will list the packages that are published to the machine.

7. When you double click the package it will list the properties of the package like InUse, PackageID, VersionID etc.

8. This method is similar to that of using Get-AppvClientPackage in Powershell.

Windows 10 Build 14327 - Enabling or Disabling AppV/Uev shows success or failure status

Earlier in my previous blog I have mentioned that Enable-AppV, Disable-AppV, Enable-UeV, Disable-UeV commands in powershell doesn't show any success or failure result.

Recently Microsoft has released its windows 10 build 14327 insider preview release. So had a chance to test this case. when tested it shows the result that the App-V/Ue-V was successfully enabled/disabled. Finally there won't be any confusion whether the service is actually enabled or not.

NOTE: Reboot will be required when enabling/disabling.

Project Centennial - First hands on Converting desktop apps to Universal Windows Platform (UWP)

There was a huge expectation about the Project Centennial also famously known as Project C. I promise it will not disappoint any of you. I was very eager to have my hands on it and experiment it more and so here I am explaining the conversion steps in detail with a test desktop app.

Prior to conversion one should know the advantages of converting desktop apps to UWP. To know more check the below link.

Microsoft has released its pre-release version of Desktop App Converter tool which can be used to convert all the existing desktop apps written for .NET 4.6.1 or Win32 to the Universal Windows Platform (UWP).

Desktop App Converter tool converts a desktop Windows installer such as MSI or EXE to an AppX package that can be deployed to a Windows 10 desktop.


1. Windows 10 Build 10.0.14316.0 or higher(Should be installed physically. Converter will fail in a VM image)
2. Desktop App Converter ( Download - Here )
3. Windows Software Development Kit (SDK) for Windows 10 ( Download Here )

The Desktop App Converter will download two files. BaseImage-14316.wim and the files to a desired location.

You can see that there are two files (DesktopAppConverter.cmd and DesktopAppConverter.ps1) DesktopAppConverter.cmd is a cmd wrapper for DesktopAppConverter.ps1.To know more type DesktopAppConverter.cmd -? You can use either CMD or Powershell file for converting purposes.

Now lets convert a test desktop app. Here I am going to use Notepad++ to convert into UWP.
Open Powershell as admin and set the execution policy to unrestricted or bypass.

Enter the below command in the Powershell.The setup command will make the Converter to expand the given base image(BaseImage-14316.wim). To know more about these parameters have a look at the below article.

"path to DesktopAppConverter.ps1" -Setup -BaseImage "path to BaseImage-14316.wim"

If it asks for reboot,Restart the machine and run the command again.

Also note that if you give the absolute path for the DesktopAppConverter.ps1 it will fail. You would need to give the relative path to make it work properly.

It will take some time to expand the base image, so you would need to wait patiently.
It expands the base image to the below path.

Enter the below command to perform conversion in an elevated Powershell.
"path to DesktopAppConverter.ps1" Installer "C:\test\npp.6.8.2.Installer.exe" -InstallerArguments "/S" -Destination "C:\Output\notepadplusplus"
-PackageName "Notepadplus" -Publisher "CN=Notepadplusplus" -Version -ExpandedBaseImage C:\ProgramData\Microsoft\Windows\Images\BaseImage-14316 -Verbose -LogFile "c:\notepad.log"

Make sure you do not keep any other application in the folder. keep only the application that needs to be converted in the Installer location. In this case only notepad++ installer exe should be kept.

This command will run the notepad++ Installer silently in an isolated environment using a clean base image which we downloaded along with the converter(We have expanded the WIM image earlier). It will capture all the changes like registry and file system I/O made by the notepad++ installer and packages it as part of the output.

You can see the verbose log in the screen as we have used -verbose parameter. Also a log file will be generated in the C:\ drive as we have explicitly mentioned in the above command using -LogFile parameter.

So what happens exactly when running the above script. will see more (Refer the above screenshots while reading the below steps for easy understanding).
  1. The script does a Pre-Requisite check like checking Minimum Windows Version,PowerShell Version etc..
  2. It Validates the given parameters like Installer presence, Output Folder presence (If it is not there it will create the folder)
  3. It will Setup Conversion Environment for Capturing.
  4. It Creates AppX Manifest file. This acts as the Core DNA of the Application. It is the Metadata for the package that contains all the required information including extension points, FTA's, shortcuts and the identity names associated with the package.You can customize this file for any changes to be made after capturing the package.
  5. It Generates Virtual File System (VFS). All the files that are captured will be placed here.Additionally there will be Assets Folder which contains Icons [This is created by the Converter].If you are working on App-V then you can relate these things as both are quite same.
  6. It Generates Virtual Registry System (Registry.dat). It Contains all the registry changes that were made by the Installer.
Output – Below is the image of the output that we get,

Assets folder contains the icons for the package. By default it shows X symbol (I guess this will be rectified in the original release). You would need to change these to original icons. Just extract the icons and replace them here with the same name, so that there will be no changes required to modify the AppXmanifest file further.

If we want to create .AppX Package then we need to follow the below steps.

Use MakeAppX.exe to convert to Appx format (It will be available as a part of Windows SDK)

MakeAppx.exe Pack -d "Path of Directory Containing the VFS, Registry.Dat & AppXManifest.xml"-p "Path to output folder"

This will build the loose files to a single AppX package .

In-order to deploy and test the .appx package using the Add-AppxPackage cmdlet, it requires that the application package (.appx) must be signed. For this we can use SignTool.exe, which comes with the Microsoft Windows 10 SDK.

Once signed (you can use a dummy certificate for this step), you can install it successfully.

Testing :Open elevated powershell and run the below command.

Add-AppxPackage "Path to .AppX File"

This will install the package successfully.


At present the Desktop App Converter supports the conversion process only on a 64-bit OS. You can deploy the converted .appx packages to a 64-bit OS only. Desktop App Converter requires the desktop installer to run under unattended mode.

MVP Tim Mangan has mentioned in his blog that there is a bug in the converter.If you give it a MSI based installer, it ignores the command line parameters that you provide and injects it’s own.To know more check his official blog page.(Interesting read :) )
Also check the review from MVP Rory Monaghan about Project C in his blog below.
Also check the blog post from Simon Binder below.

You can also watch the below video from Microsoft Channel9  to know more about the use of Desktop App Converter tool to convert desktop apps to UWP with demo.

To know more check the below official link from Microsoft.