Hi all,
We're running a fleet of ~8,000 managed Windows devices with TeamViewer Host Custom 15.62.4 deployed via Microsoft Intune. Our IT staff uses TeamViewer Full Client to connect to these hosts via TeamViewer ID + password or by device name with user confirmation.
On a small subset of devices (seems random, a few cases per week), UAC forwarding is broken during a remote session. When an action triggers a UAC prompt on the remote device:
- The screen on the supporter side goes black
- TeamViewer shows a message that the connection was interrupted
- The user at the remote device sees the UAC prompt locally and has to dismiss it
- Once dismissed, the remote screen becomes visible again
So UAC prompts cannot be remotely controlled on these devices at all. On the vast majority of devices in the fleet, UAC forwarding works normally.
The only reliable fix we've found is a complete TeamViewer uninstall + reinstall. After reinstall, UAC forwarding works again on the affected device.
- Is this a known issue with TeamViewer Host 15.62.4? Any internal tickets on broken UAC forwarding with this symptom pattern?
- What runtime state does the TeamViewer service rely on for UAC/Secure Desktop forwarding that could be broken without leaving traces in Registry/files/event log? COM proxy instances? WinStation/Desktop ACLs? Credential Provider registration? Process token state?
- Is there a way to repair the forwarding mechanism without a full uninstall/reinstall? For example, does
TeamViewer_Service.exe -remove / -install achieve what MSI reinstall does, or is MSI reinstall doing more? - Are there specific TeamViewer log keywords or debug settings that would help us capture the exact failure path the next time this occurs on a user device?
Any insights would be hugely appreciated. We'd prefer a targeted repair over deploying blanket MSI reinstalls across the fleet.
Thanks!
