Failed to open the WMI namespace [root\AppV].Error (0x8004100e) - App-V 5.0

Option 1 - Reinstall the App-V Client in the machine to resolve the wmi namespace issue.

Option 2 - If you want to avoid reinstalling the App-V client, then try to reinitialize the wmi namespace. This can be done by using the below commands and running it in an elevated CMD.

mofcomp "C:\Program Files\Microsoft Application Virtualization\Client\AppvClientWmiProvider\Remove.Microsoft.Appv.AppvClientWmi.mof"


mofcomp "C:\Program Files\Microsoft Application Virtualization\Client\AppvClientWmiProvider\Microsoft.Appv.AppvClientWmi.mof"


Option 3 - Alternatively check in wmimgmt.msc and restore appv wmi namespace.The below link is pretty old but should work.

Comments

Post a Comment

Popular posts from this blog

Decrypting how Microsoft Teams new MSI works

Image
Microsoft has released a windows Installer MSI for Microsoft Teams for deployment through SCCM.You can download it here As per Microsoft Statement: "The Teams MSI will place an installer in Program Files. Whenever a user signs into a new Windows User Profile, the installer will be launched and a copy of Teams application will be installed in that user's appdata folder. If a user already has the Teams app installed in the appdata folder, the MSI installer will skip the process for that user." NOTE: Don't change the install location as it will break the process. In this blog, I will explain how this happens by opening MSI using Installshield. 1. To Install Microsoft Teams, it first requires .net 4.5 or later to be installed in the machine. This check happens using Launch condition which also does a system search for .net registry to be present in the machine. 2. The MSI has only one file which is Teams.exe that gets installed to [ProgramFilesFolder]Teams Installer locat...
Read more

Sequencing Google Chrome using App-V 5.1

Image
1)  Launch the Microsoft Application Virtualization Sequencer from Start->Programs 2)  Select the "Standard application" type in the Type of Application to be Virtualized 3)  Select "Perform a custom installation" in the select installer screen Provide the virtual application name as Google Chrome and click next. 4)  Before the application is installed, make sure that the below registy entries are placed to disable the updates. [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Update] "UpdateDefault=dword:00000000 "AutoUpdateCheckPeriodMinutes"=dword:0000000 5)  Start the installation during monitoring phase.Install the package using source "GoogleChromeStandaloneEnterprise.msi" After installation, perform the following steps. - Delete the services : Google Update service (gupdate, gupdatem) using the below command in CMD ; SC DELETE gupdate SC DELETE gupdatem - Remove the shortcut from desktop - Remove the folder Update from Program Files (x8...
Read more

MSIX - The future universal format

MSBuild 2018 has officially announced  the new msix format,  and so now it's free to share information publically to all. Since there are already quite few blogs and video's shared in msbuild,  I will  be sharing those links below which will be quite very useful. MSIX - Inside and Out Accelerating Windows 10 enterprise app deployment through MSIX MSIX - pptx MSIX First Look - Priya Saxena Is MSIX the future for App-V - Tim Mangan A blog by Kevin Kaminski MSIX Intro A closer look at MSIX MSIX But what about App-V? Steps to create MSIX - Pascal Berger To Join MSIX Tech Community click here
Read more