I'm using a windows 7 proffesional desktop to control a windows 10 host desktop. Everything was fine, until yesterday, when i connect to the host, however it shows a total black screen, and the window freezes ( i can tell, because if i select an option from the TV's menu on the top on the window, the menu stays there forever, and if i select another, it just overlaps ). I tried to connect to the host from another desktop ( in the same lan with the first ), and it's working fine. I tried reinstalling, i tried downgrading both, the issue still remains. What can i do ?
P.S. Before the issue appeares, i connected to the host via smartphone, can that caused the issue somehow ?
Solved! Go to Solution.
Please install the version from the following link on both sides and try it again:
Thank you for the post. Which TeamViewer version is installed? I need the version number :)
You can find it in TeamViewer under "Help - About"
Please install the version from the following link on both sides and try it again:
Thank you for the fast responce!
I just installed it to the desktop, it works fine now. But i haven't install it to the host. Should i install it to be safe ? Also, should i install it to the rest desktops i use to control the host ?
Also, on the version you gave me, it says there is an available new version. Should i upgrade it ?
I have sent you the previous release - the issue with the black screen is a bug in the current version and using the previous version is a workaround.
So please do not update to the current version ;)
I will inform you when we published a new version with a fix.
I have the same problem, but when I access the host by an Android smartphone. I installed this version of your link on Host PC and reinstalled the latest version of Android, but the problem continues ... black screen. What can I do?
I have recently started using a new PC riunning Win10 Pro, and am trying to control it from my old PC WIn7 Pro. I have tried to set the option to diable user input and black the screen on the Win10 PC when controlled from the Win7. A message splashes up on the Win10 PC saying I need to install a monitor driver - whaich I say yes to, and then nothing happens for a while. Then the WIn10 screen goes black and when I try to control it from the Win7 PC I can for about 15 seconds - and then the Win10 screen I am seeing on my Win7 pc goes black for about 15 secs then comes backa again then goes black again and on and on
So I disconnect the WIn10 PC from the WIn7 PC. Then I go the the Win10 PC (physically) and despite not being connected to any TV connection ,teh screen keeps going black every 15 seconds
So I close TV on the Win10Pc - and still the screen keeps going black every 15 secs
It is only after rebooting my Win10 PC that I get control back on my Win10 PC without the black screen hitting every 15secs
So please let me know when this is fixed in the new TV12. Until then I will run TV11 as suggested in the workaround on this thread
Same problem here as of 9/26/2017. Both host and client are running the latest version of Teamviewer, but when connecting all I see is a dark gray (almost black) screen. I've tried fiddling with the connection quality settings but nothing works.
Aorus x7Pro Laptop
Windows 7 Enterprise 64
Host: (multiple configurations/vendors/OS)
Interestingly, if I enable SLI on my laptop (2 x GTX970M), it WORKS. Until I started using version 12 however, Teamviewer worked fine in single GPU mode. Very strange...
v13 doesn't fix the issue either.
12.0.83369 was also bad.
The only way I can get it to work is to uninstall and go back to 12.0.77831 and then it works.
Please fix this!
Hello there, first of all thanks for this great program keeping as free.
I have black screeen problem too. I have lots of combination to eliminate this issue. But i didn't. I found some strange behaviour on windows 10.
When this issue occured, i used another remote program, which is google remote control software, shows same result as black screen.
Also when attach to vga monitor wit vga cable, while getting black screen everything works well again.
When i remove driver from system & disable vga card, it works well. when vga disabled, resolution is 800*600 only work with this situation well.
I think windows shut down the main monitor for this applications. I could'nt any solution by software side but i will do dummy vga connector for windows thinking as attached monitor.
I just report and share my exprience for better Teamviewer.
I hope you find good solution for this. Thanks for reading.
Latest updated windows 10 64 Bit
Intel Pentium G4400 Serie CPU(integrated intel hd Graphic 630 Vga)
Asus H270 Plus Mobo
8 gb ram
I have found quite a weird solution to this blackness software bug...
I have established a second connection to the same client - the system did warm me that there was already an active session to that remote client but I have OK-d the dialogbox and continued establishing the connection...
Guess what haqs happenned: the new (second) session did not have any blackenig issues. So I have closed down the first - blackened - session and I continued working on the remote PC as nothing had happenned.
Please check this on your environment as well...
Hope this helps,
I am running the latest 1709 version (Fall Creators Update) of Windows 10 opn both PCs.
Does not help for me, since 12.0.8something the problem remains to latest 13.0.5640. I've read at some other post it could have something to do with some GPU acceleration introduced around 12.0.7/12.0.8 update. That is most likely the problem as I have GeForce 4 Ti 4200 in this XP rig which does only support ancient OpenGL/DirectX versions. There are way more ppl like me with old HW, or newer HW and unsupported Linux graphics configurations etc.
It is very unsettling to see developers just pushing one version after another with lttle to no testing. Do you even have some theoretical knowledge of what might get broken with the new stuff, when you do not test it while pushing it to everbody through automatic updates? I kinda doubt so, as could be seen (especially if you test it the way you do security, as we all remember the huge leak few years ago).
You obviously still believe it works fine on all systems when you list no minimum system requirements anywhere (at least I found nothing - does it indeed work on 2000? 98? NT?). Well, guess what - it does not. Would be nice to return the non-GPU acceleration at least as an option in the app settings. And don't you ppl want some old HW for compatibility testing? Do you even have some lab for such purpose? I am just supplying one much greater corporation than you are with HW especially for this purpose. It makes sense for them when they only make so much money as many ppl use their product (working product ofc). I think it is the same with TV, so this is serious offer - you may think you know better, but with this attitude you'll be surprised when customers start leaving you. I'll definitelly switch to something else if this is not addressed soon - no reason for me to use broken application.
It's not their fault or their problem really. The problem is (at least for me) there is no screen connected or on/awake to make the grafics output a signal. I'm not sure if teamviewer can even do anythig about it from their end. I beleive the solution to this problem is with the OS or grafics cards/drivers. If you have a screen on while using teamviewer does it then work?
I think you are talking about totaly unrelated thing. Besides, from my experience, first VGA always works, only second and others should require dummy output to initialise. But that may have been improved with later drivers.
I'm also experiencing this issue. Try to connect to my mining rig and only see a black screen. The starnge thing is, as soon as I connect to the miner from my pc via RDP, the teamviewer App on my Android phone workes perfect. As soon as I dont use the RDP anymore from my PC the teamvierwer App will show the black screen again as soon as I try to connect. This is very frustrating because when I'm at home I can use RDP, teamviwer is used when I'm not at home, so no RDP active.
So funny to see all the miners here. I am a miner as well and I am getting the black screen too. Like others when I plug in a monitor and try to remotely connect it works fine. Kindly fix!
I have this same problem when connecting from a Windows 10 client to a Win 7 laptop host after rebooting the host. I noticed that if I leave the host laptop's lid open so that the screen comes on and reboot, I get the expected login screen instead of the black screen. Perhaps there's a setting on the host that needs to be changed? I have it set to "do nothing" if the lid is closed and it has AC power. For me it appears to be a problem only the first time I connect after the host has rebooted. The version on the client and host is 12.0.90922.
I have had a similar problem, which started 3 days ago. I have a Windows 10 Laptop which had the latest version of 12 installed. I was connected to a Windows 7 remote host that had Version 12 installed. Nothing changed on the remote host. I was able to connect to it via an iPad TeamViewer session and from a Windows 10 Desktop. The Windows 10 Laptop continued to display a locked black screen when connecting remotely to anything, even the Windows 10 Desktop mentioned.
I upgraded every host to Version 13. Problem persisted on the Laptop. I have had to downgrade to Version 11 in order for the Laptop to connect to remote sessions. Is there perhaps a known Windows 10 update which may have interfered with my Version 12 or 13 settings for remote display?
same problem here, but when i connect a monitor everything works perfect. So it has something to do with the VGA drivers, I think.
My host is not headless. It has monitors connected. It has something to do with the client side connection. I could connect between the other two machines fine. Host to host, so to speak. Just not from laptop client to remote hosts.
I have the same issue with one of our user's computer. After connection is established all I see in the remote window is black screen but on the computer that you are connected is working fine. I have tried uninstalling and reinstalling but same thing. Team version is updated to the latest version 13.0.6447. User's computer is running windows 7.
Is there any update on this? I tried the switching to the version teamviewer posted in the thread on both client and host but have the same issue when running headless.
Any update with a very clear solution would be greatly appreciated!
Unfortunately my elation that the problem is solved after reinstalling the suggested version and finding that it all works, has been short lived. The problem just re-appeared notwithstanding being on the suggested version.
Try turn on monitor. Yes, the phisical one. I discovered that solution yesterday. Maybe that overlaps with other problem with correct version byt definatelly helped in my situation.
I have laptop in the office and untill the screen was OFF I can see only black screen on RDP sessions I tried to launch remotely. I can work and do almost everything else, besides RDP. After turning screen ON and reconnect, RDP starts working like a charm :)
Only just started couple of days ago. I remote access from my Win7 laptop to Ubunutu 17.10. Black screen and nothing else. Tried pushing back to version 12 on Win7, didn't work. Worked fine few days ago.
I had a similar issue connecting from an older laptop with Windows 10 to a newer laptop with widows 10. I was using Teamviewer 13 on both laptops. The newer laptop could connect to the older one fine but if I tried to go the other way all I got was a black screen. I also noticed that if I minimized the top toolbar it just seemed to go up but left a grey streak. I found out that removing my Nvidia drivers & software cured this issue. I can now connect either way with no issue.
Iam running windows 10, and installed TV version 13. I tried install the solution provided, however its still does not work for me. Meanwhile, if I install older version such as TV 7, it works fine. But it would be give the problem as well if the host TV has a higher version. Does anyone knows the soluton? Thanks I appreciate it
As my previous P4 computer (865PE, GF 4) finally gave up, it was replaced with slightly newer one (Pentium D, 945G with HD 2400 XT) and now it works.
So I think this confirms what I thought, since the said version, this thing requires certain DirectX/OpenGL technologies for acceleration which old graphics lack (or you may lack SW support, like under Linux) so it does not work. I guess that in most cases you people have some obsolete graphics (though could still be good enough to draw desktop) while the development team is unable to specify minimum HW requirements and lie in telling it works everywhere. Though it is not surprising, they lie in so many things (like this **bleep** about comercial usage which pops at some of my computers stating I have only 5 minutes for connection - to ALWAYS disconnect me in 52-56 seconds!).
I have 6 pc’s all running newest version of TV i would assume since they where all installed in last 2 weeks. I login to them from my ipad which has newest version and 1-2 of them always have a black screen with the mouse pointer. The only fix i have found is sending the ctrl alt delete command and then waiting like 5-10min to connect again. Aometimes when i reconnect ctrl alt del blue screen menu is open and sometimes its not but either way i usually have a screen thats working. I would say it works 75% of the time after 10minutes weather I use ctrl alt del or not but using ctrl alt del seems to give it a slightly better chance of working after 10 minutes. Rebooting always solves it too but i dont wanna reboot computers all the time lol. Every computer has either a 1060, 1080 or 1080ti. Pretty sure every computer randomly encounters the black screen, all running windows 10
The reason of the black screen issue might be a video being played on the additional display (client side).
I have only 1 program running on any of the computers which is not video and none of the computers have a monitor connected
Hi, I have the same problem connecting from my iPad to my PC running windows 7 pro 64. My PC screen backgound turn black, I am prompted to grant access to the ipad and on the ipad I get the connecting to partner with the wheel going on for ever. I have this with version 12 and 13.
This solved the problem for me. I uninstalled Duet Display, rebooted, and then my Teamviewer is back to normal. Thanks for the great suggestion!
I am having the same problem between my PC and Mac that sit in France, and a Mac that sits in the US and that was just updated to v13. Is there a seafile link for us that might do the same trick as for those guys last year?
Thanks in advance,
Is there any fix for this for people using TeamViewer 13?
Please install the version from the following link on both sides and try it again:
Mac user chiming in. Have had the same problem (recently) on an iMacPro with 2 peripheral monitors. I keep the machine running but put the monitors to sleep via: System Prefs>Desktop/Screen Saver>Hot Corners> Put Display to Sleep. Now I too get the black screen log in issue, whereas befotre it was fine. It only happens when the monitor is alseep vs on screen saver. I have to use this option as the iMacPro does not have a sepaarte power button for the display of this all-in-one unit. Any fixes or work arounds for me? Using V13 on Desktop and iPhone currently.
I don't know why I had a black screen, and I don't know why it has been replaced in the meantime by a locked screen. How to work around that one: I "lock" the Mac, which interrupts the connection obviously. After reconnecting to the Mac I get the login screen, I log in with the pass word, and everything works fine from there.
I have the same problem. Both Macs running 13.2.14328. Used to work fine but now only black screen and I can't see any way of fixing it. I have a signficant (for me!) invoice waiting for payment for business use of TeamViewer but see no point in paying it if this product no longer works in the way I need it.
Ditto. I'm another Mac user. I have 2 screens on my MacPro running the latest version. It shows a black screen when I try and connect remotely from any other account device.
Interestingly, when I try and connect via VNC, I get the same result. Something is broken somehow...