Save function not working in Chrome after Windows Preview Update and Chrome Update

Question

Save function not working in Chrome after Windows Preview Update and Chrome Update

Scott Mauney 0

Subject: Windows 11 / Google Chrome File System Access API — Save Works Once, Then Fails Silently

Date: November 6, 2026

I am reporting a reproducible file-saving problem involving Google Chrome on Windows 11 that appeared following substantial Chrome and Windows Preview updates.

Most importantly, I have independently reproduced the same failure using Google's own Chrome Labs File System Access API demonstration:

https://googlechromelabs.github.io/text-editor/

This establishes that our custom application is not required to reproduce the problem.

1. Description of the problem

Chrome's File System Access API behaves inconsistently when saving files to the Windows file system.

Observed behaviour:

Chrome can initially create and save a new file in the main OneDrive Documents directory.

Subsequent saves frequently fail silently.

Saving into subdirectories fails, including a newly created test folder outside OneDrive.

Overwriting an existing file fails.

Subsequent Save As dialogs repeatedly return to the main OneDrive Documents directory, even after another destination has been selected.

The Save As dialog closes normally, but the file is not created or updated.

No application success confirmation appears when the operation fails.

Occasionally a save succeeds again, but the failure recurs on subsequent attempts.

The behaviour resembles a file-handle, file-writing, or directory-permission state problem.

2. Independent reproduction

The same one-and-done saving failure occurs in the Chrome Labs Text Editor, which demonstrates the File System Access API.

https://googlechromelabs.github.io/text-editor/

A successful initial save is followed by failures during subsequent saves, overwrites, or attempts to select another destination.

This reproduces the failure without using any of our application code.

3. Browser and platform comparison

Google Chrome on Windows 11: Fails as described.

Microsoft Edge on the same Windows 11 computer: Saves and overwrites files successfully.

Google Chrome on macOS: Saves successfully both before and after its recent Chrome update.

Chrome Incognito on Windows: Same failure.

Local and AWS-hosted versions of our web application: Same failure in Windows Chrome.

4. Troubleshooting already performed

Updated Chrome and Windows.

Cleared Chrome's cached files.

Restarted Windows.

Tested Incognito mode.

Checked Chrome File Editing permissions.

Checked Windows Security and Malwarebytes for blocked operations.

Tested a newly created project with minimal data.

Tested saving to different directories.

Tested using Chrome Developer Tools.

None resolved the problem.

5. Recent system changes

The problem appeared after significant Google Chrome and Windows 11 Preview updates installed around November 5, 2026.

The timing suggests a possible browser/operating-system compatibility regression, but the responsible component has not been identified.

6. Technical investigation requested

Please investigate potential problems involving:

window.showSaveFilePicker()

FileSystemFileHandle.createWritable()

FileSystemWritableFileStream.write() and .close()

Windows file replacement and overwrite operations

File handle and directory access permissions

Interaction between Chrome's security sandbox and the Windows file system

File-dialog state or permission persistence after an initial successful save

Expected behaviour: Chrome should save new files, overwrite existing files, and write to user-selected directories consistently, as Microsoft Edge currently does on the same Windows computer.

Actual behaviour: Chrome intermittently saves once, then fails subsequent save operations without an actionable error.

Please advise whether this is a known regression and what diagnostic logs would help identify the failure.

Thank you.Subject: Windows 11 / Google Chrome File System Access API — Save Works Once, Then Fails Silently

Date: November 6, 2026

I am reporting a reproducible file-saving problem involving Google Chrome on Windows 11 that appeared following substantial Chrome and Windows Preview updates.

Most importantly, I have independently reproduced the same failure using Google's own Chrome Labs File System Access API demonstration:

https://googlechromelabs.github.io/text-editor/

This establishes that our custom application is not required to reproduce the problem.

1. Description of the problem

Chrome's File System Access API behaves inconsistently when saving files to the Windows file system.

Observed behaviour:

Chrome can initially create and save a new file in the main OneDrive Documents directory.

Subsequent saves frequently fail silently.

Saving into subdirectories fails, including a newly created test folder outside OneDrive.

Overwriting an existing file fails.

Subsequent Save As dialogs repeatedly return to the main OneDrive Documents directory, even after another destination has been selected.

