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: Oldest
Most helpful Newest Oldest
  1. CrazyKats 19,595 Reputation points Volunteer Moderator
    2024-10-02T19:33:58+00:00

    Build 26100.1882 is out, have you updated?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-10-02T20:09:08+00:00

    I am using 24H2, 26100.1882 installed through the windows installer tool, and then updated to 09-24 Cumulative Update preview.

    I ran sfc /scannow after windows installer upgraded me to 24H2 and it came back clean.

    I allowed 09-24 to install, and afterward my sfc /scannow runs exhibit the same behavior reported - says corrupted files, and that it has repaired them but subsequent sfc /scannow runs continue to report corrupted, and repaired.

    No number of runs of sfc /scannow solves the issue. It continues to errantly report corrupted files and repairs for every subsequent run, even after reboots.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more