Microsoft's September 18 Windows Insider release spreads new Windows 11 preview builds across four testing branches, with a redesigned accessibility mouse indicator as the clearest user-facing experiment. The releases are Build 26220.9492 for Beta, Build 26340.9502 for Experimental, Build 28120.3032 for Experimental on 26H1, and Build 29671.1000 for Future Platforms.
These are Insider Preview builds, not a general Windows update. Microsoft uses the Insider channels to test features with different groups before deciding whether, when or in what form they should reach normal Windows installations.
The mouse indicator can stay visible until Escape
In the Experimental channel, Microsoft is testing a new animation for the accessibility Mouse indicator. More importantly, it adds an option to keep the indicator active until the user presses Escape.
That can matter for presentations, demonstrations and accessibility use cases where a temporary highlight disappears too quickly. The change lives in accessibility settings, and Microsoft labels it as an Experimental-channel feature, so people on stable Windows 11 should not read the announcement as a promise that the same control is already available to them.
The September 18 post is also a good example of how fragmented Insider testing can look. Four build numbers were announced together because Microsoft is simultaneously maintaining Beta, Experimental and more specialized branches. A feature appearing in one of those branches does not automatically exist in all the others.
The branch matters more than the build number alone
A week earlier, Microsoft shipped another group of Insider builds with different experiments, including faster indexer-based File Explorer search from This PC in the Experimental channel. That September 11 release also covered Beta, Experimental, 26H1 and Future Platforms branches.
The pattern is useful context for anyone following Windows features from preview headlines. A build number identifies a particular test state, but the channel tells you more about how close that code is to ordinary users. Experimental features can change, disappear or move between branches as Microsoft gathers feedback.
For most Windows users, there is nothing to install from this story. Insider builds are for people who deliberately opt into preview software and accept the extra instability that can come with it. If the persistent mouse indicator solves a real problem for you, the safer move on a production PC is to watch for Microsoft to promote the feature rather than joining a preview channel solely to get it.
What changed on September 18 is still worth tracking: Microsoft is refining a small accessibility control while continuing to run several Windows development tracks in parallel. The practical lesson is to read Insider announcements with their channel labels attached, because "Windows is testing this" and "Windows has this" are not the same claim.
The September 18 release does not erase the builds shipped the week before. Insider machines can move through a sequence of previews as Microsoft iterates, and some features are enabled gradually or only for subsets of testers. That makes screenshots and advice tied to one Insider build less durable than documentation for a stable Windows release.
Microsoft's September 11 post illustrates that churn: it listed six preview builds, including a Release Preview build for 26H1, and highlighted different experiments from the September 18 set. Following the channel history helps separate a one-week experiment from a feature that is moving closer to broad release.
Reporting notes