[SOLVED] Win 11 24h2 26100.1876 Sfc hashes missmatch WebView2

E

ElbernTsinah

Member
Joined
Sep 25, 2024
Posts
24
Hello,

I use an insider release preview version 26100.1876 Windows Feature Experience Pack 1000.26100.23.0 I won't post ComponentScanner compressed archive as it's only for mainline.
I opted in to release preview a few month ago Sfc and Dism ran well for months.

But after doing an inplace upgrade from release preview iso, i have those entry using sfc /scannow that cause problems:

2024-09-26 02:14:39, Info CSI 00000526 Hashes for file member [l:33]'Microsoft.Web.WebView2.Core.winmd' do not match.
2024-09-26 02:14:39, Info CSI 00000524 Hashes for file member [l:31]'Microsoft.Web.WebView2.Core.dll' do not match

I reboot then run again sfc /scannow and Dism /Online /Cleanup-Image /RestoreHealth
It keep trying fixing the missmatch version.

scanhealth and checkhealth no error or corrupted component store.

Detail:

The problem appeared after i opted out by error to windows update insider program clicking on the link to unroll the account from insider.
After rebooting i opted in again to insider program.
I was switched by error to Dev channel.

I paused windows update that was downloading the dev release version.

I used offlineinsiderenroll to switch to release preview offline and did an inplace upgrade from release preview iso.
Once in place upgrade completed, I used offlineinsiderenroll STOP_INSIDER.
I did a reboot.

I opted in to insider program again with my microsoft account.
I was in fact back to insider preview channel.

This is after in place upgrade from iso than sfc issue arised.
So I did a windows update repair.
a new issue:
I had a phantom old version of windows showing in windows cleanup. aus logic boostspeed couldn't find this phantom update.
I was despaired and used dism++ to remove package_for_RollupFix~31bf3856ad364e35~amd64~~261001742.1.10
The phantom old windows never showed again in windows cleanup tool.

when i started Dism /Online /Cleanup-Image /StartComponentCleanup I had a 1702 error at 71.4%
I did another windows update repair upgrade, searched anywhere on the web for a fix, then found Sysnative forum :)
package_for_RollupFix~31bf3856ad364e35~amd64~~261001742.1.10 was reinstalled by windows update repair as shown in dism++ so it's ok i won't touch it, and removed dism++, as this tool is too powerfull for me.


I'm sorry for the wall of text, i thought giving details about how things happend would help to explain where things went wrong :)
 

Attachments

I wanted to edit previous message but could'nt find a way i guess.

Interesting thing is in a previous repair using the webview2engine repair function would lead to more cbs log error. (modify, then click on repair, it does reinstall webview2)
 
Last edited:
Hello,
I used again in order sfc /scannow and Dism /Online /Cleanup-Image /RestoreHealth
And i noticed more entry suddenly I just post the cbs log just in case. :

There is also phantom Windows update cleanup that is back on track, cleaning worked ( took some time) but the entry reapair into windows cleanup tool




\WebView2SDK\\Microsoft.Web.WebView2.Core.dll from store
2024-09-26 14:23:18, Info CSI 000007b4 [SR] Repairing file \??\C:\WINDOWS\SystemApps\Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe\\Microsoft.Web.WebView2.Core.dll from store
2024-09-26 14:23:18, Info CSI 000007b5 [SR] Repairing file \??\C:\WINDOWS\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\\Microsoft.Web.WebView2.Core.dll from store
2024-09-26 14:23:18, Info CSI 000007b6 [SR] Repairing file \??\C:\WINDOWS\SystemApps\Microsoft.Windows.SecureAssessmentBrowser_cw5n1h2txyewy\\Microsoft.Web.WebView2.Core.dll from store
2024-09-26 14:23:18, Info CSI 000007b7 [SR] Repairing file \??\C:\WINDOWS\SystemApps\Microsoft.Windows.OOBENetworkCaptivePortal_cw5n1h2txyewy\\Microsoft.Web.WebView2.Core.dll from store
2024-09-26 14:23:18, Info CSI 000007b8 [SR] Repairing file \??\C:\WINDOWS\ImmersiveControlPanel\\Microsoft.Web.WebView2.Core.dll from store
2024-09-26 14:23:18, Info CSI 000007b9 [SR] Repairing file \??\C:\WINDOWS\SystemApps\ShellExperienceHost_cw5n1h2txyewy\\Microsoft.Web.WebView2.Core.dll from store
2024-09-26 14:23:18, Info CSI 000007ba [SR] Repairing file \??\C:\WINDOWS\SystemApps\Shared\WebView2SDK\\Microsoft.Web.WebView2.Core.winmd from store
2024-09-26 14:23:18, Info CSI 000007bb [SR] Repairing file \??\C:\WINDOWS\SystemApps\Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe\\Microsoft.Web.WebView2.Core.winmd from store
2024-09-26 14:23:18, Info CSI 000007bc [SR] Repairing file \??\C:\WINDOWS\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\\Microsoft.Web.WebView2.Core.winmd from store
2024-09-26 14:23:18, Info CSI 000007bd [SR] Repairing file \??\C:\WINDOWS\SystemApps\Microsoft.Windows.SecureAssessmentBrowser_cw5n1h2txyewy\\Microsoft.Web.WebView2.Core.winmd from store
2024-09-26 14:23:18, Info CSI 000007be [SR] Repairing file \??\C:\WINDOWS\SystemApps\Microsoft.Windows.OOBENetworkCaptivePortal_cw5n1h2txyewy\\Microsoft.Web.WebView2.Core.winmd from store
2024-09-26 14:23:18, Info CSI 000007bf [SR] Repairing file \??\C:\WINDOWS\SystemApps\ShellExperienceHost_cw5n1h2txyewy\\Microsoft.Web.WebView2.Core.winmd from store
2024-09-26 14:23:18, Info CSI 000007c0 [SR] Repair complete
 

