Mouse freeze on surface book 2 after the most recent firmware UEFI version 389.2268.769.0 update!!! especially when power adapter plugged in

I too have this issue when having the slider to best performance that the mouse freezes. 

Surface book 2  13.5"  GTX1050, 16GB ram

1809

Windows 10 pro

Surface UEFI 389.2370.769

Hi,

We do understand where you're coming and we see your point in wanting to revert back to a previous firmware version.  Have you tried running a System Restore on your Surface device?  If not, you may also try to  Reset Your Surface to ensure that you are able to revert back, deleting all the drivers and updates that took place.

If none of these works, then you may need to do a fresh installation and create a recovery drivefor your Surface device.

Should you have any further inquiries, please do not hesitate to reply back to this thread so we could get back to you.

John,

I have this same issue, I spent a couple of hours today online with Jonathan, a Surface Book tech at microsoft.  We went through a lot of trial and error with no solutions.  We were going to contact Logitech together when we got disconnected.  I have yet to hear back from him today, but he could be talking to logitech on his own.  We really didnt accomplish anything other than any old dell/microsoft basic mouse works, but a Logitech G502, we tested 3 different ones, does not.  

We need someone who has the ability to confirm you guys are looking into this issue.  It makes my 6 day old $3200 laptop not that great of a purchase.

Thanks

Will

Ho come on.

Stop with the crappy automatic response and upgrade this issue => it's not that hard to test, plug any USB mouse, plug the SB2 and rise the battery settings and VOILA.

I can 100% confirm that it was the firmware update, and I reported this issue almost day 1 after the upgrade the your support.

Hello,

I have the same problem. I using SB2 with all the latest updates, an updated dock, Microsoft USB keyboard and mouse with Microsoft Mouse and Keyboard Center. I tried uninstalling and reinstalling the drivers and no difference. The keyboard is also affected sometimes I'll be typing and I'll get something like "                          " or "ffffffffffffffffffffffffffff" show up right after the lag spike.

Is there a solution for this yet?

So I had been using my SB2 on 1709 undocked for several months because I was traveling and had a bad experience trying to upgrade to 1803 (thankfully was able to revert to a restore point). My touch pad started freezing especially when two finger scrolling in August. Now I am done traveling, updated to 1803 and the latest firmware, and its unbelievable how Microsoft can make things worse and worse with each update. I too am having issues when docked on my external keyboard having a lag/spike and getting a "ffffffffffffffffffffff" and my computer seems slow and laggy a lot of the time and fan running full blast. These weren't issues before I updated and I wish I hadn't. I have been watching my PC performance and am never really using more than half the RAM/CPU. I don't know why it gets laggy then. Even after closing all open applications, the SB2 was still laggy and fan running full speed. A reboot solved the issue for now. Good grief Microsoft. 

This is hilarious... so I had another machine running 1809 that was getting BSOD coming out of hibernation. Never saw that issue before. Now on my SB2 that I upgraded to 1803 its getting a BSOD coming out of hibernation now as well. This was NEVER an issue on 1709 before upgrading to 1803 / the updated SB2 firmware pack. WTF Microsoft. Introduce more and more bugs instead of fix existing. I am guessing its a 1803 and later issue because the other machine is a different make/model so firmware wouldn't be common.

Multiple people are experiencing this problem with freshly installed/up-to-date/brand new Surface books. Also my colleague uses a standard mouse and I use a gaming mouse (which has all the latest drivers etc.). If you folks read through this thread you can see we have tried all the 'standard reply'-stuff already and more. We even have a good suspicion of where the problem might be by eliminating many factors.

The hardest part in forums like these is convincing 'support' that it's not a standard issue thing and probably something beyond their reach. That's where threads like these usually die because support will not acknowledge that and take further action.