Replace System.Management with local CIM - #1
Merged
Conversation
ml6719
marked this pull request as ready for review
July 27, 2026 16:23
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
System.Managementimplementation with a localMicrosoft.Management.Infrastructure/CimSessionadapternet8.0-windowsand self-containedwin-x640.6.0-preview.1package and symbols outputWhy
Modern
System.Managementcan loadwminet_utils.dllfrom the machine-installed .NET Framework and fail on older Windows Server installations. The new local CIM path removes that dependency while retaining the Hyper-Vroot\virtualization\v2console operations.Validation
System.ManagementLocalSystemself-contained probes passedSystem.Management.dllnorwminet_utils.dllloadedRelease gate
This remains draft and the NuGet workflow is deliberately blocked until the unchanged physical-host probe passes on Server 2012 R2, 2016, 2019, 2022, Windows 10, and Windows 11. Server 2016 must include the host with the original failure state.