Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Launching a virtual application fails with error code 0x3E500D05-00090001
Article ID: 2783096 - View products that this article applies to.
When a user attempts to launch an application virtualized with Microsoft Application Virtualization (App-V) v5, the application fails with the following error:
The application failed to launch.
This may be due to a network failure.
Error code: 0x3E500D05-00090001
This can occur if the path to the .appv container file is incorrect in the client package. Normally this is seen if the content was moved or renamed.
To resolve this issue, correct the path to the .appv container file is incorrect in the client package.
In the Full Infrastructure model and using the App-V v5 Console UI interface, package path is specified when the package is added. To update the package path, delete the package and then add the package again specifying the correct path.
In the Full Infrastructure model and using the App-V v5 Powershell CmdLets, the package path is specified when the package is imported (Import-AppvServerPackage). To update the package path using Powershell, remove the package (Remove-AppvServerPackage) and then import the package (Import-AppvServerPackage) specifying the correct path.
In the Full Infrastructure model, App-V v5 clients receive the updated package path from the publishing server at the next refresh (or Sync-AppvPublishingServer).
On a standalone App-V v5 client using App-V v5 Powershell CmdLets, the package path can be changed using the Set-AppvClientPackage with the -Path switch. It is also specified via Add-AppvClientPackage.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.