hotfixHere’s another good KB article we just published today. This one talks about an issue where you get a 00000003 or 0000000A error when trying to launch a virtualized application from an App-V client:



You receive the following error when trying to launch or stream an application using the App-V client:

The Application Virtualization Client could not Launch <APPLICATION NAME>
The System Cannot Find the File Specified
Error Code: XXXXXX-XXXXXX2A-00000003

You may also see the following error:

Unexpected Error
Error Code: XXXXXX-XXXXXX0A-0000000A


This can easily happen if you use the wrong convention for specifying a UNC path as an HREF for the SFT file in the application’s OSD file.


If you use the traditional format and not the proper HREF format for specifying a UNC path, the App-V client will error out. You will need to specify the FILE:// HREF prefix in front of the UNC path. For example, if the SFT file located in \\server\share\directory\application.sft path, you will need to specify the format as follows:


More Information

Please note: Specifying a UNC path using the traditional format (\\server\sharename\directory) for the ASR (ApplicationSourceRoot) OSR (OSDSourceRoot) and ISR (IconSourceRoot) is required for those three values per the documentation here:


For the most current version of this article please see the following:

2641546: Error Codes XXXXXX2A-00000003 or XXXXXX0A-0000000A when attempting to stream an application from a Microsoft Application Virtualization Management Server

J.C. Hornbeck | System Center Knowledge Engineer

App-V Team blog:
AVIcode Team blog:
ConfigMgr Support Team blog:
DPM Team blog:
MED-V Team blog:
OOB Support Team blog:
Opalis Team blog:
Orchestrator Support Team blog:
OpsMgr Support Team blog:
SCMDM Support Team blog:
SCVMM Team blog:
Server App-V Team blog:
Service Manager Team blog:
System Center Essentials Team blog:
WSUS Support Team blog:

clip_image001 clip_image002