Windows 10: Windows 10 Update: 1803 update from 1803 to 1909 / now 20H2 failing for >1 year: Corrupt...

Discus and support Windows 10 Update: 1803 update from 1803 to 1909 / now 20H2 failing for >1 year: Corrupt... in Windows 10 Installation and Upgrade to solve the problem; Windows update has failed for over 1 year from1803 to 1909 and now 20H2: Background info: error codes: 0xc1900101 and 0x80240034 system spec: see... Discussion in 'Windows 10 Installation and Upgrade' started by Justin__J, Dec 15, 2020.

  1. JUSTIN__J
    Justin__J Win User

    Windows 10 Update: 1803 update from 1803 to 1909 / now 20H2 failing for >1 year: Corrupt...


    Windows update has failed for over 1 year from1803 to 1909 and now 20H2:

    Background info:

    • error codes: 0xc1900101 and 0x80240034
    • system spec: see extract below #1
    • ran SFC scan: failed to repair corrupt files: see details below #2
    • onward searches to fix these specific file corruptions were not clear or did not seem appropriate to me

    I welcome suggestions for targeted fixes please.


    Thank you,
    Justin


    #2 =======extract from SFC.LOG - subset: cannot repair fails only===============================


    2020-12-15 13:14:54, Info CSI 000043af [SR] Beginning Verify and Repair transaction
    2020-12-15 13:14:55, Info CSI 000043b1 [SR] Cannot repair member file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-12-15 13:14:55, Info CSI 000043b3 [SR] Cannot repair member file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-12-15 13:14:55, Info CSI 000043b5 [SR] Cannot repair member file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-12-15 13:14:55, Info CSI 000043b7 [SR] Cannot repair member file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-12-15 13:14:55, Info CSI 000043b9 [SR] Cannot repair member file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-12-15 13:14:55, Info CSI 000043bb [SR] Cannot repair member file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-12-15 13:14:55, Info CSI 000043bd [SR] Cannot repair member file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-12-15 13:14:55, Info CSI 000043bf [SR] Cannot repair member file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-12-15 13:14:55, Info CSI 000043c1 [SR] Cannot repair member file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-12-15 13:15:01, Info CSI 000043d2 [SR] Cannot repair member file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-12-15 13:15:01, Info CSI 000043d3 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2020-12-15 13:15:01, Info CSI 000043d5 [SR] Cannot repair member file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-12-15 13:15:01, Info CSI 000043d6 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2020-12-15 13:15:01, Info CSI 000043d8 [SR] Cannot repair member file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-12-15 13:15:01, Info CSI 000043d9 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2020-12-15 13:15:01, Info CSI 000043db [SR] Cannot repair member file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-12-15 13:15:01, Info CSI 000043dc [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2020-12-15 13:15:01, Info CSI 000043de [SR] Cannot repair member file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-12-15 13:15:01, Info CSI 000043df [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2020-12-15 13:15:01, Info CSI 000043e1 [SR] Cannot repair member file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-12-15 13:15:01, Info CSI 000043e2 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2020-12-15 13:15:01, Info CSI 000043e4 [SR] Cannot repair member file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-12-15 13:15:01, Info CSI 000043e5 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2020-12-15 13:15:01, Info CSI 000043e7 [SR] Cannot repair member file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-12-15 13:15:01, Info CSI 000043e8 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2020-12-15 13:15:01, Info CSI 000043ea [SR] Cannot repair member file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-12-15 13:15:01, Info CSI 000043eb [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2020-12-15 13:15:01, Info CSI 000043ee [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpComputerStatus.cdxml; source file in store is also corrupted
    2020-12-15 13:15:01, Info CSI 000043f1 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreat.cdxml; source file in store is also corrupted
    2020-12-15 13:15:01, Info CSI 000043f4 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreatCatalog.cdxml; source file in store is also corrupted
    2020-12-15 13:15:01, Info CSI 000043f7 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreatDetection.cdxml; source file in store is also corrupted
    2020-12-15 13:15:01, Info CSI 000043fa [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpPreference.cdxml; source file in store is also corrupted
    2020-12-15 13:15:01, Info CSI 000043fd [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpScan.cdxml; source file in store is also corrupted
    2020-12-15 13:15:01, Info CSI 00004400 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpWDOScan.cdxml; source file in store is also corrupted
    2020-12-15 13:15:01, Info CSI 00004403 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpSignature.cdxml; source file in store is also corrupted
    2020-12-15 13:15:01, Info CSI 00004406 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\Defender.psd1; source file in store is also corrupted
    2020-12-15 13:15:05, Info CSI 00004469 [SR] Verify complete


    #1 =======system spec = more available upon request===========

    [System Summary]

    Item Value
    OS Name Microsoft Windows 10 Home
    Version 10.0.17134 Build 17134
    Other OS Description Not Available
    OS Manufacturer Microsoft Corporation
    System Name ANTHNYSWS-PC
    System Manufacturer Hewlett-Packard
    System Model HP Pavilion dv7 Notebook PC
    System Type x64-based PC
    System SKU WC159EA#ABU
    Processor IntelR CoreTM i5 CPU M 430 @ 2.27GHz, 2267 Mhz, 2 Cores, 4 Logical Processors
    BIOS Version/Date Hewlett-Packard F.1A, 4/1/2010
    SMBIOS Version 2.6
    Embedded Controller Version 50.37
    BIOS Mode Legacy
    BaseBoard Manufacturer Hewlett-Packard
    BaseBoard Model Not Available
    BaseBoard Name Base Board
    Platform Role Mobile
    Secure Boot State Unsupported
    PCR7 Configuration Binding Not Possible
    Windows Directory C:\WINDOWS
    System Directory C:\WINDOWS\system32
    Boot Device \Device\HarddiskVolume1
    Locale United Kingdom
    Hardware Abstraction Layer Version = "10.0.17134.1098"
    User Name anthnysws-PC\anthnysws
    Time Zone GMT Standard Time
    Installed Physical Memory RAM 4.00 GB
    Total Physical Memory 3.93 GB
    Available Physical Memory 801 MB
    Total Virtual Memory 7.93 GB
    Available Virtual Memory 2.25 GB
    Page File Space 4.00 GB
    Page File C:\pagefile.sys
    Kernel DMA Protection Off
    Virtualization-based security Not enabled
    Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/devices detected, Disabled by policy, TPM is not usable
    Hyper-V - VM Monitor Mode Extensions Yes
    Hyper-V - Second Level Address Translation Extensions Yes
    Hyper-V - Virtualization Enabled in Firmware No
    Hyper-V - Data Execution Protection Yes

    :)
     
    Justin__J, Dec 15, 2020
    #1
  2. BTARUNR
    btarunr Win User

    Microsoft Rolls Out Windows 10 April 2018 Update (build 1803)

    Any Office365 users here? Does Outlook (or any Office app for that matter) request activation after each system restart post this Windows 1803 update?
     
    btarunr, Dec 15, 2020
    #2
  3. DRONE
    Drone Win User
    Drone, Dec 15, 2020
    #3
  4. KASTRIOT
    kastriot Win User

    Windows 10 Update: 1803 update from 1803 to 1909 / now 20H2 failing for >1 year: Corrupt...

    Latest win10 Update 1803 cant install?

    Windows 10 1803 update issues(Solved!)
     
    kastriot, Dec 15, 2020
    #4
Thema:

Windows 10 Update: 1803 update from 1803 to 1909 / now 20H2 failing for >1 year: Corrupt...

Loading...

  1. Windows 10 Update: 1803 update from 1803 to 1909 / now 20H2 failing for >1 year: Corrupt... - Similar Threads - Update 1803 update

  2. W10 update from 1803 to 20H2 fails

    in Windows 10 Installation and Upgrade
    W10 update from 1803 to 20H2 fails: I have tried all the measures described in the various topics and cannot get the upgrade to work The last attempt was via ISO downloaded from MS. Final option option is to wipe and reinstall but I'd like a solution if possible I have the required logs Full install failed...

  3. Updating from Windows 1803 to 20H2

    in Windows 10 Installation and Upgrade
    Updating from Windows 1803 to 20H2: Hi all: I've got a Toshiba laptop that has been sitting for years because it had become un-useable due to extreme slow performance. Last update was October 2018 - Version 1803. Decided to try to revive it this week. It's working fine now but won't update to 202H. It doesn't...

  4. Windows update, 1803 to 1906/1909 failed

    in Windows 10 Installation and Upgrade
    Windows update, 1803 to 1906/1909 failed: Hi, I have been having this prevailing problem where many others are having the same issue I am facing. My laptop keeps failing to update from version 1803. This is what I have tried so far which have not worked: - setting, windows update - downloaded the installer,...

  5. Failed Windows 10 64 bit Update from 1803 to 1909

    in Windows 10 Installation and Upgrade
    Failed Windows 10 64 bit Update from 1803 to 1909: I have been working for several months now to update my Windows from 1803 to 1909. I have tired: 1 Updating the usual was via Windows Update in settings. 2 Updating using the Media Creation Tool. 3 Disabling all USB drives and accessories. 4 Turning off my antivirus...

  6. Windows 10 Update from 1803 to 1909 fails with 0xc19001e1

    in Windows 10 Installation and Upgrade
    Windows 10 Update from 1803 to 1909 fails with 0xc19001e1: Hi, for quite some time my laptop cannot update from 1803 to 1909. It always ends with error code 0xc19001e1. I have tried various online fixes, but none helped. Any idea what could the cause or where to look for the cause. Thanks in advance! FYI, I have tried updating...

  7. Windows 10 update 1803 to 1909 failed

    in Windows 10 Installation and Upgrade
    Windows 10 update 1803 to 1909 failed: Hi, I have tried everything that is suggested like removing the softwareDistribution directory and running repair, troubleshooting but the update always failed around 60% of the update. The update will rollback. How can I resolved this problem. Thank you....

  8. Windows 10 1803 update to 1909 failed installation

    in Windows 10 Installation and Upgrade
    Windows 10 1803 update to 1909 failed installation: Hello, my PC currently runs Windows 10, version 1803 (build 17134.1069). A few days earlier, I saw that the Win 10 version 1909 came out, so I wanted to update. I was surprised to notice that my version was 1803, an old one. How come my PC didn't update automatically to the...

  9. Updating from 1803 to 1909

    in Windows 10 Installation and Upgrade
    Updating from 1803 to 1909: Error message after a few hours of downloading and updating. 'Windows could not configure one or more system components. To install Windows, restart the computer then restart the installation' after it downloads 100%, reaches a stage where it says something like you computer...

  10. updating from 1803 to 1909

    in Windows 10 Installation and Upgrade
    updating from 1803 to 1909: I am trying to update from windows 1803 to 1909, I get this error message after a few hours of downloading and updating. 'Windows could not configure one or more system components. To install Windows, restart the computer then restart the installation' after it downloads...