Operating system: Windows
Version: 15.41.7
Release date: 2023-04-26
This has to set a new record for response time. Post asking the question: 23/6. Reply: 8/12. Two weeks short of 6 months. Well done Teamviewer, another example of great customer support.
Hi @khakhovich,
Thank you for your post, and welcome to the TeamViewer Community! 🙂
I think I know where the issue you have is coming from. The problem is that you are installing the TeamViewer full version on the remote computer, and then you sign in with your account on this device to assign it. This will indeed consume a license move. However, this is not how easy access (unattended access) should be set up.
The best practice for setting up unattended access is to install TeamViewer Host on the remote computer. After opening the Host, you can click the Manage device button. You'll be able to assign the Host to your account, but this will not consume any license moves from your license.
We explain how to set up unattended access here: Provide unattended remote support
Let me know if this has worked for you!
/JeanK
"How is it that I can't get the new interface ? In the beginnen I use it but it's gone."
🤷♂️ Why would you want to?
What possible advantage does it provide?
How is it that I can't get the new interface ? In the beginnen I use it but it's gone.
I did a reinstall en also tried it on a windows device, both disappeared at the next start up. We got the tensor basic since a couple weeks now.
Please make "grant easy access" available in the new interface. do not force me to sign in on the new interface and get greeted with "you don't have enough licenses". grant easy access is only used in my case to support remote desktops off hours in unattended mode when users are not in the office.
old interface have this feature, new does not. please stop trying to milk customers into more licenses.
"...it's even easier now"
What utter nonsense. [removed per Community Guidelines]
You've clearly never had to deal with actual real-world users who can't tell the difference between googling for a website and entering a URL, can't read the actual words on a website screen, have no idea what web browse they are using, don't see what happens when they click a download link, and don't know where to find downloaded files.
No, it absolutely is NOT easier. Just the part about having to log into TeamViewer website _just to set software options_ is ABSOLUTE **bleep**. At the absolute minimum, that requires multiple stages of "device verification" back and forth which is easier *HOW, EXACTLY?*
I'm normally very patient with changes and am able to deal with the many and bizarre requirements of various software companies but nothing has made me as angry as this latest set of changes at TeamViewer. It's a TOTAL FAIL which is not even mitigated by any additional convenience or security. Why the actual **bleep** should we have to re-learn all the procedures we have used for a decade just because some marketing droid decided the software needed a facelift?
This was change for the sake of change. *ROLL IT BACK.*
For those that want a quick and easy fix, Past the below into a text file and save it with a .reg file extension, the run it (Make sure teamviewer is closed first) and it will revert to old version without needing to sign in.
Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\TeamViewer] "UIVersion"=dword:00000001
OR
Right click this link and click "Save File As"
teamviewer-revert-to-old-interface.reg
https://raw.githubusercontent.com/bmwillrath/teamviewer-revert-to-old-interface/main/teamviewer-revert-to-old-interface.reg
WhatsApp.
What a pity this forum won't allow editing of the quoted text. Sorry everyone, I didn't need to put the entire text in but did want to thank and congratulate B123 on a thorough and thoughtful post that said most of what I wanted to but was too frustrated (yes, and angry) to compile into a single document.
I might add that having a window (as support person or end user) occupy just about the entire screen is also an indulgent waste of space. Who the **bleep** signed off on this? Not everyone has multiple monitors.
Also one other thing that I find intensely annoying is that screen sizes are not consistent. Instead of remembering the size and scaling of a particular remote computer's screen, it seems to remember only the last screen and use that setting for your next session, irrespective of the actual screen layout. So I get black bands on the sides of 4:3 screens, unreadably small text on a 1920x1080 27", and other wastes of time. Irritating. Years ago the same screen always came up the same size & layout - why change it?
Indeed, why change all the settings that were working. Has TViewer decided to folow Microsoft's philosophy of change for its own sake? It's not important to be making improvements, it's important to be seen to be making improvements? Where the word improvement is heavy air-quoted and sniggered at behind your hand.
No, TeamViewer GMBH, this is a sorry **bleep** of a change and I'm jumping ship to **Third Party Product** who still embrace simplicity over all this **bleep** you have encumbered us with.
Yeah, fine if you only do "quick support" but I need to set up permanent passwords and access PCs at random without interacting with the user every frigging time. That gets old very fast. I have sometihng over 400 remote users and getting a new password from them every time is a HUGE waste of time.
So to set a permanent password REQUIRES LOGGING IN TO A TEAMVIEWER ACCOUNT. And since you obviously can't log all your users in on your account, you then have to create a unique account for each user. Which is tedious at best.
@JeanK So let me get this straight, to have access to the program's settings, including reverting to the classic interface, you have to have (or create) and account & log in to it? So every PC that we set this up on, we will have to go through logging in to our account - which of course means adding it to our trusted devices with all the back & forth emails, MFA etc - even if that person will never need access/maybe shouldn't have access to that account, or if we aren't being asked to add it to our account, or if it is a one-time assist. Or what if we have several hundred of them to roll out. . . Even for a free home user, just to change their settings - say to use the classic interface, or set a permanent password so their more tech-savvy teenager can help them out - they will have to create an account?? Or the support professional, without yet being able to get access to their PC, will need to get it logged in to their account so they can get the Client ID from the user?
Thanks goodness we have quickly found the registry setting for the UI, I will be implementing that via Group Policy at my support client locations.
And why hide the self-minimizing option many levels down in the advanced settings (which, remember, we can't get to without creating & signing in to an account. . ) Why change its default behavior at all? Great, make this a new option for those who want it - but why make it the new default, with the added pitfall of throwing up a choice with a 50/50 chance of closing the connection when the user does the obvious and closes that window, expecting from previous behavior that it will stay running in the system tray?
That is all so incredibly much less convenient than it has ever been before.
Also, why would you put what is essentially an ad for the product we already own and are currently using on the splash screen? That is going to age about as well as Clippy the MS Office Assistant. . .
How can I send a message to a device with the new Teamviewer?
Hi @JeanK,
Thank you for your answer. Here is a reply, point by point, based on actual use cases.
Connecting to a TeamViewer ID is the primary use-case and should really stay as the first thing the user sees. This is not just about fixed passwords and unattended access.
If you want to split TeamViewer into a Host and a Viewer, that's fine, but keep the TeamViewer ID of the host and the ephemeral password visible as the first thing that shows up.
In real use cases, the process of people exchanging TeamViewer ID and password, and the connection itself can be quite asynchronous (the person in front of the PC might not be able to type anything straight away, if at all).
Call this "semi-attended" access if you wish, but that's a frequent case many of us have to deal with (I've seen similar use cases in other comments).
What you refer to is not what I meant. See screenshot in this post: https://community.teamviewer.com/English/discussion/129541/new-ui-is-too-complex
I had created 3 sessions, 1 cancelled after closing the "Connect with ID" dialog without entering anything, the others with different TeamViewer IDs, but I can then see 3 sessions without having any idea which remote TeamViewer IDs they were for.
This is particularly a problem when I need to have multiple sessions, with completely different users, opened at the same time. Sure, you can edit the session name, but it's often too late. (Again, they may not enter the session ID immediately: the new model forces more synchronisation between participants.)
The old way (using the remote PC TeamViewer ID) is much simpler and effective.
See previous comments. They'll often just not wait around to type the new session ID, or won't be able to (and hopefully won't enter it into the wrong PC).
You seem to think it's just a matter of explaining the new way, but that's not the case.
The fundamental problem with this new version is that you've completely changed the workflow between participants. This requires more round trips, more synchronisation between participants and more steps in general. It's objectively more complex. Requiring more effort from the person in front of the controlled PC (even if you think it's not much) is generally a problem too.
Please make sure future updates keep the TeamViewer ID and password as the main information displayed at first on the host. Simplicity was the whole point of using TeamViewer.
Hi @Farplants_IT,
Thank you for your feedback. 🙌
I'm sorry your first remote support session didn't go well after the update. But let me reassure you - everything you could you with the old interface, you can do with the new one, and it's even easier. It just takes a little time "to get used to the new system".
What you describe is the typical attended access scenario.
We explained the best practice in a step-by-step article on how to provide attended remote support here:
Please give it a try and let me know if there is anything I can help you further!
Hi @B123,
Let me answer to all the points you mentioned.
This is correct - connecting with an ID and a password is (still possible) no longer recommended by the new interface.
Based on what you said, you want to connect If you want to connect with "a fixed password".
This sounds to me like you want to connect to a remote device anytime without having someone on the remote side.
Therefore, it's unattended access you are looking for. Unattended access is still possible - we explain in detail how to proceed to set up unattended access in our article here:
Let's talk about the export (person giving support) and the participant (person receiving support).
The expert will always see the toolbar appearing when connected to a remote device/participant, like in the screenshot below:
The participant does not see this toolbar.
This way, you can always know in which direction the connection is used.
In this use case, the participant can join the session via session code. Let's say you have the participant on the phone, and want you, as an expert, want to connect to them:
As previously mentioned, the obvious case you describe here is explained here:
Please check this out and let me know if it worked out or you have any issues. I'm here to help!
Hi @HOMECALL_PC and @Drewskius@Drewskius,
Thank you for your message. 🙌
Guiding through clients and providing remote support is still possible, and it's even easier now. The process just changed a little.
We explain how to provide remote support (attended, so when there is someone on the remote side) here:
Let me know if you have any further questions! I'll be happy to assist.
@Pdxpaul About the second thing you mentioned, you can fix this by enabling the Close to tray option in the Advanced settings. To do so:
Now, when you close TeamViewer Remote, it should only close the windows and run in the background.
Let me know if this fixed it!
Hi @sipher and @Pdxpaul ,
I am sorry to cause this confusion.
The screenshot I shared is only relevant for participants joining a session.
To access the settings, you must first sign in with your TeamViewer account.
I edited my initial post accordingly and added the info about signing in and a screenshot showing where the settings button is.
Here again, for your reference, to revert to the old interface:
I hope this could help.
@JeanK This is infuriating, as far as I can tell there is no settings cog/wheel/gear on the splash screen in the new UI to get to the settings menu. Likewise there is not one in your screenshot, and not on the handful of clients I have had to deal with in the last couple of days. Only option seems to be the registry setting that some commentors have very helpfully posted.
Another really annoying thing with the new UI is that if you open it by double-clicking on the desktop icon, then realize you don't want it & go to close it, it immediately goes to the "close all connections" dialog rather than just minimizing itself and notifying the user that it is still running in the background. That is an unwelcome change that is sure to catch a lot of people off-guard and end up closing some connections that will be hard to get back. Also confusing is that it now does not show up in the system tray area, so that is another place that we are used to directing people to find out if it is running, get their client ID etc. that is no longer available.
Rollout fail, sorry
For anyone struggling with the new interface, change this registry key and restart Team Viewer to go back to the old interface
[HKEY_CURRENT_USER\SOFTWARE\TeamViewer]
"UIVersion"=dword:00000004
Values:
00000004 - new version
00000002 - old version
This change is unbelievable to me. Its already causing me to lose time supporting this application rather than what I'm paid to support. I'm surprised there aren't more complaints in this thread.
I have been with Teamviewer for over 10 years now. I've loved it until now. I will wait until the end of my contract in the hopes that enough of their clients will revolt and convince them to put the ID info on the main screen. Otherwise I'll be switching to a competitor, and probably saving money to boot!
What a **bleep** shame, Teamviewer. 👎️
JeanK, according to your advice, the user can:
But in the photo you shared, there is no Settings (⚙) option to click.
How can users of the device shift to see their ID from the "new" splash screen? (No Settings (⚙) in this screenshot.)
Are you stating that if a user clicks "Join a session" it will show the ID?
Thanks for clarifying that users will NOT need to create a new account. However, I still don't fully understand why this new splash screen is necessary. We'd select to remain with the ID and PIN "front and center" for the user to share.
You know what the great thing is about having multiple machines to test with? Figuring things out myself.
HKCU\SOFTWARE\TeamViewer
Change DWORD value 'UIVersion' from 4 to 1.
Hope this helps others in a similar situation to ours.
Just to clarify, you cannot or will not? This seems a fairly reasonable request, and it's by no means an impossible task.
Hi @Jito463,
Unfortunately, we cannot provide you with a reg key setting. The abovementioned way is the only supported way to switch to the old interface.
Is there a registry key we can set to default the better, classic interface? I don't have a paid license, but we do at my job, and this change is causing us severe issues.
I did find a short term workaround, but a reg key setting would make things much simpler.
Hi all,
Thank you all for your feedback - I'll try to answer all your questions chronologically.
@JPazur @Spanky_here6 You can switch to the old interface by the following:
TeamViewer Remote will restart with the old interface.
@sipher End-users do not require an account. End-users can join the session by clicking on Join session in the main interface when they open TeamViewer Remote (please see screenshot below). Alternatively, you can also send them a session link so they can join the session via QuickSupport, as @wingers said.
Let me know if you have any further questions.
What a shame this interface is so terrible.
Had the first experience of it on Out Of Hours at the weekend (no announcement from TeamViewer they were fundamentally changing the way you connect to a user)
Call went like
And then 20 minutes of creating a session, sending it to the email on their phone, explaining how to type that in on the PC because no I don't want them to connect via quick support. Not slick at all.
TeamViewer was the best, hands down. Simple, easy, reliable, universal. Their attitude to cancellation of service is rubbish and was already thinking of leaving for **Third Party Product**. This update has sealed the deal, may not even wait till the end of the current contract.
Shame.
There's a few uses cases where that simply doesn't work:
The new UI is objectively more complicated (at the very least because we now have to deal with the concept of "sessions" too).
There's a number of cases where the new system doesn't make much of a difference indeed, but there's also a number of existing use cases that have now become more complex.
It's not just a matter time to accept the change, unfortunately.
Learn more about the latest feature we’ve released.
Discover quick, practical tips to get more out of TeamViewer each month.
