Latest Teamviewer Version

[Tolomeo Tanguay]

TeamViewerHost is used for 24/7 access to remote computers, which makes it an ideal solution for uses such as remote device monitoring, server maintenance, or connection to a PC, Mac, or Linux device in the office or at home without having to accept the incoming connection on the remote device (unattended access). Install TeamViewer Host on your devices to access them effortlessly.

TeamViewer MSI is an alternative installation package for the full version of TeamViewer Remote or for TeamViewer Host. TeamViewer MSI is used to deploy TeamViewer via Group Policy (GPO) in an Active Directory domain.

I am just trying to install TeamViewer 64bit on a new Windows machine. But once I downloaded it, the installer prompts that I have already installed Team Viewer 32bit, whereas I never installed Team Viewer on this machine. I can't find any Team viewer folders or files on the entire computer.

This drove me nuts as well - receiving the "Team Viewer 32 bit version installed" message, uninstalling the existing 32 bit version- checking it was gone - then finding same "Team Viewer 32 bit version installed" error when trying to install 64 bit version and seeing the 32 bit version was back again - then repeating the process.....

I am using TeamViewer on my MacBook at home to connect to my PC at work. At some point in the past week I have started getting an error message on my home computer about needing to update my TeamViewer. It says "Your partner is using a newer version of TeamViewer and you need to update your version of TeamViewer to establish a connection".

The problem is, when I'm in my TeamViewer, it tells me that there are no updates available and that the version I'm using (version 10.0.52680) is the most current and up to date. But it still will not let me connect. I tried completing shutting down the TeamViewer on both computers to see if that helps. The problem is I obviously can't be in both places/on both computers at the same time. Does anyone have any suggestions for what to try next? I am going on maternity leave in a matter of weeks and I desperately need to be able to access my work computer while I am gone.

If your connection partner has a newer TeamViewer version running, you can either update your own TeamViewer version to TeamViewer 13 or you can ask your partner to start a TeamViewer in an older version.

My friend just got a brand new Dell Inspiron 7xxx 64bit running WIN10 Home. He has TV 14.5.1691 . This is the same version I am running yet TV gives me a notice that I can't connect to partner because he is running out of date. Tried re-bot, uninstall/re-install on BOTH out computers yet I still the same message. My friend can connect to my computer fine Any ideas on how to fix this?

I'm experiencing a similar issue. I'm trying to connect to a host that claims to be using a more recent version of Teamviewer. But there is no newer version to update to!! I'm running TV 14.7.1965 on macOS, trying to connect to a PC with Win10.

This is NOT solved. Yet again, TV14 will not update to 15 for me and manually trying to DL TV15 gives me errors on three different browsers that the request can not finish (sorry, i'm on a german pc, so i don't know what the actual error message in englisch is...)

it's about once a year that i travel and am more dependant on TV than ever, and ever again it fails me in some way...

I'm a 1 person show ... my company's only IT person. I've been using PDQ deploy to install Teamviewer on all of our machines so that I can get remote co-access to my end-users machine to support them. This new version is absolutely a nightmare. It's worse than beta software with the bugs, the horrible GUI, the serious degradation in performance, and oftentimes the compelte lack of functionality. The software looks horible, is hard to use, way too many clicks, and in the end, doesn't work!

Since I have a business account, I called their support when this surprise version was implemented because I could no longer use it without each of my end users creating an account and logging in (that's never going to happen!). However, they were so innundated that the phone line went to a message telling me to make a ticket online and then it hung up - even though one of the 'features' of a paid accoun is phone support. So I created a ticket, but never heard back from them.

I called back later in the day and was able to get into the call queue . I spoke with someone who was nice, but told me that with my business account, I should not be installing the full version on end-users machines, but I should be installing only the Host version. So I went through the process of generating a host to install. I deployed that on several test machines. The Host is garbage. Sometimes the install works, sometimes it doesn't. Sometimes the machine is remotely controllable, sometimes it isn't. If I try to configure unattended remote access, sometimes I can get it to allow my account to manage the machine, sometimes it won't accept my username and password... sometimes I enter my username and password and it just hangs there and nothing happens. Totally inoperable, totally inconsistent across the board!

Since we have multiple locations, I have the machines I manage organized into different groups by location. No longer can you drag and drop to move machines & device into the group they should be in. Furthermore, with the Host, sometimes a machine I've installed it on shows up in the management console, but most often it doesn't show up at all! The host says it is managed by (my email address), but it doesn't show up in my TeamViewer anywhere. If it does show up in Teamviewer, then I am not able to move the device into the correct group in the TeamViewer app.

I created a host which has our logo and "supposedly" puts the machine in the correct group, but it never puts the machine in a group - the machines are just lost in the ether somewhere. I deployed the exact same host setup.exe to 5 machines and 3 of them had the branding and 2 did not... 2 of them have the god-aweful new GUI where you have to make 2 extra clicks to find the TeamviewerID. 2 of them were managed by my account, and 3 of them I cannot get them to accept my account management.

One of the main reasons we've used teamviewer in the past was simplicity and consistency. This this 10 steps in the wrong direction. This new software is complete garbage, and I'm strongly considering moving to something else. My end users are going to have to learn something new anyway... it might as well be something that works instead of this steaming heap of **bleep**.

I had the same experience yesterday. Could not connect to a client that I had just connected to last week. Had them install the new software then neither one of us could figure out how to connect from my machine to theirs.

Any new versions need to be better, faster, easier to use, not harder to use. And definitely not more confusing. Do not do like Windows and just make changes to be making changes. Make things better for the user. When you make our lives harder, we move to something else. I know I will.

TeamViewer has obviously had brain fade here. I can't find an option to connect using a LAN IP address and it appears that someone at the receiving end is required to generate a code to give to the person initiating the connection. Absolute idiots!

WOW what a fail, this is juvenile development. Been doing this for 30 years and cant work out how to add a machine to a list. And how about having to add device to join this blog when the same device has been running TV for years. Get your act together, turn this new garbage off until you get it functioning. Whoever developed this has never done support. Leaving if you don't wake up!!

All they need to do is to click on "Join a session" and enter a Session Code or click on "Connect to a TeamViewer ID" (which doesn't quite make sense, since it will actually display their PC's ID.)

I know that if you use QS or host you pretty can get the old interface but as sometimes happens that it's useful I like the most to install the full version. So the last two days they were nightmare so I had to rely on other solutions to fill out my supporting job as the only workaround I figure out of this GUI mess. So **bleep** stupid so **bleep** outrageous. I'm just waiting the moment our license will expire to get their sales asking to renew because I'm going to tell him we switched to something else hoping they do not mess the same way.

Same for our tech support. We were using TV for years and this new changes may result in us being forced to change to an alternative. Calls with computer illiterate users are difficult already and considering you have SO MANY extra steps is a no-go for us.

I think , considering they are substantially changing the product, its uses, its benefits and simplicity, a refund for those wishing to move on shoudl be in order. Either that or to at least maintain the "classic" apps and functionality until the end of current subscribers billing cycles.

After 15 years with teamviewer I will be moving to another product. So far... complete failure on the new interface and management, multiple outages, connection issues constantly, my device groups are a complete mess, new interface takes up to much real estate on my screen, I pay way to much for teamviewer, and someone should be fired at teamviewer for the new platform.

3a8082e126