Not to be rude sir, but this isn't helping troubleshoot the issue. My driver signing is still enabled and I have no trouble installing or using Teamviewer 12 or 13. Are you running the latest version? I'm running a mix of 12 and 13 (upgrading them all to 13 now), all on Windows 10 (x64), builds 1703 (Creator's Update, upgrading as well) and 1709 (Fall Creator's Update, fully patched), and I have had 0 issues with installation and not seen the behavior you're describing. I have it installed on 9 computers (personal use, 6 Windows boxes, 2 Macs, 2 CentOS). I have not have not had to lower or adjust a single security setting on Windows; only one setting for SELinux on the CentOS boxes. Lowering a security setting isn't "hacking"...it is changing a setting. Unsigned drivers aren't necessarily dangerous either (though I've not had to do this experience with TeamViewer, like you say), it depends on where the driver is coming from and why you're installing it. Reasonable admins should carefully weigh these factors before installing such drivers, but signed drivers aren't a guarantee of security either. They just guarantee that Windows doesn't complain. Perhaps you'll recall when Adobe dumped their private key onto the internet in September 2017? (https://www.theregister.co.uk/2017/09/22/oh_dear_adobe_security_blog_leaks_private_key_info/) Windows (regardless of version) would have never complained about malicious software signed with that key, but it still would have been a malware-related security event. The developers at TeamViewer (none of whom I've ever had any contact with) work very hard on a complex software; they offer it free for personal use, and they have created it to be cross platform compatible. Good software is tough to architect and implement to begin with; and even harder to get right across every box every time. Microsoft has been in this game how long? And they break stuff all the time. Apple too. It is a fact of life, especially as tech becomes more complex (and hopefully more useful). Admins should use intelligence and reason, not insults or disparagements to choose which software they use, and why.
... View more
The issue seems to be primarily with PCs running nVidia drivers. I've noticed it on my MacBook Pro as well (Late 2013, using nVidia 740M 2GB). There could be some AMD instances, but I see many compliants about nVidia drivers, with specific mentions. I haven't noticed AMD complaints, I suppose because the nVidia compliants have stood out. I wonder how many people on this thread are running nVidia drivers? I've also noticed on my PCs, my Intel Graphics and AMD graphics don't have this issue. I have a limited testbed, but it does seem to stand out. Doing some looking around it looks like TeamViewer and nVidia have had some trouble playing nicely together at least since TeamViewer 9.
... View more