Attachments

Last edited:
I'm maybe on something:

disabling and enabling again optional windows functions: .net framework 3.5 (include .net 2.0 and 3.0) then 4.8 advanced services asp.net 4.8 + and tcp shareport

After both install i checked windows update again, and KB5043178 did appear.
KB5043178 include: WebView2 apps improvements.
lol for whatever reason, maybe previous in place upgrade, and windows update repair , missed this KB.
Curently installing, i will check later if it does fix things.
 
/startcomponent cleanup worked as windows update repair replaced some winsxs components, and reset flags i guess ?
Still webview hashes error, and windows update 8,63 Go (8.3Gb) I think i have read that it would happen if windows update cleanup was forced interrupted by the user.

Yesterday i found flags in rush (regedit) keys about windows cleanup i didn't touched anything, i forgot to put a note somewhere about where those reg keys could be found there was some flags that could be changed there.
Maybe there will be a way to tell windows, the cleanup completed, or something by reseting some flags in rush or elsewhere, but i don't want to risk more harm than good.
I did enough silly things over time, i don't wanna add up more messing with windows system ^^
Problem is i like to touch everything.

When i had a laptop with kde neon, i could do things, i would never try on windows lol.
On my main computer, i really love windows, it's just a bit different, sometime i prefer windows over linux, it depend of the tasks required and softwares to use. If i was on an apple os i would be happy same for windows or linux ^^
I watched a live twitch where twitch users all together, was installing almost from scratch every packages, required to install and run one linux distributions, giving orders by wrighting commands on the chat, it would be
The kind of things you won't see often on windows lol

From know, i won't try to figure how to fix cbs log, and play with Winsxs rush, and other places related.
Even if i would love to apply fix manually not using a tool :)




​

 
Last edited:
C:\WINDOWS\SystemApps\Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe\\Microsoft.Web.WebView2.Core.dll

I reinstalled windows this time with help of a custom UUP dump iso version of Win 11 24h2 fr Home.
Previously i tryed a dism repair pointing to the iso install.wim.


I used a website to calculate the hash from sources\install.wim and Systemapps folder from the fresh in place upgrade i did:
a46788e94463899b6799304178a634643b20949cc7d378938db8abce8f69d17e sha 256.

I will reboot later and try sfc scan now to see if it would complain again, anyway i see winsxs is very complex, about manifest, hardlink to different folders and so on, mayube rush keys everywhere ^^
since hours and days, i have read informations from different forums, and website to understand how things like this happen, but i"m still confused.
 
Hello,

Digging for more data, i found: SFC flags Windows Defender PowerShell module files as corrupted - Windows Client

Maybe it's similar to what is discribe on this article.
WebView2 can be found everywhere on a windows install, it's used by many components, apps integrating it for browsing catalog usage i guess.
Windows itself use webview for different tools / settings pannel, each requiring a different version of WebView2.

It's very deeply integrated to windows system.
The computer is used by different family members, and i felt guilty about thinking i did borked windows 11 24h2 install doing something wrong.
It's maybe not the case.

