Windows 11 Pro 24H2 Release Preview 261000.1876 webview2 hash mismatch in store

Anonymous
2024-09-26T20:27:22+00:00

over the weekend, i ran SFC /scannow as part of my routine Maintenace. normally the command returns with ther typical 'no error found' type of message. but this time it said it had found and fixed corrupted files. subsequent passes also said the same thing. i took ma look at the CBS.log, and each time it found an issue, it listed these files, which seem to be related to webview2 -

2024-09-26 12:43:45, Info CSI 000003a9 [SR] Repairing file ??\C:\WINDOWS\SystemApps\Shared\WebView2SDK\Microsoft.Web.WebView2.Core.dll from store

2024-09-26 12:43:45, Info CSI 000003aa [SR] Repairing file ??\C:\WINDOWS\SystemApps\Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe\Microsoft.Web.WebView2.Core.dll from store

2024-09-26 12:43:45, Info CSI 000003ab [SR] Repairing file ??\C:\WINDOWS\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\Microsoft.Web.WebView2.Core.dll from store

2024-09-26 12:43:45, Info CSI 000003ac [SR] Repairing file ??\C:\WINDOWS\SystemApps\Microsoft.Windows.SecureAssessmentBrowser_cw5n1h2txyewy\Microsoft.Web.WebView2.Core.dll from store

2024-09-26 12:43:45, Info CSI 000003ad [SR] Repairing file ??\C:\WINDOWS\SystemApps\Microsoft.Windows.OOBENetworkCaptivePortal_cw5n1h2txyewy\Microsoft.Web.WebView2.Core.dll from store

2024-09-26 12:43:45, Info CSI 000003ae [SR] Repairing file ??\C:\WINDOWS\ImmersiveControlPanel\Microsoft.Web.WebView2.Core.dll from store

2024-09-26 12:43:45, Info CSI 000003af [SR] Repairing file ??\C:\WINDOWS\SystemApps\ShellExperienceHost_cw5n1h2txyewy\Microsoft.Web.WebView2.Core.dll from store

2024-09-26 12:43:45, Info CSI 000003b0 [SR] Repairing file ??\C:\WINDOWS\SystemApps\Shared\WebView2SDK\Microsoft.Web.WebView2.Core.winmd from store

2024-09-26 12:43:45, Info CSI 000003b1 [SR] Repairing file ??\C:\WINDOWS\SystemApps\Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe\Microsoft.Web.WebView2.Core.winmd from store

2024-09-26 12:43:45, Info CSI 000003b2 [SR] Repairing file ??\C:\WINDOWS\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\Microsoft.Web.WebView2.Core.winmd from store

2024-09-26 12:43:45, Info CSI 000003b3 [SR] Repairing file ??\C:\WINDOWS\SystemApps\Microsoft.Windows.SecureAssessmentBrowser_cw5n1h2txyewy\Microsoft.Web.WebView2.Core.winmd from store

2024-09-26 12:43:45, Info CSI 000003b4 [SR] Repairing file ??\C:\WINDOWS\SystemApps\Microsoft.Windows.OOBENetworkCaptivePortal_cw5n1h2txyewy\Microsoft.Web.WebView2.Core.winmd from store

2024-09-26 12:43:45, Info CSI 000003b5 [SR] Repairing file ??\C:\WINDOWS\SystemApps\ShellExperienceHost_cw5n1h2txyewy\Microsoft.Web.WebView2.Core.winmd from store

the error it found with each of those files was this -

2024-09-26 12:52:49, Info CSI 0000024e Hashes for file member [l:31]'Microsoft.Web.WebView2.Core.dll' do not match.

Expected: {l:32 ml:33 b:a46788e94463899b6799304178a634643b20949cc7d378938db8abce8f69d17e}.

Actual: {l:32 b:50a5c14fd4da7116a2072d12cb94c258354d0237979d5d5afa979be740d118f5}.

2024-09-26 12:52:49, Info CSI 0000024f [SR] Repairing file ??\C:\WINDOWS\SystemApps\Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe\Microsoft.Web.WebView2.Core.dll from store

2024-09-26 12:52:49, Info CSI 00000250 Hashes for file member [l:33]'Microsoft.Web.WebView2.Core.winmd' do not match.

