What is this?
A PowerShell workaround for a Windows 11 bug: custom mouse cursor themes are installed correctly, but the screen stays stuck on the classic Windows Aero cursors. It reloads all 14 cursor roles into the live session and can keep re-applying them from a background process.
A PowerShell workaround for a Windows 11 bug: custom mouse cursor themes are installed correctly, but the screen stays stuck on the classic Windows Aero cursors. It reloads all 14 cursor roles into the live session and can keep re-applying them from a background process.How do I apply the fix?Select your scheme in Windows Settings or main.cpl, then double-click Apply-CurrentCursorScheme.cmd (or run it from PowerShell) - cursors switch immediately. Run it from your normal account: 'Run as administrator' breaks the per-user registry read.
Select your scheme in Windows Settings or main.cpl, then double-click Apply-CurrentCursorScheme.cmd (or run it from PowerShell) - cursors switch immediately. Run it from your normal account: 'Run as administrator' breaks the per-user registry read.Do I need admin rights or anything else installed?No admin rights and nothing to install - it is plain PowerShell calling Windows' own SetSystemCursor and LoadCursorFromFileW APIs. The script never writes the registry and never downloads anything; it only reloads cursors into your current session.
No admin rights and nothing to install - it is plain PowerShell calling Windows' own SetSystemCursor and LoadCursorFromFileW APIs. The script never writes the registry and never downloads anything; it only reloads cursors into your current session.Are there cursors it can't fix?NWPen, Person and Pin have no SetSystemCursor slots and cannot be fixed. Roles not set in your scheme are skipped, and if a cursor file fails to load the rest still apply but the script exits with an error listing the failures.
NWPen, Person and Pin have no SetSystemCursor slots and cannot be fixed. Roles not set in your scheme are skipped, and if a cursor file fails to load the rest still apply but the script exits with an error listing the failures.Which Windows versions does it work on?Windows only. The author reproduced the bug on Windows 11 25H2 (Insider Beta, build 26220.9223) with third-party .cur packs like Jepri Creations; other builds may be affected but are unverified.
Windows only. The author reproduced the bug on Windows 11 25H2 (Insider Beta, build 26220.9223) with third-party .cur packs like Jepri Creations; other builds may be affected but are unverified.Why do my cursors keep reverting even after I fix them?It is not your setup: Windows occasionally re-runs the step that loads the registry scheme into the live cursor slots, resetting them to the classic style mid-session. The author found no sign Microsoft has publicly acknowledged the bug and suspects a regression around cursor initialization in Insider builds, accessibility pointer settings, or legacy control panel scheme compatibility.
It is not your setup: Windows occasionally re-runs the step that loads the registry scheme into the live cursor slots, resetting them to the classic style mid-session. The author found no sign Microsoft has publicly acknowledged the bug and suspects a regression around cursor initialization in Insider builds, accessibility pointer settings, or legacy control panel scheme compatibility.What does the background worker do once registered?It applies all cursor roles about 3 seconds after login and again roughly 25 seconds later, covering Windows' two post-login cursor initializations, then keeps re-reading the registry and re-applying every 10 seconds (adjustable via -WatchIntervalSeconds). A named mutex blocks duplicate instances, and it writes CursorSchemeStartup.log in your %TEMP% folder.
It applies all cursor roles about 3 seconds after login and again roughly 25 seconds later, covering Windows' two post-login cursor initializations, then keeps re-reading the registry and re-applying every 10 seconds (adjustable via -WatchIntervalSeconds). A named mutex blocks duplicate instances, and it writes CursorSchemeStartup.log in your %TEMP% folder.How do I get the default Windows cursors back?Open main.cpl and apply the Windows default scheme - with the startup entry registered, the resident worker follows the switch automatically. Logging off and back on also restores defaults, as long as the silent startup entry has been removed.
Open main.cpl and apply the Windows default scheme - with the startup entry registered, the resident worker follows the switch automatically. Logging off and back on also restores defaults, as long as the silent startup entry has been removed.What are similar projects?tiny11builder, RemoveWindowsAI, Winhance, winutil, Win11Debloat, MediaCreationTool.bat, Windows10Debloater, Scoop
tiny11builder, RemoveWindowsAI, Winhance, winutil, Win11Debloat, MediaCreationTool.bat, Windows10Debloater, ScoopWhich topics is it in?troubleshooting, mouse, registry-tweaks, script, windows-11, powershell, themes, accessibility, cursor, customization, utility, automation
troubleshooting, mouse, registry-tweaks, script, windows-11, powershell, themes, accessibility, cursor, customization, utility, automation