TeamViewer 13 Client Will Not Let me Sign In

The Email and Password field are grayed out. I've tried reinstalling the software and I've rebooted my computer multiple times. I even downloaded the client again.... I need some help to figure this one out. The client was working fine for a long time. This started a few days ago.

Find more posts tagged with

Accepted answers

kimenemark

Perhaps I'm not explaining myself good enough... sorry for that.

I also have production VM's on the PC. You don't have to remove anything. Just disable Hyper-V and reboot PC.
Then log in to TeamViewer.
Then enable Hyper-V again and reboot.
Now both your VM's work and TeamViewer works... at least in my setup.

EDIT:
I can explain in more detail if you need it...

All comments

kimenemark

I have the exact same issue since friday where I updated my version 13 to latest build!!!

Dominik971

Hi,

I have the same issue since wenesday... Did you get a solution ?

RYACOM

Nope. Nothin' so far.

kimenemark

Any of you using Hyper-V on the PC's with this problem?

I got so desperate that I tried to find a solution myself.

In my case I tracked it down to an issue with my Hyper-V setup on my notebook (still not sure what exactly... propably somehow the Virtual Switch setup).

If I disable Hyper-V on the PC and reboot then I can suddenly login to the desktop TeamViewer program with my credentials and see all my clients.

After that, I enabled the Hyper-V setup and rebooted again and TeamViewer still works.

Hopefully this helps others in similar situations... and perhaps support can use it as well

RYACOM

I was actually going to ask the same question. I also am using Hyper-V. I have to use it though, and disabling/removing and re-enabling isn't something I can do on this machine. There are production VMs on it.

I am a paying customer, too. I'm going to find a number and call in to see if we can get this resolved. I had a pretty strong feeling that was the culprit. I had a similar issue with the Microsoft Store and Minecraft of all things. Something to do with the Virtual Switch was making it unable to authenticate to the store while ingame. It also wouldn't let me see purchases within the store that is ingame. They eventually patched it and it's fixed.

Wish me luck.

TheDeadLotus

I was able to find a work around (which renders the desktop app pointless) is to log in inside a browser, then "Connect" to the computer that I'm on. This will log me into the desktop app so I can then use the app. This started Friday when I got a new computer at work. My old one was running Windows 7, this one is running Win 10.

kimenemark

After login both works side by side for me... if I log out of TeamViewer I'm sure I will have to do it all over again... haven't tried but will try to track problem further once I get more time... hopefully in a couple of days... if not support beats me to it

Have a nice day

kimenemark

Sorry for your problems mate... I'm a paying customer... would kind of annoy me if non-paying users would get help before me

You get annoying messages... My teamviewer don't work at all... a little different issue I think?

Hope to get help sooner than later... I would consider spending my money elsewhere if not

kimenemark

I tried that as well (also running Windows 10) but it didn't work for me... the 2 fields (username/password) was both greyed and not editable in TeamViewer desktop program!

Dominik971

I confirm that HYPER V seems to be the origin of my troubles...

Uninstalling Hyper V allows me to use Teamviever and log in...

But now if i want to use Hyper V and Teamvier... do not really know how to make them work side-by-side...

TheDeadLotus

I have no idea why this workaround works.

RYACOM

I also need to give a little extra detail into my experience with this, a week or more after the suggestion to remove the Hyper-V feature and add it back.

On Monday I was going to open a VM to test a script and noticed that all of my VMs were off. This is not normal. After a little bit of investigation I realized that my virtual switch had been wiped. All of my custom virtual networks were gone. Whenever I tried to start my VMs they failed with a pretty ambiguous error. I had to remove all of the network adapters from all of my VMs, remove the Hyper-V feature (two reboots), add it back (two reboots), and uncheck the "Hyper-V Extensible Virtual Switch" option each physical adapter before I could recreate the virtual switches and attach them to the physical adapters. Just a heads up for anyone who tries the "Remove the Hyper-V" suggestion.

Just to be clear, the suggestion did work. I am still able to get into TeamViewer and connect to my clients now, and I have rebooted and still am able to log in. My VMs are up and working. I just didn't know that it was going to do that.

Make sure to plan an outage of at least 45 minutes if you're going to attempt this, more or less depending on the amount of virtual networks and VMs/adapters you have.

mda400

13.1 still works. its 13.2 that starts having this issue. I run a Server 2016 with MDT vm and Windows 10 pre-release vm at the same time, so I disabled automatic updates for now.

I've experimented with removing the additional virtual ethernet connections, disabling Enhanced Session mode, disabling memory integrity (Win defender virtualization-based security), disabling/re-enabling Hyper-V feature as above (which teamviewer will allow sign in until i start a VM so it likely has something to do with a service Hyper-V is using that the new 13.2 TV version doesn't play well with). and no luck.

Sudrigian

I'm having the same problem in linux, runing Ubuntu 18.04.

Toast

It actually related to the Hyper-V network adapters, not Hyper V as a whole. Disable the Hyper-V network adapters. Then you can login. Once logged in, you can enable the adapters again.

