Here’s a quick heads up on an issue we ran into recently. When you open a Microsoft Application Virtualization (App-V) app for active upgrade and make a minor change, it is possible that the application will fail to start the first time it is imported on the App-V Management Server. On a client, users will see the error specified below upon the first launch attempt (any other launch will work fine, it only happens for the first launch)
The Application Virtualization Client could not launch. A device attached to the system is not functioning. Error code xxxxxxxx-xxxxxx29-0000001F
They key factor here is the size of the update you are performing. If the size of the package does not change, or it changes too little, you will run into this issue.
You can use the steps to work around this behavior and ensure that the package launches after adding it to the App-V Management Server:
Now you should not see the error.
Good luck sequencing!
Sebastian Gernert | App-V Escalation Engineer
Madelinde Walraven | App-V Support Escalation Engineer
Get the latest System Center news on Facebook and Twitter:
System Center All Up: http://blogs.technet.com/b/systemcenter/ System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/ System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/ System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
Windows Intune: http://blogs.technet.com/b/windowsintune/ WSUS Support Team blog: http://blogs.technet.com/sus/ The AD RMS blog: http://blogs.technet.com/b/rmssupp/
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Hello, this problem I do not resolv this note upper, but add information to registry in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration -- ApplicationSourceRoot value: http://servername_FQDN/content/