Anyway the fix is about waiting for a future update of windows.
If a sayd update happen it will tell to sfc: updated versions that are signed by using a Microsoft certificate that the Windows operating system trusts should not be flaged, it does require a future windows update to the Windows Image ?

Is it still possible the problem happened because conflict with traces of an old KB or windows in place upgrad setting pointing to older version of systeme webview 2 found in different folders compared to the current windows image of 24h2 ?
I have Racing imagination and more i dig, the more i imagine things, the more i dig in loop lol
 
Decouple Windows App versioning: windows app SDK version 1.6

I guess it's a nice advancement, to point to edge webview2 sdk ( installed in program files microsoft folder.
All apps built from 1.6 wil not have to embed a version that should stuck to the version of windows app SDK that it was built from.

I think there are reference to entrys of microsoft windows store windows app sdk as well, but it should not removed by user, as apps requiring a specific version of windows app sdk, may not work if next version is not retrocompatible to previous one.
I reinstalled 1.5 version and 1.6 version of the sdk, no change at all.

The Windows App SDK now consumes the Edge WebView2 SDK as a NuGet reference rather than embedding a hardcoded version of the Edge WebView2 SDK. The new model allows apps to choose a newer version of the Microsoft.Web.WebView2 package instead of being limited to the version with which the Windows App SDK was built. The new model also allows apps to reference NuGet packages which also reference the Edge WebView2 SDK

From now, there are reference of webview dlls related to framework something, office something it goes everywhere.

I'm really happy that there is no need anymorer to embed a hardcoded version of edge webview2 sdk.
It was flying everywhere on windows lol, simpler from now.
 
edit: opening Microsoft.Web.WebView2.Core.winmd (in notepad++) it does say WindowsRuntime 1.4 does it's windows appruntime sdk 1.4 ?

I went to C:\Windows\SystemApps\Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe as it's one folder related to cbs log.
I was curious and found file:///C:/Windows/SystemApps/Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe/AppxManifest.xml

Thing is <Description>Microsoft Windows App Runtime CBS (5001.221.1556.0 x64)</Description>
Wasn't helping at all about package i would have to check, I knew it was windows appruntime package, there are many version available.

On the page where you download app runtime sdk, there is a removal section with warning about appruntime uninstalling that could lead to softwares not running.

Interesting command:
# For 1.0 and 1.0 Preview releases
get-appxpackage *appruntime*

I have temporary set user scope in powershell to unrestricted to run this script, and it listed all versions of appruntime.
In fact the 5001.221.1556.0 x64 version pointed to manifest is set to:
NonRemovable : True
And signature Kind : System it would be logical to think it is critical to windows operations, to keep this appruntime version.
I was thinking a repair would be possible, and i should download the sdk version corresponding to 50001.221.1556.0 x64 but it's nowhere to be found compared to other entrys of appruntime listed by get-appxpackage *runtime*

If i extrapolate, and let my imagination run: that would confirm it's a windows system file deployed from a windows image, / windows install, it was not a version that would come from microsoft store SignatureKind : store instead it's System
Now if i continue to push my mind into a fantasy land lol the fix would be to wait for a windows update, to update hash in component store, and/ or systemapps folder
But i'm not an advanced user, and i can't assume i foudn the error of this missmatch, it could be anything else.

At last i'm happy to correlate this folder to a appruntime versioning.
It's another step to find maybe a fix later :)

I like to investigate, it does remind me the good old time on a linux laptop.


Name : Microsoft.WindowsAppRuntime.CBS
Publisher : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture : X64
ResourceId :
Version : 5001.221.1556.0
PackageFullName : Microsoft.WindowsAppRuntime.CBS_5001.221.1556.0_x64__8wekyb3d8bbwe
InstallLocation : C:\Windows\SystemApps\Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe
IsFramework : True
PackageFamilyName : Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe
PublisherId : 8wekyb3d8bbwe
IsResourcePackage : False
IsBundle : False
IsDevelopmentMode : False
NonRemovable : True
IsPartiallyStaged : False
SignatureKind : System
Status : Ok
 
Last edited:
Archived Release Notes for the WebView2 SDK - Microsoft Edge Developer documentation

NuGet\Install-Package Microsoft.Web.WebView2 -Version 1.0.2210.55 correspond to the release not of the corrupted hash dll version.
SFC give the hash of the non corrupted dll that should be found somewhere into the component store.

looking at every Microsoft.Web.WebView2.Core.dll from a windows search and noting each hash, i would be able to find the right dll version then look agaub at webview2 release-notes, and download this specific version from the nuget link ?

