Windows 11 new update build 26300.9818 has a bug

This problem is not a reported problem in the KB5127936 October optional preview update, though those optional preview updates are basically beta versions of the next month's update and may contain bugs.

The best option may be to uninstall that optional preview update to test if that resolves the problem, if not, this is just a user to user forum, the best option is to open the Feedback Hub app and report this to the Windows Developers there so they can investigate this before the full November update is released.

Had this same issue as well. Using Vivetool did not work, as previously mentioned above. I eventually uninstalled the October 2026 preview update, which reverted back to the new loading circle.

Then I found this article on neowin.net while looking for an updated solution.

Microsoft rolls back a Windows 11 design change with latest build but says it's temporary

Under the Windows design section...

We are temporarily rolling back the solid (donut) spinners across some of the key Windows scenarios including Boot, Logon, Restart, Shutdown, and Update as we work on a bug. We expect to resume rolling it out soon.

No explanation as to what the bug is, but I haven't seen anything suspicious across several Windows 11 machines running the latest build. Hopefully this will be addressed by the time the October 2026 preview update is officially ready to be rolled out.

Fix: old “dotted ring” spinner came back after KB5127936 (Windows 11 build 26300.9818), without uninstalling the update

Problem After installing the preview update KB5127936 (build 26300.9818), the boot, sign-in, restart and shutdown screens show the old Windows 10-style dotted spinner again instead of the modern solid ring. Several people have reported the same thing.

Cause (what I found on my machine) The modern animation is controlled by the hidden feature flag ID 59728252. On my PC, a plain vivetool /enable did nothing. Querying the flag showed this :

vivetool /query /id:59728252

State    : Disabled (1)
Type     : Override (0)
Priority : Security (9)

/query only shows the override with the highest priority. A plain /enable is applied at the default User priority, which is lower than Security, so the Disabled override wins and nothing changes. I can’t say who set that override. It looks like this build disables the feature, whether on purpose or by mistake.

Fix :

1. Download ViVeTool (v0.3.4 or later) from the official GitHub repo and extract it.
2. Open Command Prompt as administrator and cd into the ViVeTool folder.
3. Run :

vivetool /enable /id:59728252 /priority:userpolicy

4. Restart your PC.
5. (Optional) Check with :

Undo :

vivetool /reset /id:59728252 /priority:userpolicy

Notes :

• This worked for me on build 26300.9818. I can’t promise it works on every PC or build.
• KB5127936 is an optional preview update, so bugs like this are possible. It’s worth reporting the issue through the Feedback Hub (Win + F) so Microsoft fixes it properly.
• ViVeTool toggles unreleased, experimental features, so use it at your own risk. If anything behaves strangely, run the undo command above.

I found a bug. Please fix it.

C:\Users\KATANA\Desktop\vivetool>vivetool /query /id:59728252

ViVeTool v0.3.4 - Windows feature configuration tool

[59728252]

Priority : Security (9)

State : Disabled (1)

Type : Override (0)

C:\Users\KATANA\Desktop\vivetool>

As a preview I would suggest you uninstall it and report the problem via the Feedback Hub in windows.

Previews are optional and do create problems for some users.