The Save As dialog closes normally, but the file is not created or updated.

No application success confirmation appears when the operation fails.

Occasionally a save succeeds again, but the failure recurs on subsequent attempts.

The behaviour resembles a file-handle, file-writing, or directory-permission state problem.

2. Independent reproduction

The same one-and-done saving failure occurs in the Chrome Labs Text Editor, which demonstrates the File System Access API.

https://googlechromelabs.github.io/text-editor/

A successful initial save is followed by failures during subsequent saves, overwrites, or attempts to select another destination.

This reproduces the failure without using any of our application code.

3. Browser and platform comparison

Google Chrome on Windows 11: Fails as described.

Microsoft Edge on the same Windows 11 computer: Saves and overwrites files successfully.

Google Chrome on macOS: Saves successfully both before and after its recent Chrome update.

Chrome Incognito on Windows: Same failure.

Local and AWS-hosted versions of our web application: Same failure in Windows Chrome.

4. Troubleshooting already performed

Updated Chrome and Windows.

Cleared Chrome's cached files.

Restarted Windows.

Tested Incognito mode.

Checked Chrome File Editing permissions.

Checked Windows Security and Malwarebytes for blocked operations.

Tested a newly created project with minimal data.

Tested saving to different directories.

Tested using Chrome Developer Tools.

None resolved the problem.

5. Recent system changes

The problem appeared after significant Google Chrome and Windows 11 Preview updates installed around November 5, 2026.

The timing suggests a possible browser/operating-system compatibility regression, but the responsible component has not been identified.

6. Technical investigation requested

Please investigate potential problems involving:

window.showSaveFilePicker()

FileSystemFileHandle.createWritable()

FileSystemWritableFileStream.write() and .close()

Windows file replacement and overwrite operations

File handle and directory access permissions

Interaction between Chrome's security sandbox and the Windows file system

File-dialog state or permission persistence after an initial successful save

Expected behaviour: Chrome should save new files, overwrite existing files, and write to user-selected directories consistently, as Microsoft Edge currently does on the same Windows computer.

Actual behaviour: Chrome intermittently saves once, then fails subsequent save operations without an actionable error.

Please advise whether this is a known regression and what diagnostic logs would help identify the failure.

Thank you.

0 comments

Answer accepted by question author

Neil D 34,660 Volunteer Moderator

As it is a windows preview and an optional update you can uninstall it and wait for the full release next week. You should post the info you have included here in the Feedback Hub in windows for the dev team.

0 comments

4 additional answers

Your answer

Answer 1

Onyx Is here 5,535 Independent Advisor

I do understand what you're saying but as this is a preview build not even support would have information enough to help which is why I mentioned filing it as a bug via both systems.

0 comments

Answer 2

No matching known issue is currently documented on the Windows 11 26H2 release-health page, so capture a minimal Chrome API trace and a Process Monitor file-system trace, then use removal of the recent Preview update only as a controlled isolation test.^1^

Your results already rule out several application-level explanations: the failure reproduces in Chrome Labs, in normal and Incognito Chrome, across local and hosted applications, while Edge succeeds on the same Windows installation. This does not establish whether Chrome or the Chrome/Windows interaction is responsible, but it makes further cache, application-code, destination-folder, and site-permission troubleshooting low value.

Capture the exact failing API stage

Chrome documents the expected sequence as obtaining a handle from showSaveFilePicker(), calling createWritable(), writing, and closing the stream.^2^ Instrument each awaited operation separately so a rejected promise cannot appear as a silent failure:

async function saveText(text, existingHandle) {
  try {
    const handle = existingHandle ??
      await window.showSaveFilePicker({ suggestedName: "test.txt" });
    console.log("picker succeeded", handle.name);

    const stream = await handle.createWritable();
    console.log("createWritable succeeded");

    await stream.write(text);
    console.log("write succeeded");

    await stream.close();
    console.log("close succeeded");
    return handle;
  } catch (error) {
    console.error("save failed", {
      name: error?.name,
      message: error?.message,
      stack: error?.stack
    });
    throw error;
  }
}

Run a controlled sequence:

Create test.txt.
Reuse the returned handle and overwrite it.
Request a new handle with Save As and select another folder.
Preserve the Console output after each attempt.

