Win Server 2012 R2 CLR error: 80004005

robttc · Nov 17, 2022

Hi Everyone,

New here and I came across SysNative after still pulling my hair out trying to resolve this issue.
(you guys are awesome and I'm so glad there's a community of people like yourselves! I mean the work you put into this site, WOW! I've seen)

Have a Server 2012 R2 VM trying to migrate roles off of and unable to launch PowerShell, ServerManager or basically anything that is required to actually add or remove roles and decomm.
(Can't even run Windows Installer to remove apps!)

Getting this error below "CLR error 80004005" have done some research and it seems to be related to .Net Framework.
Have run chkdsk to confirm no errors on disk, "sfc /scannow" and "Dism /Online /Cleanup-Image /RestoreHealth"
sfc comes back with errors, dism says no sources found (even when pointing to a clean 2012R2 install.wim)
Even tried an in-place upgrade and this fails.
This server is an AD server AND file server (I didnt build it

)

I discovered SFCFix and ComponentScanner in hopes it would address the corruption. SFCfix is able to list the corrupted files but unable to resolve the corruption.

I have attached the following logs: SFCFix log, ComponentScanner Log, CBS log Folder and DISM log folder.

I would be honoured if someone here on the forums was able to assist.
If there is anything else I'm missing, please let me know :)

PeterJ · Dec 5, 2022

Hello and welcome,

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

Download the file SFCFix.zip and save it on your desktop.
Save any work you have open, and close all programs.
Drag the SFCFix.zip file over the

SFCFix.exe executable and release it.
SFCFix will launch, let it complete.
Once done, a file will appear on your desktop, called SFCFix.txt.
Attach that file to your next reply.

robttc · Dec 13, 2022

Hi Peterj,

Thanks for your reply and for the SFCFix.zip you've provided.
I've applied the zip and rebooted per SFCFix instructions.

Error still appears. I have attached the SFCFix.txt output.

Thank you again for your help :)

PeterJ · Dec 13, 2022

Open an elevated command prompt.
Copy and paste the following commands into it, press enter after each.

Code:

sfc /scannow

Wait for this to finish before you continue

Code:

copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

This will create a file, cbs.txt on your Desktop. Zip this file and attach the zipped cbs.txt to your next post.

robttc · Dec 14, 2022

Hi PeterJ

SFC run and CBS log attached as zip :)

PeterJ · Dec 14, 2022

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

Download the attachment SFCFix.zip and save it on your desktop.
Save any work you have open, and close all programs.
Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
SFCFix will launch, let it complete.
Once done, a file will appear on your desktop, called SFCFix.txt.
Open the file, then copy and paste its content in your next reply.

Step 2:
Open an elevated command prompt.
Copy and paste the following commands into it, press enter after each.

Code:

sfc /scannow

Wait for this to finish before you continue

Code:

copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

This will create a file, cbs.txt on your Desktop. Zip this file and attach the zipped cbs.txt to your next post.

robttc · Mar 6, 2023

Hi PeterJ!

Sorry for the late reply on this one. Other projects came up after the holidays. revisiting this one, hoping to get powershell working again

I ran the latest SFCZip provided; also attached is the CBS log zipped.

Output below and attached:

Thank you again for your help!

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-03-06 23:13:42.790
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .zip script file at C:\Users\username\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\windows\winsxs\amd64_netfx4-penimc_v0400_b03f5f7f11d50a3a_4.0.9696.17230_none_15cda161c739837a\penimc_v0400.dll
Successfully took permissions for file or folder C:\windows\winsxs\amd64_netfx4-clr_dll_b03f5f7f11d50a3a_4.0.9696.17230_none_74c559696dfce929\clr.dll

