Hey there,
Let me briefly comment here. This issue should be fixed in Reach Firmware 26.2. Please update the receiver and check if it resolves the issue for you.
As always, the full list of fixes and improvements is available in our community forum thread.