servermanager.exe event id: 1000

%3CLINGO-SUB%20id%3D%22lingo-sub-1160855%22%20slang%3D%22en-US%22%3Eservermanager.exe%20event%20id%3A%201000%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1160855%22%20slang%3D%22en-US%22%3E%3CP%3EI%20recently%20installed%20a%20new%202019%20server%20and%20fully%20updated%20it.%20After%20getting%20it%20fully%20updated%20the%20servermanager.exe%20stopped%20working.%20it%20crashes%20every%20time%20you%20try%20to%20open%20it.%20The%20error%20box%20states%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%222020-02-07_17h58_54.png%22%20style%3D%22width%3A%20399px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F169801i9ECE2C4259D5DF6D%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%222020-02-07_17h58_54.png%22%20alt%3D%222020-02-07_17h58_54.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20decided%20to%20look%20in%20the%20event%20viewer%20and%20found%20the%20following%20corresponding%20event%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%222020-02-07_18h00_08.png%22%20style%3D%22width%3A%20765px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F169802i2715644C9D51AD4D%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%222020-02-07_18h00_08.png%22%20alt%3D%222020-02-07_18h00_08.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20tried%20multiple%20potential%20solutions.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3Eusing%20powershell%20to%20reinstall%20.net3%20and%20.net4%3C%2FLI%3E%3CLI%3Eusing%20powershell%20to%20remove%20servermanager.exe%20and%20reinstall%20it%3C%2FLI%3E%3CLI%3E%3CEM%3ERename%20the%20registry%20key%20HKLM%5CSOFTWARE%5CMicrosoft%5CServerManager%5CServicingStorage%5CServerComponentCache%20to%20ServerComponentCache.old%3C%2FEM%3E%3C%2FLI%3E%3CLI%3E%3CEM%3Eusing%20DISM%20%2Fonline%20%2Fcleanup-image%20%2Fcheckhealth%20showed%20nothing%3C%2FEM%3E%3C%2FLI%3E%3CLI%3E%3CEM%3Eusing%20sfc%20%2Fscannow%20showed%20nothing%20%3C%2FEM%3E%3C%2FLI%3E%3C%2FOL%3E%3CP%3EI%20got%20nothing%20else.%20has%20anyone%20else%20seen%20this%20and%20managed%20to%20resolve%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1160855%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EManagement%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPowerShell%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1160998%22%20slang%3D%22en-US%22%3ERe%3A%20servermanager.exe%20event%20id%3A%201000%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1160998%22%20slang%3D%22en-US%22%3E%3CP%3ESome%20other%20things%20to%20try%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ea%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F929135%2Fhow-to-perform-a-clean-boot-in-windows%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eclean%20boot%3C%2FA%3E%3C%2FP%3E%0A%3CP%3Ecreate%20a%20new%20local%20account%20and%20logon%3C%2FP%3E%0A%3CP%3Erepair%20install%20by%20running%20%3CSTRONG%3Esetup.exe%3C%2FSTRONG%3E%20from%20the%20root%20of%20install%20media%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EGiven%20what%20you've%20already%20tried%2C%20my%20suggestions%20here%20are%20likely%20to%20not%20be%20fruitful%20either.%20If%20it%20were%20me%20given%20a%20new%20install%20I'd%20not%20waist%20any%20more%20time%20with%20it%20and%20clean%20install%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1187137%22%20slang%3D%22en-US%22%3ERe%3A%20servermanager.exe%20event%20id%3A%201000%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1187137%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20currently%20running%20with%20the%20theory%20of%20SentinelOne%20causing%20this...%20I%20found%20this%20thread%20today..%20I%20need%20to%20either%20update%20or%20remove%20S1%20to%20test.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20title%3D%22Server%20Manager%20fails%20to%20launch%20on%20Server%202019%22%20href%3D%22https%3A%2F%2Fwww.reddit.com%2Fr%2FWindowsServer%2Fcomments%2Feshsvn%2Fserver_manager_fails_to_launch_on_server_2019%2Fffay09c%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EServer%20Manager%20fails%20to%20launch%20on%20Server%202019%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I recently installed a new 2019 server and fully updated it. After getting it fully updated the servermanager.exe stopped working. it crashes every time you try to open it. The error box states:

 

2020-02-07_17h58_54.png

 

I decided to look in the event viewer and found the following corresponding event:

 

2020-02-07_18h00_08.png

 

I have tried multiple potential solutions.

 

  1. using powershell to reinstall .net3 and .net4
  2. using powershell to remove servermanager.exe and reinstall it
  3. Rename the registry key HKLM\SOFTWARE\Microsoft\ServerManager\ServicingStorage\ServerComponentCache to ServerComponentCache.old
  4. using DISM /online /cleanup-image /checkhealth showed nothing
  5. using sfc /scannow showed nothing

I got nothing else. has anyone else seen this and managed to resolve it?

2 Replies
Highlighted

Some other things to try;

 

a clean boot

create a new local account and logon

repair install by running setup.exe from the root of install media

 

Given what you've already tried, my suggestions here are likely to not be fruitful either. If it were me given a new install I'd not waist any more time with it and clean install it.

 

 

 

 

 

Highlighted

I am currently running with the theory of SentinelOne causing this... I found this thread today.. I need to either update or remove S1 to test.

 

Server Manager fails to launch on Server 2019