Force Quit WindowsServer to deal with IntelBluetooth post wake issues

I recently updated from Big Sur to Ventura on my laptop hack and bluetooth works fine just like Big Sur.

Except for one thing, after sleep, you have to toggle it off and on again or use the command sudo pkill bluetoothd for it to work or else it shows toggled on but can't connect, so I assume it has some issues with starting up bluetoothd after wake.

Sometimes however, bluetooth completely fails to start/connect to devices even after the on off toggle or using sudo pkill bluetoothd and the OS needs to be restarted.

But if instead of rebooting the OS, if we force quit WindowsServer, which automatically logs you out of the system and kills all apps/processes, the bluetooth process is restarted and works again.Not sure if this is a known issue as I couldn't find much around.

I'm also not sure if force quitting WindowsServer causes any significant downsides as the only thing I know is that it is related to display and as far as you don't have any important process/app running, force quitting it should be fine.

Correct me if I am wrong.

I had no such issues on Big Sur btw.

If anyone is aware of a potential fix, let me know too.

submitted by /u/DoomsDay000000
[link] [comments]