Update: Complete work around.

Open Control Panel.
Select Network and Internet
Click Network and Sharing Center.
Click Change Adapter Settings
Right-click your Primary network adpater and select Properties.
Click the Sharing tab.
Check the Allow other network user to connect through checkbox.
Under the home networking connection, select the Hyper-V Default Switch.

For whatever reason, some programs (such as TeamViewer) want to use the Hyper-V Default Switch.

fcjbispo

Hi,

I tried this solutions and for a while it seems to be working. But when in the very moment i did put a VM to boot.. Boom! Teamviewer blocked the login fields! **bleep**!!!

kimenemark

Hi guys... as promised... I have done some more testing and reported my findings to support.

When I'm running with Hyper-V disabled I have absolutely no issues.

If I start Hyper-V service (and reboot PC) I also have no problems but as soon as I start one of my VM's (they don't start automaticly) I'm not able to use TeamViewer... It just won't log me into my account (desktop program).

As soon as I disable Hyper-V service (and reboot PC) again TeamViewer works again.

So I think my reasoning in one of my earlier posts were right... it's somehow the Hyper-V switch thats the issue.

I have collected info for the support team in the 3 stages so I hope they will be abe to fix the issue.

evanly

There have been other posts about this before, but still no fix.

When Hyper-V is enabled in Windows 10 Pro, I am unable to sign into my TeamViewer Account in the desktop app. This NOT is a new issue, been around for at least the last couple of months/weeks - I can't quite nail down when it started, but I'd say late July.

I don't think the Hyper-V feature set within Windows should be preventing TeamViewers functionality - in fac,t it never used to, and I can still connect to remote systems via ID/password. It's just the account/contact list features - crazy.

And before it's suggested - no, I don't want to remove and re-add the Hyper-V features and restart just so I can get my TeamViewer contact list - only to have it logged out and locked out when I use Hyper-V again. That's absurd.

I find is rediculous that there is not whisper of a fix for this, after months and many posts.
I'd love to enable Insider Builds on the off-chance this is fixed, but I can't sign in to enable this!

TeamViewer, please advise us on a fix for this.

Main other thread on this:

https://community.teamviewer.com/t5/TeamViewer-13/TeamViewer-13-Client-Will-Not-Let-me-Sign-In/m-p/39674#M2133

evanly

While i'm appreciative of @kimenemark posting this, this is not actually a solution, and it does not prevent the issue from recurring.

TeamViewer should NOT require this for such incredibly basic functionality.

evanly

+1 Disabling/re-enabling Hyper-V feature as above works until I start a VM.

Luckily, I only need VMs to do mission-critical operations. Not good enough.

DanZ

Teamviewer is pile of dog **bleep**. What a fail. Can't you just fix the problem, it's been months as people were complaining and the problem is still there.

I have the problem ON ALL OF MY PCs. All of them have the problem. EVERY SINGLE ONE has the problem. MacBook where I run windows (bootcamp), my windows desktop has the problem, and my ubuntu VM also has the same **bleep** problem. WHAT A PILE OF **bleep** seriously.

DanZ

Even though it works, this absolutely cannot be marked as solution to the problem. It's a crytical bug in TV software that must be solved by them and not by us doing weird dances.

I run VM all the time in HyperV, I absolutely cannot uninstall or turn it off, so TV sign-in for me basically does not work at all.

TWG

Hey Guys,

I had a similar case and found out that in Options-->General(tab)-->Incoming lan connection I had "accept exclusively" selected.

You might want to check that too.

Cheers

oldgayracist

I had the same issue

os: ubuntu 16.04

I went to Extras > Options > General

in the 'Account assignment' I've tried to assign my account, but there was an error saying that niether name or password match (I double checked it was correct)

rebooted pc

after reboot I've started teamviewer, instantly saw the same arror message in the pop-up window and now I'm able to type in the inputs, nothing is greyed out.

I hope it helps

pacz

Hello DSperber,

Did you ever resolve this issue? I have the same set up with Ceton, WMC, HTPC. TV will not let me sign in. I just upgraded to TV14 and it still will not allow authentication?

If it matters, TV worked perfectly before TV13. So, something obviuously changed in these new versions.

Dultrawiz

I have WMC + Ceton Echos setup and have seen this issue as the few others above have. the only way i am able to remote into the Main PC hosting the WMC content is by shutting down all the Cetons in the house and then i can remote just fine. I agree this is not a solution and a very inconvient workaround but it works. And this does seem like it has started within the last few versions of TeamViewer.

pacz

Kind of defeats the whole purpose of remote sessions...Hard to shut down Ceton Echos and XBOX's when you are 3,000 miles away traveling and the family has a PC challenge. :-)

Is it possible to roll back to TV 12 or 11?

inspiresayan

Same question. When I Try to connect Namecheap black Friday then it's not opening.

Spartanz

Hi Toast,

Thanks for the post, your solution fixed my login problem. Althrough I only did your steps 1 to 7 only. But it fixed my login stayed in blue. Thanks again