Black screen after updating to Winver 1803

When connecting to machines I've had no problems connected to for years, the screen is now just a black box after updating to Windows 10's newest "feature" update (winver 1803).

Confirmed all three machines (this one and the two remote PCs) are using the most up-to-date version of Teamviewer. I updated one of them to Winver 1803, stillsame issue.

Find more posts tagged with

Accepted answers

zsuraski

Yes - I managed to thoroughly solve it! At least on my system the problem is now 100% gone.

After ping ponging with Intel, blaming the HD 4600 driver for this - and them saying they tried to reproduce it to no avail (https://communities.intel.com/message/553064) - I finally managed to get to the bottom of this issue.

Now, I'm not sure whether this is the same root cause that's affecting everyone here - but I suspect if it's not identical, it's probably similar.

For me - the root cause was an app called Duet Display - which allows using an iPad as a secondary display on Windows. Long story short - as soon as I uninstalled it - the TeamViewer issue (and several other similar issues in other apps) went away.

If you have Duet Display laying around - try uninstalling it and see what happens (disabling the Duet startup process is NOT enough). There are also several other similar apps to Duet - so if you ever installed one of those, try uninstalling them and see what happens.

Hopefully this will help some people here.

Good luck!

Julia

Hi all,

Thank you for your patience. Today we published a new "InsiderBuild" with a new option which should fix the problem. You can activate the InsiderBuild within TeamViewer under "extras - options - advanced" but please be aware of the fact, that InsiderBuild can contain bugs, because they are just Previews (find out more in our Knowledgebase article).

When the InsiderBuild is installed you can navigate to "extras - options - advanced" until you find the new setting "Disable hardware acceleration" under "more". Please tick the option and check if you still see the black screen.

This option will also be in the next official release for all people, who do not want to install the InsiderBuild.

All comments

zsuraski

Now, I'm not sure whether this is the same root cause that's affecting everyone here - but I suspect if it's not identical, it's probably similar.

Hopefully this will help some people here.

Good luck!

Julia

Hi all,

This option will also be in the next official release for all people, who do not want to install the InsiderBuild.

Mark_W

I have this problem too.

A workaround: Click View > Screen Resolution, and change to any resolution other than the current one. Then it should work as normal, and you can also change back to the original resolution.

Hope that helps!

Julia

Hi all,
Thank you for informing us - we will have a look at this and keep you updated.
Cheers

zsuraski

First off, I believe I have some good news. There is a *REAL* workaround for this issue, and I can confirm that it's working fine for me on an Intel HD 4600 machine. No, it's not asking TeamViewer to refresh the screen or anything of the sort, and it doesn't involve updating drivers (even though I did that too, and it is possible[*] to install the latest Intel driver on OEM machines like Lenovo's or HP's, but it doesn't solve that problem).

The solution is simple:

- Right after you connect to the remote system and experience the blank or otherwise corrupted view - hit Ctrl-Alt-Del to access the Windows security screen, and then hit ESC or Cancel to exit it.

That's it - problem solved - the TeamViewer window will be redrawn, and from that point onwards - everything seems to work fine (you don't have to continue doing it or anything of the sort; The window will be properly drawn until you disconnect from the remote computer).

Yes, it's annoying to have to have to use this workaround - but honestly, it's not that much of a big deal to do this once per connection, and it's certainly much preferable to practically not being able to use TeamViewer at all in the relentlessy pushed 1803 update.

TeamViewer folks - perhaps this can help you in some way to fix this problem outside the realm of a particular driver?

Zeev

[*] https://www.howtogeek.com/343287/how-to-fix-the-driver-being-installed-is-not-validated-for-this-computer-on-intel-computers/

SSMCPA

I am using TeamViewer version 13 so it isn't just a Teamviewer 12 issue. This happened on an older laptop I was using a while ago and the fix was to uninstall the nvidea drivers. When it re-occured after the next major Windows update I had to re-install & then uninstall the nvidea drivers again. This got it working again. The issue is now happening on my newer laptop now but it doesn't have nvidea drivers. I find I can use the Windows Teamviewer Remote Control app available on the Windows Store to remote control successfully. It is not a full featured app so if I need to do file transfer or anything else then I need to open a second connection using Teamviewer 13 and even though I can't see the screen I can still use the file transfer and other features.

laialexander

Do you know how much I love you?? Your reply reminded me that I tried out the Microsoft Store version of the app and it WORKED!! I could have the tool working as expected, and I could have access to all of my hosts and friends' computer now!

It worked, although not the original full version but at least it worked! I do really very appreciate your help, and I do hope I could buy you a coffee to express my appreciation to you!

Thank you thank you thank you!

Alexander Lai

sunnytsoi

It works for me! thanks so much. I have been studying this issue for over 10 hours.

dube920

Just as a note, I'm having similar problems with other programs (particularly Snagit just being a gray blob) after the Windows feature update. So that's definitely the crux of the issue.

Mark_W

