Updated:03:03 PM CEST Oct,03
(new)
(c) 1998-2026 Gameguru Mania
Privacy Policy statement
|
TeamViewer Cut Server 2012 and Left the Client Hanging - tech|
| (hx) 03:02 PM CEST - Oct,03 2026 | TeamViewer stopped active support for Windows Server 2012, Server 2012 R2, Windows 7, Windows 8, Windows 8.1, and Server 2008 R2 on April 29, 2025. The last build that still runs on those systems is 15.64. Version 15.65 and anything newer will not install a working upgrade path.
The reason is a library cut. TeamViewer uses the Boost C++ libraries for utilities such as file transfer. Boost 1.87 dropped older Windows. New TeamViewer builds are compiled against that library, so they cannot ship on Server 2012. Microsoft had already ended extended support for Server 2012 and 2012 R2 on October 10, 2023.
How to keep access:
On the old server, uninstall the broken 15.65-or-newer client, including the Host service. Install TeamViewer 15.64 Host, or the full client, from TeamViewer’s own previous-versions page. Assign the existing account, then turn automatic updates off so it cannot jump to 15.65. A current TeamViewer client can still connect inbound to 15.64. Test it. If that session also hangs, connect from a 15.64 client as well.
If TeamViewer has to go, use Remote Desktop instead. Turn on Remote Desktop and Network Level Authentication. Allow it only from a VPN or known admin addresses. Do not publish port 3389 to the internet. Server 2022 gets no Microsoft security patches, so this is a stopgap, not a fix. Move the box to Server 2016 or newer when the application allows it. |
|
last 10 comments: All comments
|
|
Add your comment (free registration required)