Server Manager Crashing

[rhsiv]

One of our technicians has been working to resolve an issue with the server manager crashing when trying to add roles and features. Currently, this issue is causing us, is we are unable to add BitLocker to the server. However, as you can imagine, this could cause many issues moving forward. I wanted to see if anyone else has seen this issue before. We've not had this error before. Below are the specifics of the server:

Server 2012R2
-Ran SFC /scannow, it took a long time to complete. Some files could not be fixed
-Ran DISM /scanhealth, and no errors found
-Ran SFC again, but still cannot repair some files
-Ran DISM /restorehealth, this took a long time, but repairs were completed successfully
-Ran SFC again, but still cannot repair
-Tried reinstalling .net framework - cannot uninstall due to SM crash, and reinstall with offline installer doesn't do anything

Errors that occur in event viewer when SM crashes:

Event 1000, Application Error
Faulting application name: ServerManager.exe, version: 6.3.9600.17238, time stamp: 0x53d0b3e7
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process id: 0xe28
Faulting application start time: 0x01d88bb918a42551
Faulting application path: C:\Windows\system32\ServerManager.exe
Faulting module path: unknown
Report Id: 5e4168e9-f7ac-11ec-8107-f4f46d0654b6
Faulting package full name:
Faulting package-relative application ID:

Event 1026, .NET Runtime
Application: ServerManager.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 0000000000000000

We're open to any ideas or suggestions. If anyone would like any more information, just let me know.

 

[Sky-Knight]

Server 2012 R2's extended support ends Oct 23.

Systemic problems with the OS mean replacing the platform entirely, it's in sore need of upgrade anyway.

 

[Markverhyden]

Looks like nuke and pave time. And since you're going to spend all that time and effort to rebuild a server, presumably with a Domain, lots of GP, etc, etc you might as well put it into a new box with current version of server that'll be supported for a number of years.

 

[timeshifter]

I agree that it's time to move on, but in the meantime...

Have you tried installing with PowerShell?

Install BitLocker on Windows Server

Learn how to install BitLocker on Windows Server.

docs.microsoft.com

 

[HCHTech]

Also, you could just bite the bullet and open (and pay for) a ticket with Microsoft. Sometimes, that's the only way and the cost is justified.