Server Manager fails to open - WMI repository is consistent after /resetrepository but ServerManager.log not created

ranjeet kumar 0 Reputation points
2026-10-29T09:01:45.9066667+00:00

Hello Microsoft Support,Windows Server - Server Manager is not opening.When I run ServerManager from PowerShell, it closes immediately with no error.What I already tried:Fixed WMI: net start winmgmt - success lodctr /R - Successfully rebuilt performance counter winmgmt /resetrepository - WMI repository has been reset - success winmgmt /verifyrepository - WMI repository is consistentCleared Server Manager cache: Removed C:\Users\Administrator\AppData\Local\Microsoft\Windows\ServerManager Removed C:\ProgramData\Microsoft\Windows\ServerManager\Cache Created new Cache folder Run winmgmt /resyncperfStill same problem: ServerManager still not opening File C:\Users\Administrator\AppData\Local\Temp\ServerManager.log not found / does not exist Get-WindowsFeature Server-Gui-Mgmt-Infra shows no outputI have attached screenshots of WMI reset success and cache folder.Please help:What should I do next? Should I run DISM /Online /Cleanup-Image /RestoreHealth and sfc /scannow?Is it safe to reinstall Server-Gui-Mgmt-Infra on production server?My Server details: Server IP: 192.168.2.5 OS: [Write your OS here - run winver on server, example: Windows Server 2019 Standard]

Windows for business | Windows Server | Devices and deployment | Install Windows updates, features, or roles
0 comments No comments

3 answers

