Magic mouse turns off/ disconnects after 1-2 seconds under bootcamp when not used and turns on while shutting down

Bluetooth collaboration seems to be turned on. (Even though I switched to English some settings remained in German and it says bluetooth Kompatibilit't whichs translates to bluetooth compatibility so I guess that must be the same as collaboration?) Might it have something to do with the fact that I I only have the generic bluetooth radio device (with no power management tab) and not the apple broadcom built in bluetooth. Whenever I try to install the latter by browsing my computer for drivers and than manually choising it by picking from the list there is an error.

Would it help to use a bluetooth mouse with a logitech unifying receiver such as the windows version of the mx master 3 that is plugged in via usb? It would be still bluetooth based but the bluetooth signal would be received by the unifying receiver?

The device manager looks like this. When I click on bluetooth radio there is no power managament tab. However, there is one for for the broadcom 802.11ac network adapter and I had already unchecked the box to "allow the computer to turn off the device". This didn't help unfortunately.

Since it it is an apple variant, shouldn't I have the apple broadcom built in bluetooth drivers which do not work?

Yes, I do have the Power management tab for the Broadcom network adapter (but not for the bluetooth radio) and already disallowed it to turn off.

Btw, why are there two setting for bluetooth within microsoft's device manager? The general bluetooth subtree (bluetooth radio in my case) and the broadcom network adapter under the network adapters subtree?

No, there is no power management tab.

It's a MacBook Pro 13-inch with the touchbar, 2016, Four Thunderbolt 3 Ports

I've just tried a Logitech bluetooth mouse and it worked fine. Are these the drivers you meant?

vendor id = 0x05AC

product id = 0x007E

As I said the mouse (any bluetooth mouse) starts working again while shutting down or after closing the notebook‘s lid and being in the log in screen. Then after logging in it stops working again on the desktop. Maybe this might help to narrow down the problem.