One of the problems I faced was with the Windows Software Update Services, the service which "deploys updates" to computers on the network.
I found the "Update Services" service in a disabled state, the Windows Internal Database (WID) SQL Instance was completely missing from the server. As a result the Windows Server Update Services mmc console would simply not launch and crash. Starting the Update Services service also did not help improve the situation due to the missing SQL WID database.
Running a "wsusutil reset" simply failed due to the lack of database!
Fatal Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)