Discovered another way - press "refresh screen" under "view options" in the view menu. See if this works...!

przeban

I check Team Viewer on may other updateted computers (all with Intel Graphic only) and everythink work fine. I have problem only on my XPS 15 2014 laptop with Intel and Nvidia graphics. I think the problem is in Nvidia card or cooperation between Intel and NVidia.

I am IT guy if you need person for some tests I will be happy to help

waynedc

This InsiderBuild with Hardware Acceleration turned off and Duet installed fixed the issues for me.

Prior to the InsiderBuild, I had to uninstall Duet to avoid the blank black screens in Teamviewer.

Thank you,

Wayne

przeban

workaround

the problem is caused by Intel drivers ( in my case HD Graphics 4600) . turn off the Intel Graphics device in your computer and the Teamviewer will work properly

ericortner

Having the same issue with WIndows 10 after 1803 update with Nvidia Geforce 1080GTX video card. TeamViewer works like normal if I have an external display connected, in my case via HDMI. I've updated to the latest Nvidia drivers and that did not resolve the issue either.

zsuraski

You're very welcome.

Take a look at the last message at https://communities.intel.com/message/551697 - I actually detailed how I found it...

DavidIQ

Interestingly enough this seems to have been the source of my problems with Visual Studio and BlueStacks as well. Removed Duet now since I'm not even using it. Thanks!

zsuraski

Same here - it solved issues I was having with Steam (local streaming), Yi Home security camera, Microsoft Mouse and Keyboard Center (go figure!) and a couple of other apps. It was (is) a pretty nasty bug. It's reported to both Intel and Duet, so hopefully between the two of them it will be solved for people who actually need Duet.

dube920

Can confirm, worked for me too! Thank you!

cethkalexander

It will be much informative if the release note or change log could be released as well, so that we could consider if we should take the risk of installing the early release version of the update.

zsuraski

You're very welcome! This was one tricky bug to figure out. Glad it seemed to solve it for everyone who experienced it!

Zeev (from Israel

zsuraski

Julia - not sure if you noticed but it seems that the root cause for pretty much everyone involved was Duet Display (in conjunction with Intel display drivers). So far there were around 7 people who confirmed that this was the same root cause for them...

Perhaps this should go into the Team Viewer knowledge base.

I also reported this to both Intel and Duet, so I believe that sooner or later they will solve it with a new update.

DavidIQ

I doubt disabling HWA within TeamViewer will fix the clash with Duet. I had disabled HWA globally on my machine and that did not take care of the black screen, although it did correct the issues I was having with the other applications. Removing Duet was the ultimate solution to fixing TeamViewer. Re-enabling HWA after removing Duet still allowed the other applications to work properly so the real source of the problem is Duet.

RayLeRital

**bleep** DUET!

I have not been able to use TeamViewer for months, and I could never imagine that the problem was caused by this app...

As I uninstalled it, everything works fine.

And not only TeamViewer, also some other complatibility problems with some apps have been solved.

Thank you very much!

Betelgeuse

I have this problem when connecting to Intel HD 4000 graphics, BUT after about 10 seconds the screen comes on.
Another problem though is that the Windows start menu (all programs) gets very small and it does not work on clicking items. Also when using Windows Settings scrolling will not work. In other places scrolling works fine.
When remoting other computers everything works fine, so I have the feeling it has to do with Intel graphics 4000

zhitao

I've been having this problem for a long time, and uninstall Duet Display really helps! Thanks a lot!

DeeX

I have seen you link this "solution" on many threads that have the same topic.
However, I can assure you this is a new thing presumably with Windows itself.
I have been using TeamViewer for years on the same workstations and only recently have I ran into this problem. There has got to be a solution to get the graphics cards to not go to sleep.

FCC

Amazing work, thanks a lot. That Duet software was the cause of my blackscreen on Teamviewer. Those guys at Duet never really got their software 100%.

Peril

I tried everything else, including the development builds - deleting Duet is what did it for me.

salsabor

Thanks for your post, I had the same problem like you and after to receive the last version of W10 1803 compilation 17134.137, the Teamviewer 13.1.3629 doesn't works showing a black screen when connecting.
I tested severals ways to repair it like to uninstall the VGA drivers and it works OK too, but when the VGA receive the driver automatiacally, it not work again. Other temporally solution was install the version 12.0.77831.0, but I never imagine that the reason in my case was the DUET DISPLAY from Ipad.
By your post, I could solved and I would like to give you thanks since I was so mad with this topic.

Best regards,

Salsabor from Spain

Julia

Hi zsuraski,

I really appreciate your input here and your workaround.

Our development had a look at this issue together with a lot of customers who had the same problem.

We also made some tests with these customers and the new option within TeamViewer was especially developed for this behavior. Our customers already confirmed during the tests, that this option will solve the problem.

Thanks for your suggestions to create a Knowledgebase article about it and indeed - I can confirm that we will publish a Knowledgebase article about the new option within TeamViewer in the near future.

Cheers,