Sort by: Most helpful
  1. Daphne Huynh (WICLOUD CORPORATION) 2,620 Reputation points Microsoft External Staff Moderator
    2026-10-29T09:35:46.33+00:00

    Welcome to Microsoft Q&A!

    Thank you for taking the time to provide the troubleshooting steps you have already completed.

    Based on the symptoms you described, I would not reinstall Server-Gui-Mgmt-Infra at this stage.

    Server Manager relies not only on WMI, but also on the Windows servicing infrastructure and component store to enumerate and manage roles and features.

    In your case:

    • winmgmt /verifyrepository reports that the WMI repository is consistent.
    • Server Manager still closes immediately.
    • ServerManager.log is not being created.
    • Get-WindowsFeature Server-Gui-Mgmt-Infra does not return the expected feature information.

    Since WMI is now reporting a consistent repository but feature enumeration is still not working, the next area I would focus on is the Windows component store and system files, rather than resetting WMI again.

    Microsoft also documents scenarios in which Server Manager cannot enumerate Windows features when there is an underlying issue with Component-Based Servicing data.

    I would like to recommend next step

    Before removing or reinstalling any Server Manager component, please open an elevated Command Prompt and run:

    DISM.exe /Online /Cleanup-Image /RestoreHealth
    

    Allow DISM to complete. If it completes successfully, run:

    sfc /scannow
    

    After both commands have completed, restart the server during an appropriate maintenance window.

    DISM checks and repairs the Windows image and component store. SFC can then verify protected Windows system files and repair corrupted files where possible. Given the symptoms you are experiencing, this is a safer next step than uninstalling and reinstalling a Windows feature before confirming the health of the underlying servicing components.

    I would also avoid performing another WMI repository reset at this point. Rebuilding or resetting the repository should not be used as a routine troubleshooting step, particularly when winmgmt /verifyrepository already reports that the repository is consistent.

    After the restart, open an elevated PowerShell window and run:

    Get-WindowsFeature
    

    Run the command without specifying Server-Gui-Mgmt-Infra first. It should return the available and installed roles and features on the server.

    If the feature list is returned successfully, try opening Server Manager again.

    If DISM or SFC reports corruption that cannot be repaired or Get-WindowsFeature still fails to return the feature inventory after the repair and restart, the issue will require deeper investigation. Relevant information would include the DISM and CBS logs, Application and System event logs, the exact Windows Server version/build, and potentially additional diagnostic data depending on what those logs reveal.

    I understand that you would understandably prefer a definitive fix, especially when dealing with a production server. However, I also want to be transparent about the limitations of troubleshooting this type of issue through Microsoft Q&A.

    Microsoft Q&A is a community troubleshooting forum. I can use the symptoms and information provided to recommend supported troubleshooting steps, but I do not have direct access to the affected server or the ability to perform the type of interactive log, dump, trace, or environment-specific analysis that may be required for a full root-cause investigation.

    In particular, the absence of ServerManager.log does not by itself tell us why the Server Manager process is terminating. Similarly, if Get-WindowsFeature continues to fail after the component store and system files have been repaired, there would not be enough evidence from the current information to safely conclude that reinstalling Server-Gui-Mgmt-Infra, resetting WMI again, or performing another specific repair action is the correct solution.

    For that reason, I would not want to recommend increasingly invasive changes to a production server without first identifying the underlying failure. Doing so could introduce additional changes without addressing the actual cause.

    If DISM, SFC, the restart, and the subsequent Get-WindowsFeature validation do not resolve the issue, the appropriate next step would be to open a Microsoft Support case. Microsoft Support can collect and analyze the required diagnostic data from the affected environment and determine the next action based on the actual failure rather than assumptions made from the limited information available in a forum thread.

    I realize this may not provide the immediate definitive resolution you were hoping for. However, I would rather be transparent about what can be safely determined through the forum than recommend an unsupported or potentially disruptive change to your production server without sufficient diagnostic evidence.

    References:

    Get-WindowsFeature (ServerManager) | Microsoft Learn

    Fix Windows Update corruptions and installation failures - Windows Server | Microsoft Learn

    Error 0x800f0805 when Server Manager and DISM fail to list the available features - Windows Server | Microsoft Learn

    Install-WindowsFeature (ServerManager) | Microsoft Learn

    Uninstall-WindowsFeature (ServerManager) | Microsoft Learn

    Scenario guide: Troubleshoot WMI connectivity and access issues - Windows Server | Microsoft Learn

    I hope this helps clarify the safest next step.

    If you find it useful, please click Accept Answer.

    Thank you for choosing Microsoft Q&A.

    Was this answer helpful?

    0 comments No comments

  2. ranjeet kumar 0 Reputation points
    2026-10-29T09:14:25.76+00:00

    now scaning

    Was this answer helpful?

    0 comments No comments

  3. AI answer

    2026-10-29T09:09:47.3133333+00:00

    Microsoft Hyper-V Server 2019 uses the Server Core management model, so local Server Manager is unavailable by design; manage the host through PowerShell, SConfig, Windows Admin Center, or Hyper-V Manager on another computer instead.^1^

    The build number 17763 is shared by Windows Server 2019 and Hyper-V Server 2019, so the build alone does not distinguish the products.^2^

    Do not reinstall Server-Gui-Mgmt-Infra

    Do not remove or reinstall Server-Gui-Mgmt-Infra on this production host. Hyper-V Server 2019 does not provide the local GUI management stack expected by Server Manager. The command documented for installing that component applies to an Exchange prerequisite scenario, not to converting Hyper-V Server or Server Core into Desktop Experience.^3^

    Windows Server 2019 also does not support converting an installed Core system to Desktop Experience by adding GUI features; changing installation options requires a clean installation.^4^

    The absent ServerManager.log therefore does not establish another WMI failure. Since the repository has already been reset and verified as consistent, further WMI resets are not indicated by the information shown.

    Confirm the installed product

    The reported values conflict: one result says Windows Server 2019 Standard, while the stated installation is Microsoft Hyper-V Server 2019. Run these commands in an elevated PowerShell window:

    Get-ComputerInfo |
        Select-Object WindowsProductName, WindowsInstallationType,
                      WindowsVersion, OsBuildNumber
    
    DISM /Online /Get-CurrentEdition
    
    Get-WindowsFeature Server-Gui-Mgmt-Infra 2>&1 |
        Format-List * -Force
    

    Interpret the result as follows:

    • If the product is Microsoft Hyper-V Server 2019 or the installation type is Server Core, stop trying to launch local Server Manager and use remote management.
    • If it is genuinely Windows Server 2019 Standard with Desktop Experience, Server Manager should be included by default and not installed separately.^5^ In that case, proceed with the repair section below.

    Manage the Hyper-V host remotely

    On the host, open elevated PowerShell and enable remoting:

    Enable-PSRemoting
    

    On an administrative Windows computer:

    1. Install Hyper-V Management Tools from Turn Windows features on or off, or install the corresponding RSAT feature.
    2. Open Hyper-V Manager.
    3. Right-click Hyper-V Manager → Connect to Server.
    4. Select Another computer, then enter the host name or address.

    For a same-domain connection, use the host name or FQDN. Workgroup or cross-domain management can additionally require TrustedHosts/CredSSP configuration; avoid enabling those unless that condition applies.^6^

    PowerShell, Hyper-V Manager, and Windows Admin Center are supported Hyper-V management interfaces.^7^

    DISM and SFC: only for the anomalous feature output

    Running DISM and SFC is appropriate if Get-WindowsFeature itself returns no result or an error, because that can indicate a servicing/component-store problem. These commands are not a way to add local Server Manager to Hyper-V Server.

    Schedule a maintenance window, ensure a current backup, and run:

    DISM /Online /Cleanup-Image /ScanHealth
    DISM /Online /Cleanup-Image /CheckHealth
    DISM /Online /Cleanup-Image /RestoreHealth
    sfc /scannow
    

    Review %windir%\Logs\CBS\CBS.log, then restart if repairs were made. Microsoft’s role-and-feature troubleshooting guidance specifies RestoreHealth followed by SFC /scannow for component-store and system-file repair.^8^

    If RestoreHealth reports that repair files cannot be found, it needs a valid matching repair source; do not proceed with feature removal or an in-place repair until the exact installed product and edition are confirmed.^9^


    References

    1. What is the Server Core installation option in Windows Server?
    2. Guest operating system and application supportability on Hyper-V
    3. Windows component Server-Gui-Mgmt-Infra isn't installed on this computer [ServerGuiMgmtInfraNotInstalled]
    4. Server Core vs Server with Desktop Experience install options
    5. Install and manage Remote Server Administration Tools in Windows (windows-server-2019)
    6. Remotely manage Hyper-V hosts with Hyper-V Manager
    7. Hyper-V features and terminology
    8. Installing Windows features and roles troubleshooting guidance
    9. Repair a Windows Image
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.