Mouse Cursor Size Issue on Windows 11 (v24H2) - HP Spectre x360

Anonymous
2024-10-27T11:48:55+00:00

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.

Windows for home | Windows 11 | Display and graphics

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.

0 comments No comments

119 answers

Sort by: Oldest
  1. Anonymous
    2025-03-06T05:44:50+00:00

    After a month of freedom, the issue randomly popped back today. No idea what exactly caused it, only notable things I've done yesterday is fiddling with audio drivers and a failed windows update KB5052093 with code 0x80070306.

    Rolling back audio drivers now but I doubt this will do anything. :: and yes issue persists after audio driver rollback.

    ¯\_(ツ)_/¯

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-03-18T16:12:33+00:00

    I have this issue since a while, and I see here that this is not fixed even after all the mentioned steps... please do something about this. Yes it is only a small thing - it can be fixed temporarly using the mouse size settings... but I have to do this each time and each time I feel motivated to just finally switch to linux... On my secondary apple and linux devices I never have such issue, I allow myself to wonder why...

    Sorry for the rant, but this is how it is for me...

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-03-19T11:19:57+00:00

    Hello,

    Here with the information from INTEL received today regarding this issue :

    "Thank you for your patience. After conducting a thorough investigation and reviewing all available resources, we were unable to fully replicate the issue. Given that this problem occurs with different drivers (both OEM and Intel), we recommend reaching out to HP for a solution. Since OEM drivers are also affected, it seems to be an HP-specific issue, as they modify the Intel driver to suit their hardware.

    If a clean OS with OEM drivers is experiencing this issue, it is crucial for HP to address it. Their driver team can collaborate with Intel through the OEM channel to work on a resolution. I understand this may not be the answer you were hoping for, and I empathize with your situation. We've exhausted all possible steps and resources, and the most effective course of action now is to seek further assistance from HP."

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2025-03-19T13:21:20+00:00

    What a dead end. I seem to be the only one but I am having this problem on a Lenovo.

    Image

    Thought about opening my own ticket on Intel support but before that, tried steps Intel provided on your ticket like DDU'ing Intel driver and such and found that the problem persists even without any Intel driver installed(uninstalled via DDU).

    I'm pretty convinced this is problem on Microsoft's end. This forum seems to be just community driven, or we're just not getting attention from official reps.

    I might try feedback hub soon but am not too hopeful.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2025-03-19T16:39:39+00:00

    [Unfortunately the problem has reappeared! the updates did NOT fix the problem.

    Sorry for my old post:

    The problem seems to have been fixed on my OmniBook Ultra sometime in the last two weeks (2025-03-12 or 2025-03-10). I've had and "Quality Update" (2025-03 Cumulative Update for Windows Version 24H2 ... KB5053598) and a "Driver Update" (Intel 32.0.100.3717).

    Was this answer helpful?

    0 comments No comments