Server Manager Crashes - CPU Utilization goes 100% when trying to add servers to All servers section

Question

Hello All,

Since yesterday we've been facing a weird issue, the server manager on our jumpbox VM keeps closing after pushing CPU utilization to 100%. We have tried clearing server manager cache, running sfc /scannow, DISM, .Net repair, however no luck at all. Even if we add servers in small batches, Issue still exists. The windows is up-to-date, We tried this on 2 different servers as well in our domain but still the same issue persists.

Event Viewer logs:

Event ID : 1000

Faulting application name: ServerManager.exe, version: 10.0.17763.168, time stamp: 0xc452e206

Faulting module name: KERNELBASE.dll, version: 10.0.17763.6292, time stamp: 0xb81358b6

Exception code: 0xe0434352

Fault offset: 0x0000000000041b39

Faulting process id: 0x1504

Faulting application start time: 0x01db8df8ef0364bd

Faulting application path: C:\Windows\system32\ServerManager.exe

Faulting module path: C:\Windows\System32\KERNELBASE.dll

Report Id: 3f2e0a25-d275-482b-b9af-5aebd4d056ad

Faulting package full name:

Faulting package-relative application ID:

---

Application: ServerManager.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.ArgumentException

at Microsoft.Windows.ServerManager.Common.Data.RoleFeatureRoot..ctor(System.Collections.Generic.ICollection`1<Microsoft.Windows.ServerManager.Common.Data.IFeature>)

at Microsoft.Windows.ServerManager.Common.Data.Server.UpdateFeatures(System.Collections.Generic.ICollection1<Microsoft.Windows.ServerManager.Common.Data.IFeature>, System.Collections.Generic.ICollection1<Microsoft.Windows.ServerManager.Common.Data.IFeature> ByRef, System.Collections.Generic.ICollection1<Microsoft.Windows.ServerManager.Common.Data.IFeature> ByRef, System.Collections.Generic.ICollection1<Int32> ByRef)

at Microsoft.Windows.ServerManager.Common.Data.DataAccessLayer.UpdateFeatures(System.String, System.Collections.Generic.ICollection`1<Microsoft.Windows.ServerManager.Common.Data.IFeature>)

at Microsoft.Windows.ServerManager.Common.Refresh.FeatureDataProcessor.OnCompleted(System.Exception)

at Microsoft.Windows.ServerManager.Common.Refresh.DataProcessorService.MethodCompleted(System.String, System.String, System.Exception)

at Microsoft.Windows.ServerManager.Common.Refresh.DataProcessorService.OnMethodCompleted(Microsoft.Windows.ServerManager.Common.Refresh.NodeAccessItem, System.String)

at Microsoft.Windows.ServerManager.Common.Refresh.NodeAccessItem.RaiseOperationCompletedEvent(System.String)

at Microsoft.Windows.ServerManager.Common.Refresh.NodeRefreshItem+<>c__DisplayClass13_0.<InvokeMethod>b__0(System.String, System.String, System.String, System.String)

at Microsoft.Windows.ServerManager.Common.NodeAccess.InvokeMethodOperation.OnCompleted()

at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

at Microsoft.Management.Infrastructure.Internal.Operations.CimAsyncCallbacksReceiverBase.CallUnderOriginalExecutionContext(System.Action)

at Microsoft.Management.Infrastructure.Internal.Operations.CimAsyncCallbacksReceiverBase.CallIntoUserCallback(Microsoft.Management.Infrastructure.Native.OperationCallbackProcessingContext, System.Action, Boolean, Boolean)

at Microsoft.Management.Infrastructure.Internal.Operations.CimAsyncObserverProxyBase`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].OnCompletedInternal(Microsoft.Management.Infrastructure.Native.OperationCallbackProcessingContext)

at Microsoft.Management.Infrastructure.Internal.Operations.CimAsyncCallbacksReceiverBase.InvokeWhenOperationIsSet(System.Action`1<Microsoft.Management.Infrastructure.Internal.Operations.CimOperation>)

at Microsoft.Management.Infrastructure.Internal.Operations.CimAsyncObserverProxyBase`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].ProcessNativeCallback(Microsoft.Management.Infrastructure.Native.OperationCallbackProcessingContext, System.__Canon, Boolean, Microsoft.Management.Infrastructure.Native.MiResult, System.String, Microsoft.Management.Infrastructure.Native.InstanceHandle)

at Microsoft.Management.Infrastructure.Internal.Operations.CimAsyncMethodResultObserverProxy.InstanceResultCallback(Microsoft.Management.Infrastructure.Native.OperationCallbackProcessingContext, Microsoft.Management.Infrastructure.Native.OperationHandle, Microsoft.Management.Infrastructure.Native.InstanceHandle, Boolean, Microsoft.Management.Infrastructure.Native.MiResult, System.String, Microsoft.Management.Infrastructure.Native.InstanceHandle)

at Microsoft.Management.Infrastructure.Native.ExceptionSafeInstanceResultCallback.InvokeUserCallback()

at UserFilteredExceptionHandling.UserFilteredExceptionMethod(System.Action, System.Func2<System.Exception,Boolean>, System.Action1<System.Exception>)

at Microsoft.Management.Infrastructure.Native.ExceptionSafeCallbackBase.InvokeUserCallbackAndCatchInternalErrors()

This issue impacts our ability to access our RDS deployment and be able to publish remote apps and programs. Please assist.