Server 2016 can't run Dot Net 4.0 and no way to repair it. Catch-22
The C: on a Server 2016 that has been running for two years was extended onto an additional SSD from 1TB to 2 TB. This was successful. After reboot, it now reports an error on login as the Server Manager cannot run due to do Dot Net 4 errors or Dot Net 4 being turned off.
"To run this application, you must first install one of the following versions of the .NET Framework:
v4.0.30319
...
Since Server Manager cannot run, we cannot install or repair Dot net 4.0. We also cannot run Powershell to fix it. Command line options do not seem to work either. We would really like to avoid re-installing our server application as it has millions of files on it and many users.
We do have Dot Net 4 folder existing in Windows folders but it does not have IIS installed so using aspnet code to repair does not work.
Running sfc /scannow reports errors. CBS log attached.
The dism command fails with error 14 - out of memory. Log is attached.
SFCFix fails to run with a "Something has gone terribly wrong" error.
This error went away when we deleted the CBS log folder. Now it shows no corruption.
AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2022-05-05 14:58:51.590
----------------------EOF-----------------------
If we re-run SFC/scannow again, it reports the same errors as before. Since CBS.log is there, SFCFix goes back to a "Something has gone terribly wrong" error.
The C: on a Server 2016 that has been running for two years was extended onto an additional SSD from 1TB to 2 TB. This was successful. After reboot, it now reports an error on login as the Server Manager cannot run due to do Dot Net 4 errors or Dot Net 4 being turned off.
"To run this application, you must first install one of the following versions of the .NET Framework:
v4.0.30319
...
Since Server Manager cannot run, we cannot install or repair Dot net 4.0. We also cannot run Powershell to fix it. Command line options do not seem to work either. We would really like to avoid re-installing our server application as it has millions of files on it and many users.
We do have Dot Net 4 folder existing in Windows folders but it does not have IIS installed so using aspnet code to repair does not work.
Running sfc /scannow reports errors. CBS log attached.
The dism command fails with error 14 - out of memory. Log is attached.
SFCFix fails to run with a "Something has gone terribly wrong" error.
This error went away when we deleted the CBS log folder. Now it shows no corruption.
AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2022-05-05 14:58:51.590
----------------------EOF-----------------------
If we re-run SFC/scannow again, it reports the same errors as before. Since CBS.log is there, SFCFix goes back to a "Something has gone terribly wrong" error.