cannot launch App-V applications. Application Virtualization Client service cannot start.


If you have a user who cannot launch App-V applications, try the following:

-          Check the Application Virtualization Client service is running.

-          If it will not start, open a CMD prompt with admin privileges, and type: winmgmt /verifyrepository

-          If the result is “Repository inconsistent”, then type: winmgmt /salvagerepository

-          Restart the Windows Management Instrumentation and the Application Virtualization Client services.

-         if that command does not work, try the command winmgmt /resetrepository



This should fix any WMI errors which may cause App-V to stop running.



More info here:- http://blog.wortell.nl/sanderz/troubleshooting-app-v-4-6-client-error-1114-on-rds-servers/

Comments

  1. SunnyMay 29, 2014 at 12:37 AM

    Thank you for the application virtualization help. Your blog link really works! keep on posting!

    ReplyDelete

Post a Comment

Popular posts from this blog

Server Manager will not start, error .NET Framework: "This application requires one of the following versions of the .NET Framework:"

Server Manager will not start on Windows Server 2019 after installing ADConnect. Error ServerManager.exe: This application could not be started. .NET Framework: "This application requires one of the following versions of the .NET Framework:xxxxx Do you want to install .NET framework now?" Of course it's already installed automatically on the server, so if you try and install it again you can't, error "already installed". Try the .NET repair package, can't repair the install. Try dsim.exe to install the package, error "Microsoft .NET Framework is already part of this installation". .NET Runtime version : 4.0.30319.0 - This application could not be started.This application requires one of the following versions of the .NET Framework:  v4.0.30319 The answer is to re-create the registry entries deleted when you installed ADConnect:- [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319] "AspNetEnforceViewStateMac"=dw...
Read more

Start virtualised domain controller in DSRM (Active Directory Restore Mode).

If you have a totally virtualised Active Directory infrastructure in Hyper-V, you can't boot the VM into  Directory Services Restore Mode  using F8. The keypress is not recognised. To get around this, in a elevated command prompt, type: bcdedit /set {globalsettings} advancedoptions true Now when you reboot the DC, it will ask if you want to boot into restore mode, and you can restore A.D. After rebooting, type the command: bcdedit /set {globalsettings} advancedoptions false and it will boot normally again. Now you have to find the restore mode password....
Read more