Close Menu
    Facebook X (Twitter) Instagram
    Sunday, October 12
    X (Twitter) LinkedIn Reddit RSS
    All about Endpoint Management
    • Home
    All about Endpoint Management
    Home»App-V»Failed to open WMI Namespace virtualapp.log

    Failed to open WMI Namespace virtualapp.log

    Eswar KonetiBy Eswar KonetiJuly 20, 6:03 pm2 Mins Read App-V 2,362 Views
    Share
    Facebook Twitter LinkedIn Reddit

    Sometimes pushing app-v Application doesn't work on some machines and when looked at virtualapp.log file,you will see something like below.

    “Failed to open the WMI namespace [root\microsoft\appvirt\client]” from C:\Windows\SysWOW64\CCM\Logs\VirtualApp.log.

    What does the above Error says ? The WMI namespace was not created during the install of the App-V Client.

    You can verify it by typing wmimgmt.msc from your RUN command .

    image

    If You want to connect to Remote Computer ,try below.

    image

    Right click on the WMI Control and select properties, click on the Security Tab:

    image

    Go to Root—>Microsoft ,you see appvirt is missing from it.

    image

    So ? How do you get it back ? Reinstalling the app-V client by uninstalling it and install again ?

    I do the other way ,here it is:

    Identify a Machine which is base build( not a machine setup for a user) and go to wmimgmt properties as we did above ,and select properties>go to the Backup/Restore Tab.

    image

    Click on “Back Up Now…” It asks you where to store and the file extension will be .rec

    You can either take this file into Pen Drive or via network share onto failed machine.

    Now Go back with your failed machine and click on backup/Restore to restore the backup file.

    Now Open the WMI snap in again and confirm you can see “APPVIRT” under root-->Microsoft

    Restart the computer once to take the changes effect (Ensure you restore the backup using admin account).

    Hope it helps!

    Failed to open WMI Namespace for Virtual App SCCM Virtual app error virtapp.log Virtapp missing wmi
    Share. Twitter LinkedIn Email Facebook Reddit

    Related Posts

    How to detect the source of registry key modifications on windows devices – Intune

    November 21, 8:49 pm

    Identifying devices managed by Intune but not reporting to WUfB using KQL

    November 09, 10:28 am

    Application Deployment with Hybrid Joined Requirement Rules in Intune

    October 06, 8:59 pm

    Leave a ReplyCancel reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Sign Up

    Get email notifications for new posts.

    Author

    I’m Eswar Koneti ,a tech enthusiast, security advocate, and your guide to Microsoft Intune and Modern Device Management. My goal? To turn complex tech into actionable insights for a streamlined management experience. Let’s navigate this journey together!

    Support

    Awards

    Archives

    © Copyright 2009-2025 Eswar Koneti, All rights reserved.

    Type above and press Enter to search. Press Esc to cancel.