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.
Can anyone confirm if disabling SensorService(restart afterward) works or not? We all seem to be 2-in-1 devices presumably with rotation sensor, seems kind of plausible that this service is messing something up with fastboot.
It'd be good starting point for devs to take look at if it is not just isolated to my machine. Assuming one day they'll take notice that is.
You would need the exe highlighted in the instructions, it's probably easier to set it up manually, only takes a minute to do
It's definitely the dpi, , you can manually change the dpi to fix it when it happens. Restarting a service may have a side effect of reapplying the dpi the instructions I posted does the job for me and it doesn't happen anymore with it applied, I'll keep using it until they get their act together and fix it
I am aware that it's most likely related to DPI not being set right on fastboot. Setting scale to 175 then 200 will fix it yes. Automating it sounds nice. This workaround has been known since page 1 of this thread.
What I'm trying to do is determine whether SensorService is causing all this in the first place, so that when this problem gets acknowledged, said service could be looked into as a starting point(all the people I see having this problem is using 2-in-1 style device). It's not restarting of this service that fixes it, disabling it does - for me at least.
I think the Task Scheduler workaround is working and better. However, disabling the service may not have a significant impact on users who don't use it as a tablet. In my opinion, refreshing the DPI setting is a better approach than disabling the service altogether.
