Cannot install .netframework on windows 10 machine

Divya Bollina 0 Reputation points

Installation of .NET48 fails with " Error 80092004 "

CBS.log shows

2026-04-10 13:04:39, Info CSI 00000360 Couldn't find the hash of component: NetFx4-corperfmonsymbols_h, version 4.0.15744.161, arch amd64, versionScope neutral, pkt {l:8 b:b03f5f7f11d50a3a} in the catalog [l:96]'\SystemRoot\WinSxS\Catalogs\81ed2e51aaf2b5e4c6192f5a26abec9a83aff1a31639025f7dc44933a341f38b.cat'.

2026-04-10 13:04:39, Error CSI 00000361@2026/4/10:07:34:39.059 (F) onecore\base\wcp\componentstore\csd_winners.cpp(1719): Error 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] originated in function CCSDirectTransaction::AddImplicationsToCatalogsAndVerifyComponentHashes expression: (null)

[gle=0x80004005]

Tried the Microsoft.NET repair tool, ran repair corrupt system files commands and rstarted the machine.

DISM /Online /Cleanup-Image /RestoreHealth

sfc /scannow

Please suggest steps to solve this

  1. Jack Dang (WICLOUD CORPORATION) 18,970 Reputation points • Microsoft External Staff • Moderator

    Hi @Divya Bollina ,

    I would need more time to investigate this issue. I will get back to you as soon as possible.

Sign in to comment

2 answers

  1. Jack Dang (WICLOUD CORPORATION) 18,970 Reputation points • Microsoft External Staff • Moderator

    Hi @Divya Bollina ,

    Thanks for reaching out.

    On Windows 10, .NET Framework 4.8 is already included as part of the OS, so this is not really a separate .NET installation issue. The CBS log suggests the problem is with the Windows component store and servicing stack, so the focus should be on repairing that instead of reinstalling .NET.

    Since you’ve already run SFC and DISM once, please try DISM again using a clean local source from a matching Windows 10 ISO:

    DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:X:\sources\install.wim:<index> /LimitAccess

    If your ISO contains install.esd instead of install.wim, you can use:

    DISM /Online /Cleanup-Image /RestoreHealth /Source:ESD:X:\sources\install.esd:<index> /LimitAccess

    Replace X: with the mounted ISO drive letter.

    The <index> value needs to match the edition installed on the machine. You can confirm the correct index by running:

    DISM /Get-WimInfo /WimFile:X:\sources\install.wim

    or install.esd if applicable.

    Once that completes, it’s a good idea to run:

    sfc /scannow

    again to ensure system files are now consistent with the repaired component store.

    If the same CBS error still appears after a source-based repair, that usually indicates the corruption is beyond what DISM can fix. In that case, the most reliable and supported resolution is a Windows 10 in-place repair upgrade. Running setup from the ISO and choosing “keep files and apps” will rebuild the servicing stack and component store while preserving your data and applications.

    As a secondary check, make sure the system isn’t blocked from updating its root certificates, since cryptographic validation is involved. However, given the specific error here, the primary issue is the component store inconsistency.

    Hope this helps! If my explanation and the information I provided were useful, I would greatly appreciate it if you could follow the instructions here so others with the same problem can benefit as well.

    1. Jack Dang (WICLOUD CORPORATION) 18,970 Reputation points • Microsoft External Staff • Moderator

      Hi @Divya Bollina ,

      If you're still interested or have any questions, feel free to reach out whenever it works best for you. 

    Sign in to comment

  2. AI answer

    Error 0x80092004 during .NET Framework 4.8 installation together with CBS messages about missing or invalid hashes indicates component store/catalog corruption. The supported remediation path is to repair the Windows component store with DISM, then re-run SFC, and only then attempt the .NET installation again.

    Follow these steps in order:

    1. Open an elevated Command Prompt
      • Select Start, type cmd.
      • Right‑click Command Prompt → Run as administrator.
    2. Repair the component store with DISM
      • Run: 
         DISM.exe /Online /Cleanup-image /Restorehealth
      • Wait for it to complete. This may take several minutes.
      • If the machine cannot reach Windows Update or DISM reports source errors, use a known‑good repair source instead, for example a matching Windows installation or media, e.g.: 
         DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess
        Replace C:\RepairSource\Windows with the actual path to a valid Windows source.
    3. Run System File Checker
      • After DISM completes successfully, run: 
         sfc /scannow
      • Wait for it to finish and confirm it reports that corruption was repaired or no integrity violations were found.
    4. Check CBS details if problems persist
      • To extract SFC‑related entries from CBS.log to a readable file on the desktop: 
         findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
      • Review sfcdetails.txt for files that could not be repaired. If specific corrupted files are identified and DISM still cannot repair them, use the advanced DISM method:
        • Collect correct versions of the corrupted files (for example, from a matching Windows image or update packages) into C:\temp\Source.
        • Then run: 
           DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\temp\Source\ /LimitAccess
        • Verify with: 
           DISM /Online /Cleanup-Image /ScanHealth
    5. Retry .NET Framework 4.8 installation
      • Once DISM and SFC both complete without reporting unrepairable corruption, run the .NET Framework 4.8 installer again.

    If DISM and SFC repeatedly report success but .NET 4.8 still fails with the same CBS catalog/hash errors, the remaining supported option indicated in similar update‑corruption scenarios is to repair or reinstall the current Windows version (for example, an in‑place repair of Windows 10) and then install .NET 4.8 again.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.
Sign in to answer

Your answer