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)
Hi.
The last month, my surface keyboard (External bluetooth version), keeps loosing connection to my surface book 2, if i have been away from the office, or my Surface book 2 has been in standby..... (I have tried to change the batteries in the keyboard)
When it happens (Which is does many times a day), i have to delete the paired surface keyboard on the surface book.. wait about a minute, and the press the pair button on the keyboard, and pair it with my surface book again. Then i works undtil the nex time it has been in standby or i have been away from the office.... I have han the surface book and keyboard 7 months, and have never been a issue before a month ago. (I have tried to run e driver update, and the bluetooth repair, nothing helps.
They funny thing is, that i have a business partner in another company with the same setup as mine, he told med that he has the same issue with keyboard as i have....
Any ideas what our problem is, and are there other with the same issue???
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.
Yup, this has been so far infuriating and seems to be getting worse. Surface Pro 6, Arc mouse. If the Pro sleeps, sometimes, not every time, the mouse is gone. Shows as connected, but it's not. Requires full reboot.
And I have also tried all the unticking of power off bits, and the regedit, and a bunch of other suggested fixes
I get this problem too - but have noticed it seems to be worse in the few weeks after a major update (e.g. from Windows 10 version 1803 to 1809 or 1903).
After that the issue seems to settle down.
I did try the registry setting a few people have mentioned:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power
Change CsEnabled to 0
This made no difference so I changed CsEnabled back to default 1 setting.
*The problem has not occurred once since then.*
I have also looked in vain for the setting on the bluetooth radio and wireless keyboard in device manager.
e.g. In Properties, in the Power Management tab, uncheck "Allow the computer to turn off this device to save power".
However, on my Win 10 Pro 1903 there is NO power management tab on that properties panel.
I've navigated to the correct place, there just is no tab for that.
I've navigated to the same tab through the bluetooth settings applet too - and hit the "change settings" button.
No power management option there.
I even installed the specific driver for my bluetooth USB dongle from ASUS - expecting that the full driver would provide the power management tab - but it didn't.
Gave up on that idea.
So - from my experience, try changing the registry setting, reboot, change it back to default, reboot again.
Then make a wish, cross your fingers, promise to go to church (no need to actually go) and then hope.
Worked for me ;)
Open Device Manger and Expand Bluetooth Adapters. Double tap "Marvell Avastar
Bluetooth driver" and click Power Management, unmark "Allow the computer to turn
of this device to save power" and click Ok.
Thanks so much. In my case it was the Intel (R) Wireless Bluetooth(R) under Bluetooth in Device Manager.
it is already unmarked.
As of two days ago (August 6, 2019) it was still happening. And yes, I unchecked that thing ages ago.
I think we all have tried that, hence the thread. We are having problems with the Marvel Bluetooth radio on the Surface 2 with the surface keyboard. Though, since the last update KB4505903, I can't say the Marvel is having problems anymore. I think it went away. Will know soon.