Record whether failure occurs at the picker, createWritable(), write(), or close(). A writable operation requires the parent directory to exist; replacing an existing file also requires that file to be writable and deletable. Otherwise, createWritable() is expected to throw a DOM exception rather than fail silently.^3^

Also save:

chrome://version output, including the exact Chrome version and profile path.
Windows version and OS build from Settings → System → About.
The exact Preview-update KB from Settings → Windows Update → Update history.
A screen recording showing the first successful save and immediately following failure.

Capture Windows file operations with Process Monitor

Process Monitor records real-time file-system activity and preserves operation results, process details, and thread stacks.^4^

Download and extract Process Monitor.
Run the correct executable as administrator.
Reset existing filters, then add:
- Process Name is chrome.exe → Include
- Path contains test.txt → Include
Start capture with Ctrl+E.
Perform one successful save and one failed overwrite.
Stop capture with Ctrl+E, then save it as a native .PML file.

Inspect the failed interval for results such as:

ACCESS DENIED
SHARING VIOLATION
NAME NOT FOUND
failed rename, delete, create, or replacement operations

A SHARING VIOLATION, for example, indicates that an incompatible open handle prevented the requested access.^5^ Compare the failing Chrome trace with a successful Edge save to the same test path.

Isolate the Preview update

After preserving the evidence, remove only the Preview update installed immediately before the problem:

Open Settings → Windows Update → Update history.
Under Related settings, select Uninstall updates.
Select the identified Preview update and choose Uninstall.
Restart and repeat the same Chrome Labs sequence.

Some updates cannot be removed. Uninstalling an update can reintroduce security or reliability risks, so use this only as a short isolation test and reinstall it afterward.^6^

Interpret the result narrowly:

Chrome works after removal: strong evidence of an interaction with that Windows build; include both OS builds in the report.
Chrome still fails: the Windows Preview update is not isolated as the trigger; prioritize a Chromium report containing the Chrome version, API-stage exception, and paired Chrome/Edge .PML traces.

Submit diagnostic reports

For Windows, press Windows+F, create a problem report, select Recreate my problem, start recording, reproduce the first successful save and failed second save, then stop recording. Attach the console output and, if size permits, the compressed Process Monitor trace. Feedback Hub can include screenshots, attached files, and locally saved diagnostic data.^7^

Submit a corresponding Chromium bug with:

Exact Chrome and Windows builds
The Chrome Labs reproduction steps
Edge-on-the-same-machine comparison
API-stage error details
Preview-update removal result
Process Monitor result names and affected paths

At present, the available public Windows issue list does not confirm this exact symptom as a known Microsoft regression; the collected evidence is what will distinguish a Chrome promise-handling defect, a Windows file-operation denial, or a build-specific interoperability regression.

References

Answer 3

Scott Mauney 0

Our application, MREAnalytics.com, is hosted on AWS and uses the File System Access API to save project files.

The application works correctly using Microsoft Edge on Windows 11, Chrome on macOS, Chrome on a Samsung S22, Chrome on an iPhone 13, and our Kindle. Safari on macOS can also save and reload projects, although it handles downloaded filenames differently.

The failure is isolated to Google Chrome on our Windows 11 computer.

Most importantly, we reproduced the identical saving failure using Google's own Chrome Labs Text Editor, completely independently of our application.

Chrome can initially save a file but subsequently fails to save into other directories or overwrite existing files. The Save As dialog closes normally without completing the operation.

We have already reported these findings to Google and Microsoft.

Thank you for reviewing the issue. We hope this information helps the Chromium engineering team identify the underlying problem.

Neil D 34,660 Reputation points Volunteer Moderator

2026-11-06T22:17:02.66+00:00

Posting here won't reach any engineering team. This is a user forum and using the Feedback Hub is the way to present this to Microsoft.
Scott Mauney 0 Reputation points

2026-11-06T22:41:54.15+00:00

Thank you, just sent to FH.

Answer 4

Onyx Is here 5,535 Independent Advisor

Sorry to hear you're having trouble.

As this seems to be issues with preview builds my recommendation would be to file the issue as a bug report via the Windows Preview Build Hub and Chrome Preview Hub.

0 comments