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 /verifyrepositoryreports that the WMI repository is consistent. - Server Manager still closes immediately.
-
ServerManager.logis not being created. -
Get-WindowsFeature Server-Gui-Mgmt-Infradoes 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
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.