Maybe i would find this dll from an updated iso from uup dump, i will download it again and check, but previously when i checked, the Microsoft.Web.WebView2 version in the iso was 1.0.2210.55 for systemsapps folder
note to myself lol I'm wondering if it's not a clue that solution would be to wait for a windows update.
 
I found out the right hash expected by sfc for the dll it does correspond to dll version 1.0.2535.41 that is an updated version: NuGet\Install-Package Microsoft.Web.WebView2 -Version 1.0.2535.41 hash a46788e94463899b6799304178a634643b20949cc7d378938db8abce8f69d17e
The one in system apps is 1.0.2210.55 hash 50a5c14fd4da7116a2072d12cb94c258354d0237979d5d5afa979be740d118f5

I should not manually move a copy of 1.0.2535.41 dll it won't fix anything, and dism would complain of source missing.
if i do it dism and sfc run a few time, the expected hash, would point to a46788e94463899b6799304178a634643b20949cc7d378938db8abce8f69d17e expecting 50a5c14fd4da7116a2072d12cb94c258354d0237979d5d5afa979be740d118f5
It would require to fix the winsxs again by re imaging it with a uup dump iso updated, of in place upgrade.

I did this error one time, i won't do it again.

My best guest is trying the nuget package 1.0.2535.41 install but i hope it won't do bad things.

Wait i'm not sure how to install it, powershell say i should import-module nuget, i will check on the web what it does mean
 
Ok i obtained a folder from nuget x86 command line i downloaded not sure what to do next ^^
Microsoft.Web.WebView2.1.0.2535.41 folder containing sub folders: lib runtimes tool build inside i find the 2535.41 dll with hash a46788e94463899b6799304178a634643b20949cc7d378938db8abce8f69d17e
In a native uap folder, it doesn't advance me, it's just a folder to integrate webview2 to a project i guess ? :)

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version 125.0.2535.41 or higher.

It does look like a versioning for microsoft edge webview 2, i currently have a updated version of webview2 edge runtime higher than 125.0.2535 i'm out of clue at the moment.
 
Last edited:
Oh i begin to understand what does mean hardlink as i can have an exemple with fsutil hardlink.
Not sure why sfc say:
Repairing file \??\C:\WINDOWS\SystemApps\Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe\\Microsoft.Web.WebView2.Core.dll from store
if hash 50a5c14fd4da7116a2072d12cb94c258354d0237979d5d5afa979be740d118f5 both on component store and Systemapps is the same.



hash a46788e94463899b6799304178a634643b20949cc7d378938db8abce8f69d17e
fsutil.exe hardlink list C:\Windows\WinSxS\amd64_microsoft-windows-webview2standalone_31bf3856ad364e35_10.0.26100.1876_none_1842c05de66ca15a\Microsoft.Web.WebView2.Core.dll
\Windows\WinSxS\amd64_microsoft-windows-webview2standalone_31bf3856ad364e35_10.0.26100.1876_none_1842c05de66ca15a\Microsoft.Web.WebView2.Core.dll
\Windows\ImmersiveControlPanel\Microsoft.Web.WebView2.Core.dll
\Windows\SystemApps\Microsoft.Windows.OOBENetworkCaptivePortal_cw5n1h2txyewy\Microsoft.Web.WebView2.Core.dll
\Windows\SystemApps\Microsoft.Windows.SecureAssessmentBrowser_cw5n1h2txyewy\Microsoft.Web.WebView2.Core.dll
\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\Microsoft.Web.WebView2.Core.dll
\Windows\SystemApps\Shared\WebView2SDK\Microsoft.Web.WebView2.Core.dll
\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\Microsoft.Web.WebView2.Core.dll


hash 50a5c14fd4da7116a2072d12cb94c258354d0237979d5d5afa979be740d118f5
C:\Windows\System32>fsutil.exe hardlink list C:\Windows\WinSxS\amd64_winappsdk-cbs_31bf3856ad364e35_10.0.26100.1876_none_6087edf2a421de07\Microsoft.Web.WebView2.Core.dll
\Windows\SystemApps\Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe\Microsoft.Web.WebView2.Core.dll
\Windows\WinSxS\amd64_winappsdk-cbs_31bf3856ad364e35_10.0.26100.1876_none_6087edf2a421de07\Microsoft.Web.WebView2.Core.dll
 
LOL more someone explore how things work, more things go deeper.

I thought i understood hardlink but i was wrong.
I had to read multiple time websites explaining hardlink, then it does explain inodes, and how deletion really work.

