Server 2016 can't run Dot Net 4.0 and no way to repair it

HugaBuga

New member
Joined
May 5, 2022
Posts
1
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.
 

Attachments

Rich (BB code):
=================================
Checking System Update Readiness.

(p)    CSI Payload Corrupt            amd64_microsoft-windows-c..termanagementsnapin_31bf3856ad364e35_10.0.14393.4169_none_c0d8369cd0e67b48\Computer Management.lnk
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_10.0.14393.4169_none_11cbd49cfb837123\Resource Monitor.lnk
Repair failed: Missing replacement payload.

Let's focus on the first two immediate errors at hand here. Could you please follow these instructions:

SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Afterwards, please run the following command from an elevated command prompt:

Rich (BB code):
sfc /scannow

Please post the CBS log if it fails.
 

Attachments

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top