Bluetooth dropouts with Wahoo Kickr v5 on PC

Hi everyone!

I’m currently using Zwift on my PC laptop together with Kickr v5 via Bluetooth.
Starting from December 2020 I started noticing the Bluetooth dropouts. They occur randomly, the cadence icon grays out and I stop in the game. At the same time, my HR strap also connected via Bluetooth(Garmin HRM Pro), continue working without an issue. Then, after 10-50 seconds, the cadence icon becomes active again and it takes minutes sometimes to re-activate ERG mode which I use frequently.

First, I thought it was a trainer issue. I spent some time with Wahoo support and they replaced the trainer. The new one has the same Bluetooth dropouts as the old one.
I have the latest version of Kickr, Windows, and the BT driver.

I would appreciate any help on the issue above. Thanks!

My typical Zwift log (the part where dropout occurs) looks like:

[8:27:38] FPS  48, 139753, 15525, -228821

[8:27:39] [FTMS] ERG (195w)

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Exeption caught in Windows BLE CharacteristicValueWrite()

[8:27:39] BLE  : Sending DEVICE - BLE DISCONNECT ERROR [ UUID: 229164264002465 ]

[8:27:39] BLE  : Starting Native BLE search

Also get this on the Kickr Bike (since latest updates)
[6:52:45] BLE : Exeption caught in Windows BLE CharacteristicValueWrite()

Same here. Does that categorically mean that it is the trainer failing?