MicrosoftEdge / MicrosoftEdge/WebView2Feedback

Supported preservation-safe reuse of a 152.0.4191.66 user data folder with Fixed Runtime 152.0.4191.62 x64

Open
#5,698 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

We are preparing an isolated Windows x64 desktop application that must preserve an existing WebView2 user data folder and its persistent application state.

The user data folder's recorded Last Version is 152.0.4191.66. The newest Fixed Version x64 CAB offered on the official WebView2 download page at 2026-09-08 16:28 UTC was 152.0.4191.62. We have not opened the preserved profile with the older runtime, so we are not claiming an observed incompatibility.

Can Microsoft confirm whether this exact .66-to-.62 transition is supported without resetting the user data folder or losing persistent storage, cookies, settings, or other profile state? We need profile/storage compatibility guidance, separately from SDK/API compatibility or runtime-selection policy.

If this transition is not supported, is there an official Fixed Version x64 package at 152.0.4191.66 or newer, or a documented preservation-safe migration route?

No profile files, logs, account details, local paths, or private application data are attached.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository files, tests, or code entry points are mentioned. Start by checking official WebView2 Fixed Version runtime and user-data-folder compatibility guidance for the stated .66-to-.62 transition; done means a maintainer provides an authoritative compatibility answer or identifies a supported runtime or migration path.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.