i tried both 'dism /online /cleanup-image /restorehealth' as well multiple passes of 'sfc /scannow' I also downloaded and did a repair install of Microsoft webview2, which completed successfuly, but did not solve the issue.

i am not sure how to proceed. webview2 seems to be working as it should. is this just a goof up caused by the last windows cum update (KB5043178)? if so what steps should take? or should i just leave it be and let

MS sort it out and publish a fix?

Windows Insider program | Windows Insider preview | Repair and recovery

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2024-10-11T18:41:59+00:00

Looks Like MS finally fixed the issue with KB5044384. for those that were having trouble installing the LCU released Tuesday (KB5044284), you need to have windows update repair windows. to do this go to settings > system > Recovery. then select the button marked 'Reinstall now'. Windows update will begin downloading a repair version of you OS. it will also install the LCU at the same time. after windows update finishes repairing your OS, restart. from there check for updates and windows update will find KB5044384 and begin downloading it. Windows will want to restart once it gets installed. let windows restart, then just for kicks, open terminal (or CMD prompt) and run the command 'SFC /SCANNOW'. SFC **should** come back saying "Windows Resource Protection did not find any integrity violations." if it doesn't say that, then you have other issues than the one discussed here in this thread.

(a special caveat: you must be enrolled in Windows insider program to get this update at the 'Release Preview' level or wait a week or two (or more) for the update to roll out to the release for everyone. )

although the link in updates for info about the update produces a Microsoft website 404 error, i was able to find the release notes on the update anyways. here is the link:

Releasing Windows 11 Build 26100.2152 to the Release Preview Channel | Windows Insider Blog

of particular note for this update is this line in the list of fixes:

  • [sfc /scannow command] Fixed: You get errors every time you run the command.

Was this answer helpful?

8 people found this answer helpful.
0 comments

89 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-10-10T07:07:43+00:00

    issue seems to have been compounded with the latest release of the LCU (KB5044284), every attempt to install the update ends in error 0x80073713. according to my research, this error stems from an error in the windows 'store'. on my system my least the only issue is as I have originally posted here, i.e. the webview2 files that are a part of the OS. dism finds no errors, and sfc only finds those files already reported here. all the other updates released on Tuesday installed, except for the LCU. At this point the ONLY workaround *MIGHT* be to perform a clean install and then ensure that the current LCU is installed and not an incremental LCU install. I for one am not going to be thrilled if this turns out to be the only solution to the problem MS caused in the first place with an update. If anyone else with this issue can confirm or deny that they are able to install the LCU or not, it would be helpful.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. CrazyKats 19,595 Reputation points Volunteer Moderator
    2024-10-09T15:37:02+00:00

    That has already been mentioned in this thread

    and others.

    Please file the issue in the Feedback Hub.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2024-10-07T23:03:54+00:00

    Insiders can only access Insider Feedback

    as far as I know.

    Hi CK,

    Looks like that is still the case.

    Since it was posted on this insider thread, I assumed that the FBH was filed from an insider account, but that is not the case.

    Anyway, this is quite a ridiculous and annoying restriction.

    https://aka.ms/AAslt9w

    If that was the case, why can I not link to it from my Release Desktop that is not in Insider. This is so weird. I have no issue connecting with your link.

    I have always connected with Insider links before on my Release as that is where I usually see them. They have always worked. It's a Monday, lol.

    Regards,

    Hi Johnny,

    It is not the Public Release that causes the restriction, it is the MS email address that is registered as insider.

    On my public release I had to create a second user with an email address that is not registered as insider. With that I could access the FBH as you can see on my previous post.

    Typical MS nonsense. 🤣🤣🤬

    Apparently that FBH was filed from a non-insider user.

    Here is an old link from 2018. Looks like they never fixed it. 🤣🤣

    Feedback Hub - Insider and non-Insider accounts cannot see each - Microsoft Community

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Johnny55 5,155 Reputation points Volunteer Moderator
    2024-10-07T20:29:29+00:00

    Hi fg2001, hi Johnny,

    I have no idea why access to the feedback doesn't work.

    Of course I have access withmy account.

    Maybe I have the option somewhere to give access?

    I'll take a look...

    Are you on an insider account or not?

    Just to check, I tried on Dev build as I used Release previously with no change. Same Error

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments