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-11T18:25:59+00:00

    @Cybot,

    The problem was fixed with Build 26100.2152. it was stated in the blog for that Build..

    Still failing with 26120.2122.

    From 26100.2152 blog:

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

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-10-11T18:15:48+00:00

    actually it did fix things. after windows update did it's thing, windows was reinstalled along with the LCU. but SFC still reported the issue. then i noticed windows update wanted to download a new CU (KB5044384) after the update was installed and i rebooted, the issue was no longer present. sfc came back with no errors found (Windows Resource Protection did not find any integrity violations.)

    so, the problem really did get fixed after all.

    I am now on Windows 11 Pro 24H2 (build 26100.2152)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-10-10T20:49:39+00:00

    erm.... before i contact MS.... i am going to try one of 24H2's new features... it is essentially doing a repair install, but everything is handled by Windows Update. you can find it i the settings app under 'System > Recovery > Fix problems using windows update'. Windows update will begin a download titled 'Windows 11, 24H2 (Repair Verson). depending on your connection speed it can take quite a while to download. I am just guessing here, but it is probably about the same amount of time it takes to download a copy of the windows 11 24h2 .ISO. for me it's something like 3-4 hours or more because i have a really slow connection. but for others i would imagine it would go much quicker.

    again.... this is sorta like doing a Repair install, but not needing an .iso or a flash drive or DVD with the setup files on it. IMO, it is worlds better than the other option - Windows Reset. because all your files, apps and settings remain intact, unlike with a windows reset. also, as a bonus, Windows Update also installs any updates at the same time. so with any luck, we might be able to get around this mess.

    That is not going to solve the current problems. We have to wait for a fix. 😂😂🤷‍♂️

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-10-10T19:27:00+00:00

    Well, I installed Windows 11 iOT without the Store and have that same error. I read somewhere it was from something with Edge and worried about it

    just to be clear i am not talking about the store app... i am referring to the windows 'store' of files that windows keeps in "c:\windows\WinSXS" they are used to keep the system operational. i know having more than one thing in the OS referred to as a store can be confusing....

    Was this answer helpful?

    0 comments