Desktop to UWP Bridge: Desktop App Converter
The Desktop App Converter (DAC) is a tool that enables you to bring your existing desktop apps written for .NET 4.6.1 or Win32 to the Universal Windows Platform (UWP). You can run your desktop installers through the converter in an unattended (silent) mode and obtain a Windows app package that you can install by using the Add-AppxPackage PowerShell cmdlet on your development machine.
The Desktop App Converter is available now in the Windows Store.
The converter runs the desktop installer in an isolated Windows environment 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. The converter outputs a Windows app package with package identity and the ability to call a vast range of WinRT APIs.
The latest version of the DAC is v188.8.131.52. New in this update:
- No-Installer conversion: If your app is installed using xcopy or you’re familiar with the changes your app’s installer makes to the system, you can run conversion without an installer by setting the -Installer parameter to the root directory of your app files.
- App package validation: Use the new
-Verifyflag to validate your converted app package against Desktop Bridge and Store 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)
Set up the Desktop App Converter
(These steps are not required for no-installer conversion)
The Desktop App Converter relies on the latest Windows 10 features. Please ensure that you're on the Windows 10 Anniversary Update (14393.0) or later builds.
- Download the DesktopAppConverter from the Windows Store and the base image .wim file that matches your build.
- Run the DesktopAppConverter as admin. You can do this from the start menu by by right-clicking the tile and selecting Run as administrator from under More, or from the taskbar by right-clicking the tile, right clicking a second time on the app name that pops up, and then selecting Run as administrator.
- From the app console window, run
- Set up the converter by running
DesktopAppConverter.exe -Setup -BaseImage .\BaseImage-1XXXX.wim -Verbosefrom the app console window.
- If running the previous command prompts you to reboot, please restart your machine.
Run the Desktop App Converter
- Store download: Use
DesktopAppConverter.exeto run the converter.
DesktopAppConverter.exe -Installer <String> [-InstallerArguments <String>] [-InstallerValidExitCodes <Int32>] -Destination <String> -PackageName <String> -Publisher <String> -Version <Version> [-ExpandedBaseImage <String>] [-AppExecutable <String>] [-AppFileTypes <String>] [-AppId <String>] [-AppDisplayName <String>] [-AppDescription <String>] [-PackageDisplayName <String>] [-PackagePublisherDisplayName <String>] [-MakeAppx] [-LogFile <String>] [<CommonParameters>]
The following examples shows how to convert a desktop app named MyApp by MyPublisher to a Windows app package.
With No-installer conversion, the
-Installer parameter points to the root directory of your app files and the
-AppExecutable parameter is required.
DesktopAppConverter.exe -Installer C:\Installer\MyApp\ -AppExecutable MyApp.exe -Destination C:\Output\MyApp -PackageName "MyApp" -Publisher "CN=MyPublisher" -Version 0.0.0.1 -MakeAppx -Sign -Verbose
Installer based conversion
With installer based conversion,
-Installer points to your app's setup installer.
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
Deploy your converted Windows app package
Use the Add-AppxPackage cmdlet in PowerShell to deploy a signed app package (.appx) to a user account.
You can use the
-Sign flag in the Desktop App Converter (v0.1.24) to auto-sign your converted app. Alternatively, refer to Sign your converted desktop app to learn how to self-sign AppX packages.
You can also utilize the
-Register parameter of the Add-AppXPackage PowerShell cmdlet to install from a
folder of unpackaged files during the development process.
For more information on deploying and debugging your converted app, see Deploy and debug your converted UWP app.
Sign your Windows app package
The Add-AppxPackage cmdlet requires that the Windows app package (.appx) being deployed must be signed. Use
-Sign flag as part of the converter command line or SignTool.exe, which ships in the Microsoft Windows 10 SDK, to sign the Windows app package.
For additional details on how to sign your Windows app package, see Sign your converted desktop app.
Note: If you try to sign a package using the autogenerated certificate, you'll need to use the default password "123456".
Modify VFS folder and registry hive (Optional)
The desktop App Converter takes a very conservative approach to filtering out files and system noise in the container. This is not required, but after conversion you can:
- Review the VFS folder and delete any files that are not needed by your installer.
- Review the contents of Reg.dat and delete any keys that are not installed/needed by the app.
If you make any changes to your converted app (including the ones above), you don't need to run the Converter again; you can manually repackage your app using the MakeAppx tool and the appxmanifest.xml file the DAC generates for your app. For help, see Manually convert your app to UWP using the Desktop Bridge.
- The Windows 10 build on the host machine must match the base image that you obtained as part of the Desktop App Converter download.
- Ensure that the desktop installer is in an independent directory, because the converter copies all of the directory's content to the isolated Windows environment.
- Currently, the Desktop App Converter supports running the conversion process on a 64-bit operating system only. You can deploy the converted Windows app packages to a 64-bit (x64) OS only.
- Desktop App Converter requires the desktop installer to run under unattended mode. Ensure that you pass the silent flag for your installer to the converter by using the -InstallerArguments parameter.
- Publishing public SxS 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. Inbox assemblies, like ComCtl, are shipped with the OS, so taking a dependency on them is safe. The SxS Fusion assemblies are registered in the following locations:
- File System: %windir%\SideBySide
We are currently investigating the following errors occuring on some OS builds:
If you're running into either of these errors, please ensure you are using a valid base image from the download center. If you’re using a valid .wim, please send us your logs at email@example.com to help us investigate.
If you receive a Windows Insider flight on a developer machine that previously had the Desktop App Converter installed, you may receive the error
New-ContainerNetwork: The object already existswhen you setup the new base image. As a workaround, run the command
Netsh int ipv4 resetfrom an elevated command prompt, then reboot your machine.
A .NET app compiled with "AnyCPU" build option will fail to install if the main executable or any of the dependencies were placed under "Program Files" or "Windows\System32". As a workaround, please use your architecture specific desktop installer (32 bit or 64 bit) to successfully generate a Windows app package.
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.
Desktop App Converter usage
Here's a list of parameters to the Desktop App Converter. You can also view this list by running:
Get-Help DesktopAppConverter.exe -detailed
||Runs DesktopAppConverter in setup mode. Setup mode supports expanding a provided base image.|
||Full path to an unexpanded base image. This parameter is required if -Setup is specified.|
||Specifies a log file. If omitted, a log file temporary location will be created.|
||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.|
||Don't prompt for reboot when running setup (reboot is required to enable the container feature).|
||The full path to your application's root folder for the installed files if it were installed (e.g., "C:\Program Files (x86)\MyApp").|
||The desired destination for the converter's appx output - DesktopAppConverter can create this location if it doesn't already exist.|
||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.|
||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
NOTE: The unattended/silent flags and log arguments will vary between installer technologies.
An example usage for this parameter:
||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.|
Windows app package identity parameters
||The name of your Universal Windows App package|
||The publisher of your Universal Windows App package|
||The version number for your Universal Windows App package|
Optional Windows app package manifest parameters
||The name of your application's main executable (eg "MyApp.exe"). This parameter is required for a no-installer conversion.|
||A comma-separated list of file types which the application will be associated with (eg. ".txt, .doc", without the quotes).|
||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.|
||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.|
||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.|
||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.|
||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.|
Other conversion parameters
||Full path to an already expanded base image.|
||A switch that, when present, tells this script to call MakeAppx on the output.|
||Specifies a log file. If omitted, a log file temporary location will be created.|
||Tells this script to sign the output Windows app package. This switch should be present alongside the switch
||This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable, and OutVariable. For more info, see about_CommonParameters.|
||A switch that, when present, tells the DAC to validate the converted 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
||Runs cleanup for the DesktopAppConverter artifacts. There are 3 valid options for the Cleanup mode.|
||Deletes all expanded base images, removes any temporary converter files, removes the container network, and disables the optional Windows feature, Containers.|
||Removes all the temporary converter files.|
||Deletes all the expanded base images installed on your host machine.|
The Desktop App Converter now supports creation of both x86 and x64 app packages that you can install and run on x86 and amd64 machines. Note the Desktop App Converter still needs to run on an AMD64 machine to perform a successful conversion.
||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.|
Running the PEHeaderCertFixTool
During the conversion process, the DesktopAppConverter automatically runs the PEHeaderCertFixTool in order 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. Example usage:
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
The Desktop App Converter does not support Unicode; thus, no Chinese characters or non-ASCII characters can be used with the tool.