This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello everyone, I am experiencing a strange issue with my Windows 11 (version 24H2) laptop. Every time I boot up my HP Spectre x360 16-inch 2-in-1 laptop, the mouse cursor appears significantly larger than normal.
I found that resetting the graphics card temporarily resolves the issue, but the problem reoccurs with each reboot. changing the screen resolution also fixed it, any solution? My laptop is equipped with Intel Iris Xe Graphics and has 8GB of RAM.
Any advice would be greatly appreciated! Thank you.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I fear you will, when I did it I had no issues for a while, as the windows and driver updates continued after the main update, it eventually came back. I never could track down exactly which update it was, I've got a feeling it was a feature update which was non optional. Enjoy it while it lasts!
Oh, for me upgrading to 24h2 after factory 22h2 installation still had no issues(22h2 -> 23h2 -> 24h2 via windows update).
I have restored the factory 22h2 myself, and indeed the problem is resolved. Unfortunately the 24h2 update is mandatory, and it will force install it sooner or later, you don't get to enjoy it sadly for very long..you can disable windows updates, but that's probably not a great idea in the long term.
Decided to clean install 24h2 today due to swapping ssd. To my dismay, the issue happened again after clean installation.
So I wiped the new drive, cloned the old drive and thankfully doesn't happen anymore.
So it seems like for me at least clean installation is not the solution but rather using device manufacturer's factory image (or maybe 22h2 installation, not entirely sure).
same for me on my surface pro11, ARM with all the other incompatibility issues.
