This article discusses known issues when using the Microsoft Application Virtualization (App-V) Package Converter to test and convert legacy App-V packages to App-V v5.
Cannot convert a package with the following error: "The package converter detected one or more applications in you package that is targeted for an unsupported operating system. This package cannot be converted unless the target operating system restriction is removed from the osd file"
In the OSD file of the legacy source package, a target OS is specified such as <OS VALUE="Win7"/>. Thus, when using the Package Converter only the Win7 can be chosen as the target OS for the converted package. In case, if any other target operating systems are chosen, the conversion fails with the error above. As a workaround, the TargetOS tag can be removed from the source OSD file before the package conversion.
When trying to convert a legacy package, the following warning is displayed: "The icon folder for this package is missing. This package will still convert successfully. However, there will be no icons associated with the applications”
The source legacy package does not have any icons defined. There are no shortcuts or FTAs configured for this legacy package, so the Package Converter is not able to find any icons. Thus, no icons will be added into the converted package.
Package Converter does not delete the .APPV file created during the failed legacy package conversion. Package Converter does not collect the PE Headers for the converted packages.
This might cause an error when the feature block one of the application from the converted package is launched the very first time while the App-V client is in the disconnected mode. To avoid this error, the converted package can be upgraded with the App-V Sequencer, so the PE Headers are collected for the feature block one. Another option is to fully load the package on the client before the application is launched the first time while being in the disconnected mode.
Empty folders are lost when the legacy package is converted.
When the legacy package is converted, the empty folders inside the package are not added into the new package. This might cause issues with the applications that will need to use these empty folders during the runtime. To avoid this issue, the legacy package can be opened, and a file can be added to all the empty folders before the package is converted.
Some converted applications might fail to run due to the dependency on the drive letter (ex. Q).
The legacy packages that contain applications that have a drive letter (ex. Q) embedded into the binary files might fail to run as they cannot be tokenized by the Package Converter. In the case when the application has a hard requirement on a drive letter, the package manifest can be modified to define the dependency on the drive letter. After this change, the application in the package should run after the package conversion.