Manifest folder from winsxs, if it was possible to read the compressed files there, would it deliver more informations about expected hash, file version and so on ?
There was a blog entry on microsoft where SFC was explained in detail, i can't find it.
 
Hello,


5043178.csv file showing all updated files from re release of KB5043178.
It's possible 1.0.2535.41 will be updated to 1.0.2592.51
On a microsoft forum, a french user had a sfc repair loop with previous KB5043178

Geting back to a backup no sfc loop.

I will reboot my computer as the update just downloaded, and see if there are change.
In any case, it's a release preview of windows 11.
And things like this may happen, reporting to microsoft hub is the right thing to do.
I have found on sysnative multiple faq / guides, about how fixing things with windows update work.
Pretty interesting.

I will not risk to fix manually those dlls, as the folders where the hard link points too, are critical system pannels as an exemple.
If i'm not wrong, puting the wrong file, i would not be able anymore to click on settings pannel where you are able to update windows, windows update repair and so on.

I'm really happy i learned certain things, still even if i reread informations from sysnative, or data found on the web, i'm at a point where it's pretty difficult to understand advanced knowledge, till re reading 100 time the same guide :)

Here are some webview2 files updated september 28.
I'm going to reboot now :)

including
​
Microsoft.Web.WebView2.Core.dll​
1.0.2592.51​
28-Sep-2024​
17:49​
Microsoft.Web.WebView2.WinForms.dll​
1.0.2592.51​
28-Sep-2024​
17:49​
Microsoft.Web.WebView2.Wpf.dll​
1.0.2592.51​
28-Sep-2024​
17:49​
​
​
​
 
files went back to 1.0.2535.41 webview version. no trace in winsxs about 1.0.2592.51 just .41 and .55 present in winsxs
I'm curious about dll present in the kb csv, where they put those files.

Just typing KB5043178 and sfc on a web search engine
I'm not alone, ok it was not definitively me that have done something bad with windows by installing an older iso of windows 11 release preview.

WHat happend, is i did the repair in place upgrade from old iso, the day KB5043178 did appear.
I didn't use sfc and dism after installing KB5043178 but after inplace upgrade iso install.

Now i understand it's related to a specific KB at some point.
I have a full stress panic relief.
From now i will sleep better :)

On another forum
They say it happend since dev channel release and propagated to Release preview release lol
Problem reported to microsoft team by multiple users
 
Last edited:
Windows cleanup but with 8.xx Gb file still showing bug appeared to some users at the same time.
It begin to be interesting, i thought as well this bug still present on my system was due to cleanup of old windows that went wrong at some point, even if all files was removed, and dism refreshed.
 
Marking this message as resolved, as it' s in the hand of microsoft team, it has already been reported.
It's up to them to fix it before october 8 release ( kidding )
 
Hello

24H2 is available on main channel.
As insider program didn't opt out my account, i used a tool to reset to main channel. And disable insider features from microsoft insider site.
I had to enable again with help of regedit, a tweak to be able to run with tpm 1.2 and a 4670k.
(i will buy some components later)

Then repaired inplace windows with help of official iso 24h2.

As i have read on another forum, it's not fixed yet.
Still getting errors.

This time i was able to run componentsscanner tool it did found hive missmatch.
I then used a guide to back up all hives with reg back up tool, then loaded one by one each hives in multiple folders, past it to SequenceNumberCHecker, it sayd hive been repaired for every rush backup, but no missmatch error.

I' m wondering if doing an inplace upgrade with public realease iso of 24h2 went wrong ?

Off course COmponents Scaners is meant to not run with insider releases, so i could try it with normal 24h2 install.
Still i hope the rush missmatch is not a fatal error.

I will try before posting componentscanner and sfc fix zip + cbs folder compressed.
To use windows update repair function.

Dism /Online /Cleanup-Image /RestoreHealth and Scanhealth result is ok: no component store damage.
Aucun endommagement du magasin de composants n’a été détecté.
L’opération a réussi.
 
I found out windows update repair, does integrate if i'm not wrong all recent patch, cbs log, contain less errors, especially annoying 0x xxxxxxxx one
The new microsoft official iso, even if it may integrate some kb doing a download, still not the most recent ones i guess.
Did it lead to some errors shown in cbs log, as windows was downgraded to a lesser version ?

Anyway UUP Dump to do an offline dism imaging in case of source missing error, work fine.
And windows update repair is a nice addition.
 
You must log in or register to reply here.
Back
Top