You can use the Desktop App Converter (DAC) to bring your desktop apps to the Universal Windows Platform (UWP). This includes Win32 apps and apps that you've created by using .NET 4.6.1.
While the term "Converter" appears in the name of this tool, it doesn't actually convert your app. Your app remains unchanged. However, this tool generates a Windows app package with a package identity and the ability to call a vast range of WinRT APIs.
You can install that package by using the Add-AppxPackage PowerShell cmdlet on your development machine.
The converter runs the desktop installer in an isolated Windows environment by using a clean base image provided as part of the converter download. It captures any registry and file system I/O made by the desktop installer and packages it as part of the output.
Checkout this series of short videos published by the Microsoft Virtual Academy. These videos walk you through some common ways to use the Desktop App Converter.
The DAC does more than just generate a package for you
Here's a few extra things it can do for you.
Windows 10 Creators Update
Automatically register your preview handlers, thumbnail handlers, property handlers, firewall rules, URL flags.
Automatically register file type mappings that enable users to group files by using the Kind column in File Explorer.
Register your public COM servers.
Windows 10 Anniversary Update or later
Automatically sign your package so that you can test your app.
Validate your app against Desktop Bridge and Windows Store requirements.
To find a complete list of options, see the Parameters section of this guide.
If you're ready to create your package, let's start.
First, consider how you'll distribute your app
If you plan to publish your app to the Windows Store, start by filling out this form. Microsoft will contact you to start the onboarding process. As part of this process, you'll reserve a name in the store, and obtain information that you'll need to package your app.
Make sure that your system can run the converter
Make sure that your system meets the following requirements:
- Windows 10 Anniversary Update (10.0.14393.0 and later) Pro or Enterprise edition.
- 64 bit (x64) processor
- Hardware-assisted virtualization
- Second Level Address Translation (SLAT)
- Windows Software Development Kit (SDK) for Windows 10.
Start the Desktop App Converter
Download and install the Desktop App Converter.
Run the Desktop App Converter as an administrator.
A console window appears. You'll use that console window to run commands.
Set a few things up (apps with installers only)
You can skip ahead to the next section if your app doesn't have an installer.
Identify the version number of your operating system.
You can do that by opening the System Information app on your computer and then finding the version number of your operating system.
Download the appropriate Desktop app Converter base image.
Make sure that the version number that appears in the name of the file matches the version number of your Windows build.
Place the downloaded file anywhere on your computer where you'll be able to find it later.
In the console window that appeared when you started the Desktop App Converter, run this command:
- Set up the converter by running this command:
DesktopAppConverter.exe -Setup -BaseImage .\BaseImage-1XXXX.wim -Verbose.
Restart your computer if you're prompted to do so.
Status messages appear in the console window as the converter expands the base image. If you don't see any status messages, press any key. This can cause the contents of the console window to refresh.
When the base image is fully expanded, move to the next section.
Package an app
To Package your app, run the
DesktopAppConverter.exe command in the console window that opened when you started the Desktop App Converter.
You'll specify the package name, publisher and version number of the app by using parameters.
If you've reserved your app name in the Windows store, you can obtain the package and publisher names by using the Windows Dev Center dashboard. If you plan to sideload your app onto other systems, you can provide your own names for these as long as the publisher name that you choose matches the name on the certificate you use to sign your app.
A quick look at command parameters
Here are the required parameters.
DesktopAppConverter.exe -Installer <String> -Destination <String> -PackageName <String> -Publisher <String> -Version <Version>
You can read about each one here.
Here's a few common ways to package your app.
- Package an app that has an installer (.msi) file
- Package an app that has a setup executable file](#setup-conversion)
- Package an app that doesn't have an installer
- Package an app, sign the app, and prepare it for store submission
Package an app that has an installer (.msi) file
Point to the installer file by using the
DesktopAppConverter.exe -Installer C:\Installer\MyAppSetup.msi -Destination C:\Output\MyApp -PackageName "MyApp" -Publisher "CN=MyPublisher" -Version 0.0.0.1
Make sure that your installer is located in an independent folder and that only files related to that installer are in the same folder. The converter copies all of the contents of that folder to the isolated Windows environment.
Package an app that has a setup executable file
Point to the setup executable by using the
DesktopAppConverter.exe -Installer C:\Installer\MyAppSetup.exe -InstallerArguments "/S" -Destination C:\Output\MyApp -PackageName "MyApp" -Publisher "CN=MyPublisher" -Version 0.0.0.1
InstallerArguments parameter is an optional parameter. However, because the Desktop App Converter needs your installer to run in unattended mode, you might have to use it if your app needs silent flags to run silently. The
/S flag is a very common silent flag, but the flag that you use might be different depending on which installer technology you used to create the setup file.
Package an app that doesn't have an installer
In this example, use the
Installer parameter to point to the root folder of your app files.
AppExecutable parameter to point to your apps executable file.
DesktopAppConverter.exe -Installer C:\Installer\MyApp\ -AppExecutable MyApp.exe -Destination C:\Output\MyApp -PackageName "MyApp" -Publisher "CN=MyPublisher" -Version 0.0.0.1
Package an app, sign the app, and run validation checks on the package
This example is similar to first one except it shows how you can sign your app for local testing, and then validate your app against Desktop Bridge and Windows Store requirements.
DesktopAppConverter.exe -Installer C:\Installer\MyAppSetup.exe -InstallerArguments "/S" -Destination C:\Output\MyApp -PackageName "MyApp" -Publisher "CN=MyPublisher" -Version 0.0.0.1 -MakeAppx -Sign -Verbose -Verify
Sign parameter generates a certificate and then signs your app with it. To run your app, you'll have to install that generated certificate. To learn how, see the Run the packaged app section of this guide.
You can validate you app by using the
A quick look at optional parameters
Verify parameters are optional. There are many more optional parameters. Here are some of the more commonly used optional parameters.
[-ExpandedBaseImage <String>] [-AppExecutable <String>] [-AppFileTypes <String>] [-AppId <String>] [-AppDisplayName <String>] [-AppDescription <String>] [-PackageDisplayName <String>] [-PackagePublisherDisplayName <String>] [-MakeAppx] [-LogFile <String>] [<CommonParameters>]
You can read about all of them in the next section.
Here's the complete list of parameters (organized by category) that you can use when you run the Desktop App Converter.
You can also view the entire list by running the
Get-Help command in the app console window.
|-Setup [<SwitchParameter>]||Required||Runs DesktopAppConverter in setup mode. Setup mode supports expanding a provided base image.|
|-BaseImage <String>||Required||Full path to an unexpanded base image. This parameter is required if -Setup is specified.|
|-LogFile <String>||Optional||Specifies a log file. If omitted, a log file temporary location will be created.|
|-NatSubnetPrefix <String>||Optional||Prefix value to be used for the Nat instance. Typically, you would want to change this only if your host machine is attached to the same subnet range as the converter's NetNat. You can query the current converter NetNat config by using the Get-NetNat cmdlet.|
|-NoRestart [<SwitchParameter>]||Required||Don't prompt for reboot when running setup (reboot is required to enable the container feature).|
|-AppInstallPath <String>||Optional||The full path to your application's root folder for the installed files if it were installed (e.g., "C:\Program Files (x86)\MyApp").|
|-Destination <String>||Required||The desired destination for the converter's appx output - DesktopAppConverter can create this location if it doesn't already exist.|
|-Installer <String>||Required||The path to the installer for your application - must be able to run unattended/silently. No-installer conversion, this is the path to the root directory of your app files.|
|-InstallerArguments <String>||Optional||A comma-separated list or string of arguments to force your installer to run unattended/silently. This parameter is optional if your installer is an msi. To get a log from your installer, supply the logging argument for the installer here and use the path <log_folder>, which is a token that the converter replaces with the appropriate path.
NOTE: The unattended/silent flags and log arguments will vary between installer technologies.
An example usage for this parameter: -InstallerArguments "/silent /log <log_folder>\install.log" Another example that doesn't produce a log file may look like:
|-InstallerValidExitCodes <Int32>||Optional||A comma-separated list of exit codes that indicate your installer ran successfully (for example: 0, 1234, 5678). By default this is 0 for non-msi, and 0, 1641, 3010 for msi.|
|Package identity parameters|
|-PackageName <String>||Required||The name of your Universal Windows App package|
|-Publisher <String>||Required||The publisher of your Universal Windows App package|
|-Version <Version>||Required||The version number for your Universal Windows App package|
|Package manifest parameters|
|-AppExecutable <String>||Optional||The name of your application's main executable (eg "MyApp.exe"). This parameter is required for a no-installer conversion.|
|-AppFileTypes <String>||Optional||A comma-separated list of file types which the application will be associated with (eg. ".txt, .doc", without the quotes).|
|-AppId <String>||Optional||Specifies a value to set Application Id to in the Windows app package manifest. If it is not specified, it will be set to the value passed in for PackageName.|
|-AppDisplayName <String>||Optional||Specifies a value to set Application Display Name to in the Windows app package manifest. If it is not specified, it will be set to the value passed in for PackageName.|
|-AppDescription <String>||Optional||Specifies a value to set Application Description to in the Windows app package manifest. If it is not specified, it will be set to the value passed in for PackageName.|
|-PackageDisplayName <String>||Optional||Specifies a value to set Package Display Name to in the Windows app package manifest. If it is not specified, it will be set to the value passed in for PackageName.|
|-PackagePublisherDisplayName <String>||Optional||Specifies a value to set Package Publisher Display Name to in the Windows app package manifest. If it is not specified, it will be set to the value passed in for Publisher.|
|-Cleanup [<Option>]||Required||Runs cleanup for the DesktopAppConverter artifacts. There are 3 valid options for the Cleanup mode.|
|-Cleanup All||Deletes all expanded base images, removes any temporary converter files, removes the container network, and disables the optional Windows feature, Containers.|
|-Cleanup WorkDirectory||Required||Removes all the temporary converter files.|
|-Cleanup ExpandedImage||Required||Deletes all the expanded base images installed on your host machine.|
|Package architecture parameters|
|-PackageArch <String>||Required||Generates a package with the specified architecture. Valid options are 'x86' or 'x64'; for example, -PackageArch x86. This parameter is optional. If unspecified, the DesktopAppConverter will try to auto-detect package architecture. If auto-detection fails, it will default to x64 package.|
|-ExpandedBaseImage <String>||Optional||Full path to an already expanded base image.|
|-MakeAppx [<SwitchParameter>]||Optional||A switch that, when present, tells this script to call MakeAppx on the output.|
|-LogFile <String>||Optional||Specifies a log file. If omitted, a log file temporary location will be created.|
|-Sign [<SwitchParameter>]||Optional||Tells this script to sign the output Windows app package by using a generated certificate for testing purposes. This switch should be present alongside the switch
|<Common parameters>||Required||This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more info, see about_CommonParameters.|
|-Verify [<SwitchParameter>]||Optional||A switch that, when present, tells the DAC to validate the app package against Desktop Bridge and Windows Store requirements. The result is a validation report "VerifyReport.xml", which is best visualized in a browser. This switch should be present alongside the switch
|-PublishComRegistrations||Optional||Scans all public COM registrations made by your installer and publishes the valid ones in your manifest. Use this flag only if you want to make these registrations available to other applications. You don't need to use this flag if these registrations will be used only by your application.
Review this article to make sure that your COM registrations behave as you expect after you package your app.
Run the packaged app
There's two ways to run your app.
One way is to open a PowerShell command prompt, and then type this command:
Add-AppxPackage –Register AppxManifest.xml. It's probably the easiest way to run your app because you don't have to sign it.
Another way is to sign your app with a certificate. If you use the
sign parameter, the Desktop App Converter will generate one for you, and then sign your app with it. That file is named auto-generated.cer, and you can find it in the root folder of your packaged app.
Follow these steps to install the generated certificate, and then run your app.
Double-click the auto-generated.cer file to install the certificate.
If you're prompted for a password, use the default password "123456".
In the Certificate dialog box, choose the Install Certificate button.
In the Certificate Import Wizard, install the certificate onto the Local Machine, and place the certificate into the Trusted People certificate store.
In root folder of your packaged app, double click the Windows app package file.
Install the app, by choosing the Install button.
Modify the packaged app
You'll likely make changes to your packaged app to address bugs, add visual assets, or enhance your app with modern experiences such as live tiles.
After you make your changes, you don't need to run the converter again. You can repackage your app by using the MakeAppx tool and the appxmanifest.xml file the DAC generates for your app. See Generate a Windows app package.
If you make changes to registry settings that your installer makes, you will have to run the Desktop App Converter again to pick up those changes.
|Modify and repackage output||Demo: Modify and repackage output|
The following two sections describe a couple of optional fix-ups to the packaged app that you might consider.
Delete unnecessary files and registry keys
The desktop App Converter takes a very conservative approach to filtering out files and system noise in the container.
If you want, you can review the VFS folder and delete any files that your installer doesn't need. You can also review the contents of Reg.dat and delete any keys that are not installed/needed by the app.
Fix corrupted PE headers
During the conversion process, the DesktopAppConverter automatically runs the PEHeaderCertFixTool to fixup any corrupted PE headers. However, you can also run the PEHeaderCertFixTool on a UWP Windows app package, loose files, or a specific binary. Here's an example.
PEHeaderCertFixTool.exe <binary file>|<.appx package>|<folder> [/c] [/v] /c -- check for corrupted certificate but do not fix (optional) /v -- verbose (optional) example1: PEHeaderCertFixTool app.exe example2: PEHeaderCertFixTool c:\package.appx /c example3: PEHeaderCertFixTool c:\myapp /c /v
Known issues and disclosures
Known issues and workarounds
Here's some known issues and some things you can try to resolve them.
E_CREATING_ISOLATED_ENV_FAILED an E_STARTING_ISOLATED_ENV_FAILED errors
If you receive either of these errors, make sure that you're using a valid base image from the download center.
If you’re using a valid base image, try using
-Cleanup All in your command.
If that does not work, please send us your logs at firstname.lastname@example.org to help us investigate.
New-ContainerNetwork: The object already exists error
You might receive this error when you setup a new base image. This can happen if you have a Windows Insider flight on a developer machine that previously had the Desktop App Converter installed.
To resolve this issue, try running the command
Netsh int ipv4 reset from an elevated command prompt, and then reboot your machine.
Your .NET app is compiled with the "AnyCPU" build option and fails to install
This can happen if the main executable or any of the dependencies were placed anywhere in the Program Files or Windows\System32 folder hierarchy.
To resolve this issue, try using your architecture-specific desktop installer (32 bit or 64 bit) to generate a Windows app package.
Publishing public side-by-side Fusion assemblies won't work
During install, an application can publish public side-by-side Fusion assemblies, accessible to any other process. During process activation context creation, these assemblies are retrieved by a system process named CSRSS.exe. When this is done for a converted process, activation context creation and module loading of these assemblies will fail. The side-by-side Fusion assemblies are registered in the following locations:
- File System: %windir%\SideBySide
This is a known limitation and no workaround currently exists. That said, Inbox assemblies, like ComCtl, are shipped with the OS, so taking a dependency on them is safe.
Error found in XML. The 'Executable' attribute is invalid - The value 'MyApp.EXE' is invalid according to its datatype
This can happen if the executables in your application have a capitalized .EXE extension. Although, the casing of this extension shouldn't affect whether your app runs, this can cause the DAC to generate this error.
To resolve this issue, try specifying the -AppExecutable flag when you package, and use the lower case ".exe" as the extension of your main executable (For example: MYAPP.exe). Alternately you can change the casing for all executables in your app from lowercase to uppercase (For example: from .EXE to .exe).
Telemetry from Desktop App Converter
Desktop App Converter may collect information about you and your use of the software and send this info to Microsoft. You can learn more about Microsoft's data collection and use in the product documentation and in the Microsoft Privacy Statement. You agree to comply with all applicable provisions of the Microsoft Privacy Statement.
By default, telemetry will be enabled for the Desktop App Converter. Add the following registry key to configure telemetry to a desired setting:
- Add or edit the DisableTelemetry value by using a DWORD set to 1.
- To enable telemetry, remove the key or set the value to 0.
The Desktop App Converter does not support Unicode; thus, no Chinese characters or non-ASCII characters can be used with the tool.
Run your app / find and fix issues
Distribute your app
Find answers to specific questions
Our team monitors these StackOverflow tags.
Give feedback about this article
Use the comments section below.