Updated April 26, 2024
Thank you for reporting the issue. A fix is now available through Windows Update. For more information about updates for your Surface device, please see Surface Pro 9 update history.
Surface Pro 9 lagging after sleep but only until power supply is conected
![](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)
Anonymous
Hi,
I have a MS Surface Pro 9 and after waking up from sleep the screen is always sluggish (i.e. the mouse moves aren't fluid). However, as soon as I plug the power supply the lag goes away and is away even when I unplug it.
I've done a diagnostics but couldn't find anything.
Any ideas what could be the root of this problem? I don't have anything ressources intensive that is running.
Thanks,
ioan
Surface | Surface Pro | Performance and maintenance
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.
Answer accepted by question author
Anonymous
62 additional answers
Sort by: Newest
-
Anonymous
2024-02-29T13:06:21+00:00 I have the same problem too!!!!! Started around 2-3 weeks ago. My device has auto updates on. Judging from the amount of responses I highly suspect it’s from one of the recent updates. My device is less than a year old. Nothing heavy, I literally only run Chrome and watch Youtube videos.
-
Anonymous
2024-02-28T16:48:55+00:00 I agree! Mine also started weeks ago!
-
Anonymous
2024-02-25T20:40:59+00:00 100% agree!
Microsoft, what are you doing about this? Your last update reduced the performance of my Pro 9 and I'm having to use a work around to get the device to work right. Please fix this!
-
Anonymous
2024-02-25T18:42:22+00:00 I'm aware of all that. I read the whole thread. My point of commenting is to show that it isn't an isolated incident, and that the Windows update clearly introduced an issue that should still be acknowledged and addressed officially.