Windows OS Hub
  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange

 Windows OS Hub / Windows Server 2012 R2 / 0x80092004: .NET Framework Install Error on Windows Server

September 16, 2019 Windows 8Windows Server 2012 R2

0x80092004: .NET Framework Install Error on Windows Server

When installing NET Framework 4.7.2 using online and offline installers on Windows Server 2012 R2, I came across the error: 0x80092004 — Cannot find object or property. At the same time, the “Couldn’t find the hash of component: NetFx4-PenIMC” error appeared in the Event Viewer logs. It took me quite a lot of time to find the solution. As it turned out, the issue was related to an error in the installed .Net Framework 3.5 (or its updates) that prevented .NET 4.7.2 from being installed. I found an unevident solution that helped me and I would describe it here.

To fix the 0x80092004 (CRYPT_E_NOT_FOUND) error, you have to download .NET Framework update packages from Microsoft update catalog manually.

  1. Go to https://www.catalog.update.microsoft.com and search for KB4340558;
  2. Download the update 2018-07 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 8.1 and Server 2012 R2 for x64 (KB4340558);
  3. You will be suggested to download 3 MSU files. Download all of them and save them into the folder c:\Distr\update:
    windows8.1-kb4338415-x64_cc34d1c48e0cc2a92f3c340ad9a0c927eb3ec2d1.msu
    windows8.1-kb4338419-x64_4d257a38e38b6b8e3d9e4763dba2ae7506b2754d.msu
    windows8.1-kb4338424-x64_e3d28f90c6b9dd7e80217b6fb0869e7b6dfe6738.msu

    download windows update from microsoft update catalog
  4. Then extract the MSU files using this command:
    expand -f:* c:\Distr\update\*.msu c:\Distr\update\extract expand msu update files
  5. Several files will appear in the C:\Distr\update\extract. You need CAB files only. Integrate CAB updates into the Windows image using the DISM tool (if restart is required, do it):
    dism /online /add-package /packagepath:"C:\Distr\update\extract\Windows8.1-KB4338415-x64.cab"
    dism /online /add-package /packagepath:"C:\Distr\update\extract\Windows8.1-KB4338419-x64.cab"
    dism /online /add-package /packagepath:"C:\Distr\update\extract\Windows8.1-KB4338424-x64.cab"
    dism /online /add-package /packagepath:"C:\Distr\update\extract\WSUSSCAN.cab"
  6. If the 0x80092004 error appears when installing any of the CAB files, uninstall this update using the following command (for example, the error appeared during the installation of KB4338419):
    dism /online /remove-package /packagepath:"C:\Distr\update\extract\Windows8.1-KB4338419-x64.cab"
    Then install the same CAB file with this command:
    dism /online /add-package /packagepath:"C:\Distr\update\extract\Windows8.1-KB4338419-x64.cab"
    In my case, I had to install and remove KB4338419 two times in a row until the error 0x80092004 disappeared.
  7. Restart your server and try to install .Net 4.7.2 – it would install without any errors. Then remove the files from C:\Distr\update\.

This issue is fixed in Windows 8 in the same way.

0 comment
0
Facebook Twitter Google + Pinterest
previous post
How to Install and Activate the RDS Licensing Role on Windows Server 2019/2016?
next post
Install RSAT Feature on Demand on Windows 10 1809 and Later

Related Reading

Using TSADMIN.msc and TSCONFIG.msc Snap-Ins on Windows Server...

February 2, 2021

Updating the PowerShell Version on Windows

December 24, 2020

Zerologon (CVE-2020-1472): Critical Active Directory Vulnerability

December 4, 2020

How to Run CMD/Program under SYSTEM (LocalSystem) in...

December 3, 2020

Remote Desktop Services Is Currently Busy

October 27, 2020

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange
  • Windows 10
  • Windows 8
  • Windows 7
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2008 R2
  • PowerShell
  • VMWare
  • MS Office

Recent Posts

  • Accessing USB Flash Drive from VMWare ESXi

    February 26, 2021
  • How to Sign a PowerShell Script (PS1) with a Code Signing Certificate?

    February 25, 2021
  • Change the Default Port Number (TCP/1433) for a MS SQL Server Instance

    February 24, 2021
  • How to Shadow (Remote Control) a User’s RDP session on RDS Windows Server 2016/2019?

    February 22, 2021
  • Configuring PowerShell Script Execution Policy

    February 18, 2021
  • Configuring Proxy Settings on Windows Using Group Policy Preferences

    February 17, 2021
  • Updating Group Policy Settings on Windows Domain Computers

    February 16, 2021
  • Managing Administrative Shares (Admin$, IPC$, C$, D$) in Windows 10

    February 11, 2021
  • Packet Monitor (PktMon) – Built-in Packet Sniffer in Windows 10

    February 10, 2021
  • Fixing “Winload.efi is Missing or Contains Errors” in Windows 10

    February 5, 2021

Follow us

woshub.com
  • Facebook
  • Twitter
  • RSS
Popular Posts
  • How to Restore Deleted EFI System Partition in Windows 10?
  • How to Download APPX Installation File from Microsoft Store in Windows 10 / 8.1
  • How to Hide Installed Programs from Programs and Features in Windows?
  • Windows Doesn’t Assign Drive Letter to External and USB Flash Drives
  • WinSxS Folder: Clean Up and Compress in Windows 10 and 8.1
  • Enable Multiple Concurrent RDP Sessions in Windows 8.1 /8
  • Auto-Mount a VHD/VHDX File at Startup in Windows 10, 8.1
Footer Logo

@2014 - 2018 - Windows OS Hub. All about operating systems for sysadmins


Back To Top