App-V 4.6 SP1 issue running a virtualized App-V application that is started from a network location

InformationCurrently some of our customers are reporting that they are having issues running a virtualized App-V application that is started from a network location such as a UNC path or a mapped network drive.  When this occurs they get an application error stating that some DLL could not be found.

This issue only happens on Windows XP and Windows Sever 2003 where the App-V 4.6 SP1 client is installed.  Windows 7 and Windows Server 2008 / R2 are not affected.  Note that App-V 4.6 RTM clients are not affected.

To run into the issue the following conditions must be true:

  • You are running Windows XP and / or Windows Server 2003
  • You have App-V 4.6 SP1 Client installed on the System
  • You run your Application from a Network location.  This means that the executable that is specified in the OSD in the FILENAME tag points to a UNC path or to a mapped network drive. For example:


The App-V Team is currently working on a solution for this issue and an update will be posted when it becomes available.

If you are currently in the process of upgrading to 4.6 SP1 clients on Windows XP and/or Windows Server 2003 and you have applications that are running from a network location, it is recommended that you wait until we publish a fix for this issue, or be sure to test these applications carefully before deployment.

The Microsoft App-V Team

The App-V Team blog:
The WSUS Support Team blog:
The SCMDM Support Team blog:
The ConfigMgr Support Team blog:
The SCOM 2007 Support Team blog:
The SCVMM Team blog:
The MED-V Team blog:
The DPM Team blog:
The OOB Support Team blog:
The Opalis Team blog:
The Service Manager Team blog: http:
The AVIcode Team blog: http:
The System Center Essentials Team blog: http:
The Server App-V Team blog: http:

clip_image001 clip_image002

Comments (12)

  1. Thanks for your patience, a fix coming very soon.  I'll post an update and link on the blog once it goes live.

  2. Just fortunate timing 🙂

  3. Anonymous says:

    This is a client side fix.

  4. DAle Newhart says:

    I am having this issue running the 4.6SP1 client on Windows 7.  THe app was sequenced on a a machine running XPSP3

  5. Keith Holland says:

    Hey J.C.,

    We have seen the issue with the 4.6 SP1 Client installed on XP and when we also try to re-sequence the application with the 4.6 SP1 Sequencer – when we launch the target during the monitoring phase.

    This has put our upgrade project on hold so can you please provide an ETA as to when a fix will be available?



  6. Gabriel Orlandea says:

    I am experiencing same issue with 4.6 SP1 but only on Win XP SP3. Do you guys have any updates on this issue? do you know if there is a non-public fix issued by Microsoft?

  7. Robin Penny says:

    I wonder if this connected to the 4.6 SP1 bug described here:

    This also relates to mapped or UNC drives according to Tim Mangan's last comment, although he says that bug is only an issue with Vista and above.

  8. HeDish says:

    It's gone two months soon, any solution in sight?

  9. HeDish says:

    Thank you, that was quick :>) .

  10. Jaez says:

    where do you apply this fix to your Mgmt. Server , Streaming or Client?


  11. Robin Grotendorst says:

    Sometimes not always ! you can work around this issue and use a executable.exe.local file on the share where the software resides.

Skip to main content