Hi Ahmed,
As a Known Issue there is no
workaround.
File the issue in the Feedback Hub
using WIN+F and wait for the next
build and hopefully a fix.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am experiencing persistent mouse cursor flickering on Windows 11 Pro Insider Preview Build 29648.1000 in the Experimental (Future Platforms) channel.
Windows 11 Pro Insider Preview
Build 29648.1000
Experimental (Future Platforms) channel
Intel Core i7-8650U
Intel UHD Graphics 620
NVIDIA GeForce MX130
8 GB RAM
Fujitsu M520 external mouse, plus the laptop's built-in touchpad
The mouse cursor repeatedly disappears and reappears, both while stationary and while moving.
The issue occurs:
with the Fujitsu M520 connected;
with the external mouse disconnected;
while using only the built-in touchpad;
through different USB ports;
with the default Windows cursor;
with different cursor sizes and schemes.
This makes a defective external mouse or individual USB port unlikely.
Microsoft's release notes for Build 29648.1000 list a known issue in which the mouse cursor can enter a state where it repeatedly blinks for some Windows Insiders. My symptoms appear to closely match that acknowledged issue.
As of September 6, 2026, Build 29648.1000 is also still the latest build listed for the Experimental (Future Platforms) channel in Microsoft Flight Hub.
Microsoft Basic Display Adapter
I reproduced the flickering while Microsoft Basic Display Adapter was active and the Intel graphics driver was confirmed inactive. The cursor still flickered.
This suggests that the Intel graphics driver alone is unlikely to explain the issue.
Ctrl+Alt+Delete secure desktop
The cursor remains stable on the Ctrl+Alt+Delete secure desktop, while it flickers on the normal Windows desktop.
Restarting Explorer
Restarting Windows Explorer temporarily stops the flickering, but it returns. In one test, the cursor remained stable for approximately 12 minutes.
Sign out/sign in
Signing out and signing back in also temporarily stops the problem, but the flickering eventually returns.
Fresh Windows user account
I created a new standard local account named CursorTest.
When my original account was flickering, CursorTest remained stable for approximately 5 to 10 minutes. Returning to my original account also made the original account temporarily stable.
I repeated the test and observed the same behavior.
Because merely switching sessions temporarily restored stability to the original account, this does not appear to prove that my original user profile is corrupted.
Win+L test
This produced the clearest reproducible pattern:
The cursor is flickering.
I press Win+L.
I unlock the same Windows account.
The cursor immediately becomes stable.
After a short period of normal use, the flickering returns.
Therefore, Win+L is only a temporary workaround.
I have also tested or investigated:
different cursor schemes and sizes;
different USB ports;
touchpad-only operation;
Intel graphics package cleanup;
Intel display-power settings;
disabling several third-party services;
rebooting Windows.
None has provided a permanent solution.
Is there a Microsoft-supported permanent workaround or repair for the acknowledged repeated cursor-blinking problem on Windows 11 Insider Build 29648.1000 while waiting for the next Experimental (Future Platforms) flight?
I am particularly interested in a solution or diagnostic procedure that addresses the underlying Windows issue rather than another temporary session reset, since restarting Explorer, signing out, switching users, and Win+L all provide only temporary relief.
I would prefer to avoid resetting or reinstalling Windows unless there is evidence that doing so is relevant to this acknowledged Insider-build issue.I am experiencing persistent mouse cursor flickering on Windows 11 Pro Insider Preview Build 29648.1000 in the Experimental (Future Platforms) channel.
Hi Ahmed,
As a Known Issue there is no
workaround.
File the issue in the Feedback Hub
using WIN+F and wait for the next
build and hopefully a fix.