Issue with Windows 10 update stuck on Version 1809 (error 0x80240034)

Hello as the title says my windows does not update to the latest version there is some issue getting error 0x80240034 which every option that needs to updated see screenshot (1)



I searched for it online and found out to perform SFC /scannow via a command prompt

I did that as well see screenshot (2)



I got this "Windows Resource Protection found corrupt files but was unable to fix some of them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline repairs, details are included in the log file provided by the /OFFLOGFILE flag.

Now I have opened the log file but since I am a noob can some one please help me to fix these corrupt file.
Can someone help me please. I am sharing the link for my CBS log file http://ul.to/0n9g5rqg

Also sharing my sfcdetails.txt file with you guys http://ul.to/jzm8ollp

Under no circumstances I will reinstall/refresh my windows since I do not want to lost my settings/files/software's installed my current windows version is Windows 10 Per Version 1809 (OS Build 17763.557)

Hi,
Post a screen shot of your disk with free minitool don't update when prompted
MiniTool Partition Wizard Free Download (2021 Latest) for Windows 10, 8, 7

dalchina said:

Hi, see e.g.
How To Fix Error 0x80240034 in Windows 10
- often worth searching for the error number.

Try
Reset Windows Update in Windows 10
which is more complete than the section starting
Reset Windows Updates

in the article above.

You can download an iso file to upgrade Win 10 manually e.g. using the MS media creation tool.
Rt click the iso file, click Mount
Open the new drive letter created in file explorer
Double click setup.exe
Opt to NOT accept updates as part of the upgrade to reduce failure possibility.

Ensure you have at least 30Gb free on C:
Disable or remove any 3rd party security software.

One final possibility that might help: perform an in-place upgrade repair of 1809 -like any upgrade that keeps all progs and data.

For that you need an 1809 iso file, used as above. Obtainable using e.g. the Heidoc iso downloader (free) -that's an iso from MS.

More: see the upgrade log files, run setupdiag.exe (free from MS - Google it).
Note upgrade failures can be next to impossible to resolve. If so, based on your last statement, you could stay on 1809 and disable Windows Updates.

1809? Begs the question of why you've not upgraded until now...

Ran the following commands:

DISM /Online /Cleanup-image /Scanhealth which completed 100% and said that "The component store is repairable"

After which I went forward with DISM /Online /Cleanup-image /Restorehealth

It has been 4 hours now DISM /Online /Cleanup-image /Restorehealth is stuck at 85.5% see screenshot kinda makes me worried and I do not want to break my windows at all

https://www.tenforums.com/attachment...a-untitled.png

kufr said:

I got this "Windows Resource Protection found corrupt files but was unable to fix some of them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline repairs, details are included in the log file provided by the /OFFLOGFILE flag.

Hello

the files that are defective there are part of a Windows 1809 installation medium.

2021-01-02 18:40:25, Info CSI 00005064 [SR] Cannot repair member file [l:13]'SBCModel.json' of Microsoft-Windows-Update-UX-UserPredictionModel, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch2021-01-02 18:40:25, Info CSI 00005066 [SR] Cannot repair member file [l:12]'SBCModel.txt' of Microsoft-Windows-Update-UX-UserPredictionModel, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2021-01-02 18:40:25, Info CSI 00005068 [SR] Cannot repair member file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2021-01-02 18:40:25, Info CSI 0000506a [SR] Cannot repair member file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2021-01-02 18:40:25, Info CSI 0000506c [SR] Cannot repair member file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2021-01-02 18:40:25, Info CSI 0000506e [SR] Cannot repair member file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2021-01-02 18:40:25, Info CSI 00005070 [SR] Cannot repair member file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2021-01-02 18:40:25, Info CSI 00005072 [SR] Cannot repair member file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2021-01-02 18:40:25, Info CSI 00005074 [SR] Cannot repair member file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2021-01-02 18:40:25, Info CSI 00005076 [SR] Cannot repair member file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2021-01-02 18:40:25, Info CSI 00005078 [SR] Cannot repair member file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2021-01-02 18:40:25, Info CSI 0000507b [SR] Cannot repair member file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

Do you have one?

If not, I can also provide you with a repair file.

Friendly greetings
Sorry for any mistakes. English is not my native language.

Paul Black said:

Hello @kufr,

Is your problem the same as the one here? => Difficulty running Dism commands

If so, it will be confusing because members who have replied to your problem in either thread will NOT know what you have already been asked to perform, what you have performed, and what the results were!

I think it is I will mark this thread as resolved and get to my other thread thanks for pointing it out

I was able to do the in-place upgrade without losing any of my installed apps/setting/files or folders on my Drive C. If I knew it would be so easy I would have directly gone for the in-place upgrade

This was the tutorial that I followed Repair Install Windows 10 with an In-place Upgrade

Guys go ahead if the windows update is giving you issue and you cannot fix it just like me who was stuck with Microsoft Windows 10 Pro Version 1809 (Os Build 17763.557) and was not able to update to the latest Windows 10, version 20H2 go ahead and follow the guide above.