Repository navigation
Which Fixed Version licence terms govern WebView2 Runtime 152.0.4191.53 x64 from the pinned Microsoft CAB? #5732
Unanswered
jkasprzewski-oss
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello Microsoft WebView2 team,
I am preparing the distribution of VetBreeze, a Windows desktop application incorporating the Fixed Version WebView2 Runtime. I need to identify the applicable licence text, separately from verifying the binary's provenance.
The runtime is Microsoft.WebView2.FixedVersionRuntime.152.0.4191.53.x64.cab, downloaded directly from:
https://msedge.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/f8ecb2c5-f486-4df5-994f-1eec63f1de23/Microsoft.WebView2.FixedVersionRuntime.152.0.4191.53.x64.cab
Size: 371824512 bytes.
SHA-256: f8f200b57d6a7a71d380f777f5c0ea0f71f520048add21e15737121de9ba4f68.
Our preserved download record is dated 27 September 2026. Our captured build inventory matches the CAB's 548 files.
On the official WebView2 download page we preserved the full “MICROSOFT EDGE WEBVIEW2 RUNTIME (FIXED VERSION)” terms displayed while version 152.0.4191.62 was selected. The UTF-8 text copy has SHA-256 88914604f1280f6cff05c6067d65e3e147fed7860cbb204c68289448a0a72aca. This hash identifies our saved text copy, not a Microsoft-published document hash. The text contains no patch version; its introductory paragraph addresses new or additional terms accompanying updates. We have not located a preserved licence-page record for the exact .53 download.
Please identify the licence terms governing acquisition and redistribution of the above .53 CAB and clarify whether the full Fixed Version text displayed for .62 also applies to this .53 acquisition, or whether different/additional terms apply. Please provide the applicable full text or an official reference and its effective scope/date sufficient to document that conclusion. We can supply our exact preserved text for comparison; matching our text-file hash is not required if you provide an identifiable authoritative document.
We are not requesting permission to omit end-user/distributor requirements, a waiver of any licence clause, or a retroactive change of terms. We seek one authoritative clarification of the applicable licence text and its scope for the identified binary.
Kind regards,
Jacek Kasprzewski
VetBreeze publisher
All reactions