Successfully copied file C:\Users\username\AppData\Local\niemiro\Archive\amd64_netfx4-penimc_v0400_b03f5f7f11d50a3a_4.0.9696.17230_none_15cda161c739837a\penimc_v0400.dll to C:\windows\winsxs\amd64_netfx4-penimc_v0400_b03f5f7f11d50a3a_4.0.9696.17230_none_15cda161c739837a\penimc_v0400.dll.
WARNING: File C:\windows\winsxs\amd64_netfx4-clr_dll_b03f5f7f11d50a3a_4.0.9696.17230_none_74c559696dfce929\clr.dll was not backed up as that would replace the current backup.
The file \\?\C:\windows\winsxs\amd64_netfx4-clr_dll_b03f5f7f11d50a3a_4.0.9696.17230_none_74c559696dfce929\clr.dll is in use and must be replaced over a reboot.

Successfully pended file for replace over reboot: \\?\C:\windows\winsxs\amd64_netfx4-clr_dll_b03f5f7f11d50a3a_4.0.9696.17230_none_74c559696dfce929\clr.dll

Successfully restored ownership for C:\windows\winsxs\amd64_netfx4-penimc_v0400_b03f5f7f11d50a3a_4.0.9696.17230_none_15cda161c739837a\penimc_v0400.dll
Successfully restored permissions on C:\windows\winsxs\amd64_netfx4-penimc_v0400_b03f5f7f11d50a3a_4.0.9696.17230_none_15cda161c739837a\penimc_v0400.dll
PowerCopy:: directive completed successfully.




Reboot:: directive completed successfully.




PostRebootCorruptionDetection::
No hash verification failures detected.
PostRebootCorruptionDetection:: directive completed successfully.




PostRebootRestorePermissions::
Successfully restored ownership for C:\windows\winsxs\amd64_netfx4-clr_dll_b03f5f7f11d50a3a_4.0.9696.17230_none_74c559696dfce929\clr.dll
Successfully restored permissions on C:\windows\winsxs\amd64_netfx4-clr_dll_b03f5f7f11d50a3a_4.0.9696.17230_none_74c559696dfce929\clr.dll
PostRebootRestorePermissions:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 29 datablocks.
Finish time: 2023-03-06 23:15:54.319
----------------------EOF-----------------------

PeterJ · Mar 6, 2023

Hi,

The cbs.log is clean.
Check the issues you posted in post #1 and report the result.

robttc · Mar 6, 2023

Hi PeterJ,

Thanks for having another look :)

Seems like a bit of progress; getting a new error when opening Server Manager.

Powershell still not opening as well.

Error: CLR20r3
I think its .Net related as well.

PeterJ · Mar 6, 2023

Follow the instructions below to run a scan with the DISM tool and provide a log.

Right-click the Start button and click Command prompt(Administrator).
If you get a popup about UserAccountControl, allow the program to run.
When command prompt opens, copy and paste the following commands into it, press enter after each.
Code:
```
dism /Online /Cleanup-Image /RestoreHealth
```
Wait for this to finish before you continue
Code:
```
copy %windir%\logs\dism\dism.log "%userprofile%\Desktop\dism.txt"
```
This will create a file, dism.txt on your Desktop. Please attach this to your next post. If the file is too big zip it first.

robttc · Mar 7, 2023

Hi PeterJ,

Ran command and rebooted, same error.
Please see attached DISM log :)

PeterJ · Mar 7, 2023

Some problems were fixed.
Please perform the instructions in message #10 again and report the result.

Search

Search

Win Server 2012 R2 CLR error: 80004005

robttc

Contributor

Attachments

PeterJ

Moderator, Windows Update Expert, Security Analyst

robttc

Contributor

Attachments

PeterJ

Moderator, Windows Update Expert, Security Analyst

robttc

Contributor

Attachments

PeterJ

Moderator, Windows Update Expert, Security Analyst

Attachments

robttc

Contributor

Attachments

PeterJ

Moderator, Windows Update Expert, Security Analyst

robttc

Contributor

PeterJ

Moderator, Windows Update Expert, Security Analyst

robttc

Contributor

Attachments

PeterJ

Moderator, Windows Update Expert, Security Analyst