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

Question

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?

Answer 1

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.

Answer 2

2024-10-09 21:03:19, Info CSI 000001e5 [SR] Beginning Verify and Repair transaction

2024-10-09 21:03:19, Info CSI 000001e6 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-10-09 21:03:19, Info CSI 000001e7 [SR] Repairing file ??\C:\WINDOWS\SystemApps\Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe\Microsoft.Web.WebView2.Core.dll from store

2024-10-09 21:03:19, Info CSI 000001e8 Hashes for file member [l:33]'Microsoft.Web.WebView2.Core.winmd' do not match.

Expected: {l:32 ml:33 b:84c0515b0adf5f0078b2ce28d84912ebc071737c2150d781a2d15a7464390e92}.

Actual: {l:32 b:0491fcbadc7e2e7320f741a9a562612305e515930811f176eab1b00ae5eb9d91}.

2024-10-09 21:03:19, Info CSI 000001e9 [SR] Repairing file ??\C:\WINDOWS\SystemApps\Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe\Microsoft.Web.WebView2.Core.winmd from store

2024-10-09 21:03:19, Info CSI 000001ea [SR] Repair complete

2024-10-09 21:03:19, Info CSI 000001eb [SR] Committing transaction

2024-10-09 21:03:19, Info CSI 000001ec Creating NT transaction (seq 1)

2024-10-09 21:03:19, Info CSI 000001ed Created NT transaction (seq 1) result 0x00000000, handle @0x3388

2024-10-09 21:03:19, Info CSI 000001ee Transaction UoW: {9328b0f1-8668-11ef-81da-00d861fc0ae7} for BeginTransaction

2024-10-09 21:03:19, Info CSI 000001ef Primitive operation timings: Registry: 0ms, Files: 2ms

2024-10-09 21:03:19, Info CSI 000001f0@2024/10/9:18:03:19.414 Beginning NT transaction commit...

2024-10-09 21:03:19, Info CSI 000001f1 Transaction UoW: {9328b0f1-8668-11ef-81da-00d861fc0ae7} for CommitTransaction

2024-10-09 21:03:19, Info CSI 000001f2@2024/10/9:18:03:19.422 CSI perf trace:

CSIPERF:TXCOMMIT;8125

2024-10-09 21:03:19, Info CSI 000001f3 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

26100.2033 still same ....

Answer 3

I have exactly the same issue. I have Windows 11 24H2 build 26100.1882. Very frustrated because the issue came on a freshly installed Windows 11 and already tried reinstalling Windows. No matter how many times I performed sfc scannow, it produced the same error and repairing it again and again and again. Everything in my system is updated to latest including firmware of my BIOS. My system is AMD Ryzen 9 7900X, MSI B650 tomahawk wifi motherboard, Samsung 990 Pro 1TB ssd

Answer 4

I got this error too when using sfc/scannow in the 24H2 26100.1882 build.

Answer 5

Report it in the Feedback Hub.

It might be related to the same issue

that some of us are seeing on the Dev Build.

If everything is working OK I'd just leave it be.

okay, thanks. i will wait about a week to see if it gets fixed. if it doesn't, i will post to feedback