Issue with Windows Technical Preview build 9879

[exile183]

So, Microsoft just rolled out the latest build of "Windows 10" aka Windows Technical Preview Enterprise build 9879.  And it seems to have broken Teamviewer.

Not sure what the correct nomenclature should be, so I'm gonna call the machine I'm trying to remote into the "host" and the machine I'm using to remote into the host the "client".  If that's incorrect, please let me know.

Host machine is an HP laptop (Elitebook 8530p), using the afore-mentioned Windows 10 build.  Client machine is (I'm not kidding) a Commodore 64 Extreme, i7 CPU, running Windows 8.1 Update.  I use this client to manage several machines in my home as well as provide remote support from some technically-challenged friends

Anyways, prior to yesterday, all of my hosts and clients were running the latest 9.x version of Teamviewer.  Then when this happened, I decided to try upgrading to Teamviewer 10 beta on both this HP laptop host as well as my C64 client.  The results were THE SAME using either.

This manifests in one of two ways, depending on *WHEN* I connect to the host:

1) If the host is displaying a lock screen, and I connect, everything works normally insofar as I see the lock screen on the client, and I can sign in (and see the sign in screen).  However, once the host completes the logon and goes to the desktop, my client screen just goes black.  I can move the mouse around and keyboard input seems to work, but I've got a black screen.  (I've checked and "show black screen" is not selected).

2) If the host is already at the desktop when I connect to it with the client,
a) The client tells me it's unable to capture the screen at the moment, and
b) The display begins flickering like crazy on the host

(Sometimes, the flickering will eventually stop after a minute or two - resulting, again, in a black screen on the client).


Obviously, Windows 10 is very beta (actually more like alpha) software and I can't expect Teamviewer to have a fix for this any time soon (although it'd be nice if the Teamviewer 10 Beta came up with a fix soon) - I was just hoping that somebody here might have a suggestion for some sort of workaround.  This isn't critical YET as this particular laptop is a test machine only, but I've got Windows 10 on my tablet and on my girlfriend's desktop, and sometime in the next week or so, this update to Windows 10 is going to roll out to those devices (you can't stop it).  The tablet is in the same room with me so, again, no issue, but my girlfriend frequently needs my technical support.....

[Admin]

This is interesting, i cant provide a workaround and support for W10 may be far down the line.
 It may be worth starting a support ticket to see what kind of response you get:
http://www.teamviewer.com/en/help/createticket.aspx

and or posting this on the Teamviewer facebook page:
https://www.facebook.com/teamviewer

[spartacodes]

Yes i have this issue too. :-( I thought i was the only one and cant find any info. I have had this working with teamviewer for quite some time. and now microsoft update broke something. i found a solution for me but it sux. I have to teamviewer to another computer then remote desktop to the one with windows 10. Ugh it sucks but seems to work pretty decent. i was at work and needed my home machine.

[PatrickG]

This resolved the issue for me:

As workaround, you can create the registry Key "DisableDuplicationAPI" as Dword and value 1 under HKEY_LOCAL_MACHINE->SOFTWARE->WOW6432NODE->TEAMVIEWER on the Windows 10 computer. After a restart of the service TeamViewer (under Services.msc), you should be able to reconnect without any issue.

[exile183]

This resolved the issue for me:

As workaround, you can create the registry Key "DisableDuplicationAPI" as Dword and value 1 under HKEY_LOCAL_MACHINE->SOFTWARE->WOW6432NODE->TEAMVIEWER on the Windows 10 computer. After a restart of the service TeamViewer (under Services.msc), you should be able to reconnect without any issue.

I can find HKEY_LOCAL_MACHINE and then SOFTWARE but now WOW6432NODE under that....   (It's a 32-bit machine, might that be why?)

[exile183]

This resolved the issue for me:

As workaround, you can create the registry Key "DisableDuplicationAPI" as Dword and value 1 under HKEY_LOCAL_MACHINE->SOFTWARE->WOW6432NODE->TEAMVIEWER on the Windows 10 computer. After a restart of the service TeamViewer (under Services.msc), you should be able to reconnect without any issue.

OK, just tried it on two 32-bit machines.  There is a Teamviewer folder under HKLM->SOFTWARE (omit the WOW6432NODE part).  Following the rest of these instructions MOST DEFINITELY resolved the issue for me on both of them.  AWESOME!  Thanks Patrick!