Posted by Vibes
Digon

Windows 10 does not look to start service until logon

Hi I have just upgraded a remote computer to Windows 10 version 1703 OS Build 15063.138

After the upgrade I was unable to view it in my list of available computers. I used TeamViewer to another PC and remote desktop to the upgraded PC, as soon as I logged on it became visible. I then rebooted the upgraded computer and it again disappeared. Next I hopped back onto it and uninstalled TeamViewer and reinstalled. Same outcome. Service is set to auto and is running when I see it, but by then I have logged on to the PC. It looks as if the service is now not triggered until logon.

Any ideas? Thanks in advance

1 Accepted Solution

Accepted Solutions
Posted by TeamViewer Staff
TeamViewer Staff
Solution

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

Hi all,

We published an official release today - this release includes a fix for the problem we discussed in this thread.

Please install the new version and send us your feedback.

Cheers

Julia
Senior Support Engineer - 2nd level Support
Did my reply answer your question? Accept it as a solution to help others.
Find this helpful? Say thanks by clicking on the Thumbs Up button.

View solution in original post

152 Replies
Posted by Vibes
Digon

Re: Windows 10 does not look to start service until logon

Just a quick update. I rolled back the windows 10 creators update and all working as normal. I would be interested in hearing if anyone else has this problem. IE the computer has be logged on to allow Teamviewer to connect..

Posted by JedenTag
Trigon

Re: Windows 10 does not look to start service until logon

Posted by Vibes
Digon

Re: Windows 10 does not look to start service until logon

Thanks JedenTag

Looks to be the same problem. If this is correct then the solution of rolling back versions is only temporary as this major Windows 10 will still be forced on us.

Again, if this was not an isolated case of a bad upgrade then Microsoft have altered something that does not allow the dependencies to be met so that the teamviewer service can run on startup. If so I look forward to Teamviewer 13

 

Posted by Vibes
Digon

Re: Windows 10 does not look to start service until logon

I have tried this on a second computer, however this time I installed Microsoft KB4013214 prior to the upgrade. Teamviewer works on this device without problem.

For me the solution is not to upgrade to Windows 10 V 1703 without first running KB4013214

Posted by mandfmike
Henagon

Re: Windows 10 does not look to start service until logon

How do you roll it back?

Posted by mandfmike
Henagon

Re: Windows 10 does not look to start service until logon

This didn't work for me.

Posted by Vibes
Digon

Re: Windows 10 does not look to start service until logon

Settings>Update and Security.Recovery>Go Back to Previous version of Windows 10

Posted by mandfmike
Henagon

Re: Windows 10 does not look to start service until logon

Thanks but that option is greyed out on my machine..

Posted by Vibes
Digon

Re: Windows 10 does not look to start service until logon

Hi

My silver bullet in all this is http://www.thewindowsclub.com/windows-10-media-creation-tool-create-installation-media-upgrade

If you have not used the media creation tool then its fair to say it looks at your windows and runs the very latest version over it. including all the updates.

Also this is good if you have a window 7 or windows 8 pc with inbedded license, it will still upgrade for free.

Never tried it on a remote PC, but fair to say it never failed me doing it locally

Posted by karsten
Henagon

Re: Windows 10 does not look to start service until logon

Hi,

I´ve the same problem, but i´ve no chance to rollback or to install the kb4013214 , because i´ve installed with the media creation tool on an a blank hd.
Additional i can´t reconnect after logout a windows session.

Posted by Vibes
Digon

Re: Windows 10 does not look to start service until logon

Hi Karsten

As I am also trying to discover the exact problem remotely I am having a little difficulty with access.

My situation is a follows:- Home location, small network with domain controller. Computer on the domain is still not working, laptop stand alone working.

I am trying to narrow this down a bit more, so your input will be of great help.

1/ is your remote pc on a network

2/ if you try to do updates do you get an error

I am just rebuilding a PC that is causing me problems, I will keep it out of the domain and see if I can get it working. Sorry I can't help more

Posted by TeamViewer Staff
TeamViewer Staff

Re: Windows 10 does not look to start service until logon

It looks like the Windows 10 update changed some WiFi settings which caused it to not connect until a user is logged in.

If you are using a user + password to connect to your WiFi network, this is how to change it:

  1. Open the "Network and Sharing Center"
  2. Click on the label for the wireless network connection (somewhere on the right)
  3. Click on "Wireless Properties"
  4. Open the "Security" tab
  5. Click on "Advanced settings"
  6. On the first tab ("802.1X settings") in the dropdown at the top, switch to "user authentication"
  7. Click on the "save credentials" button
  8. Enter your username + password (for domain users, don't add the "domain\" part, just the username is enough)
  9. Click on Ok and close all dialogues. This should disconnect shortly from the WiFi network and reconnect again.

If the WiFi connection doesn't work after changing the settings, you might have to go to the Wi-Fi settings in Windows 10 -> "Manage known networks" and remove the entry there. I wasn't able to find another way to get to the wireless properties dialog if it was not connected.

Maurice
Software Developer
Posted by karsten
Henagon

Re: Windows 10 does not look to start service until logon

this is my configuration:

  • laptop with a blank HD, Installation win10 1703 with media creation tool
  • domain join, network access both LAN or Wifi
  • teamviewer host 12 with recommended configuration
  • no errrors at updates
  • no reconnect after logout/reboot

second try, same laptop: 

  • blank HD, Installation win10 1607 with media creation tool
  • Teamviewer 12 Host with recommended configuration
  • upgrade 1703 with "Windows 10-Upgrade-Assistent
  • network access both LAN or Wifi, no domain join
  • no errrors at updates
  • same problem as above
Posted by mandfmike
Henagon

Re: Windows 10 does not look to start service until logon

 


@Maurice wrote:

It looks like the Windows 10 update changed some WiFi settings which caused it to not connect until a user is logged in.

If you are using a user + password to connect to your WiFi network, this is how to change it:

  1. Open the "Network and Sharing Center"
  2. Click on the label for the wireless network connection (somewhere on the right)
  3. Click on "Wireless Properties"
  4. Open the "Security" tab
  5. Click on "Advanced settings"
  6. On the first tab ("802.1X settings") in the dropdown at the top, switch to "user authentication"
  7. Click on the "save credentials" button
  8. Enter your username + password (for domain users, don't add the "domain\" part, just the username is enough)
  9. Click on Ok and close all dialogues. This should disconnect shortly from the WiFi network and reconnect again.

If the WiFi connection doesn't work after changing the settings, you might have to go to the Wi-Fi settings in Windows 10 -> "Manage known networks" and remove the entry there. I wasn't able to find another way to get to the wireless properties dialog if it was not connected.


What about LAN connections? I have 5 computers on my domain that won't connect to teamviewer until a user logs in, because I installed Win10 SP 1703. I can RDP the machines, then I'm able to use teamviewer to get in, but I don't want RDP turned on because of the security risk. Thats why I pay for teamviewer. Speaking of teamviewer, they should be trying to resolve this issue. Nothing I have read here worked for me.

Posted by Vibes
Digon

Re: Windows 10 does not look to start service until logon

Hi Maurice

My configuration as stated before is a Windows 10 PC on a network, hard wired via the LAN port. Once upgraded this is no longer visible after a re boot until local logon.

I have a laptop connected via WIFI onto the same network but not connected to the domain. This works fine without changes to the wireless card

Both units upgraded to latest version of windows.

I am able to connect to the laptop and use remote desktop to log onto the PC, once logged on it is visible to TV12

Posted by TeamViewer Staff
TeamViewer Staff

Re: Windows 10 does not look to start service until logon

I wasn't able to reproduce this problem for LAN connections yet. All I can tell from other users is that the TeamViewer service cannot connect while there is no user logged in. As for why that's the case, I don't know. Will investigate further...

Maurice
Software Developer
Posted by vabch
Photon

Re: Windows 10 does not look to start service until logon

I have the same situation going on With Windows 10 Creators update and teamviewer . I think the creators update is having problems starting certain programs that are set to automatically start and this is in general(there are two other programs where they could not start the service - Mainstream programs. I fixed by delaying the start on one of them( the other one I still have to try it -not sure if that would work here) . Try this start windows 10 and start teamviewer , then close down machine and try teamviewer. Its not so much the service , but the whole program is not being started to even start the service.This is hardwired,not wireless.  Thanks

Posted by Vibes
Digon

Re: Windows 10 does not look to start service until logon

I don't think this should just be a "Community" item to look at, this should now be down to the developers.

I am lucky, one PC I did a rollback on, one PC I used the media creation tool and it downgraded the PC to the older version. (I presume this is due to location as previously it was mentioned that the media creation tool was used to make the upgrade CD) This did wipe the PC but as most items are rolled out by the server the rebuild went well. The laptop is working well on the new windows with TV12, however as stated before this is wireless and not part of the domain.

I have activated the "Defer Feature Updates" option on my computers and await a real solution before trying an update again

Posted by TeamViewer Staff
TeamViewer Staff

Re: Windows 10 does not look to start service until logon

Hi all,

Our development is already aware of this issue.

We will inform you when we have more information

Julia
Senior Support Engineer - 2nd level Support
Did my reply answer your question? Accept it as a solution to help others.
Find this helpful? Say thanks by clicking on the Thumbs Up button.
Posted by Wiedholz
Henagon

Re: Windows 10 does not look to start service until logon

Ich habe das gleiche Problem, rolle grade das 1703 Upgrade in der Firma aus. Testgruppe mit ca. 30 Rechnern hat das Problem wie oben beschrieben.

Bitte Informieren Sie mich auch, wenn eine Lösung für das Problem vorliegt.

Posted by hubran
Henagon

Re: Windows 10 does not look to start service until logon

Any update on this? Even with the latest version v12.0.75813 installed today I see still the same behavior, the remote computer only shows up in the TV Computers and Contacts list after loging on via RDP.

Posted by mandfmike
Henagon

Re: Windows 10 does not look to start service until logon

No update yet. I use teamviewer 11. And can't access computers that have win10 SP 1703 until logged in or using RDP first. I have 65 devices I use teamviewer for unattended access. I did get a reply from Teamviewer Staff below. But I can't wait to long for them to fix this. I'm getting ready to test logmein on these computers and see if it works.

 

Hi mandfmike,

Julia (Staff) posted a new reply in TeamViewer 12 on 04-20-2017 07:59 AM :

Re: Windows 10 does not look to start service until logon

Hi all,

Our development is already aware of this issue.

We will inform you when we have more information

 

TeamViewer Community sent this message to miketapp@mandfbankhs.com. You are receiving this email because a new message matches your subscription to a topic.

 

Posted by Bauer
Digon

Re: Windows 10 does not look to start service until logon

I have the same problem, currently using TeamViewer 10. Any connection via contact list or a teamViewer ID is not possible unless someone is logged in.

I noticed though that I am still able to connect if the computer is within our LAN, it does work when I try to connect to a IP address or DNS name. So doesn't seem to be a problem of the service itself running on the computer, more likely a communication issue between the client service and the TeamViewer server. Maybe this info is of help for someone who uses TV also for internal support as well...

Posted by Wiedholz
Henagon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

Wahnsinn. Bauer Sie haben Recht.

Hatte ich noch gar nicht getestet. Ich nutze TeamViewer 12 (aktueller Build) und kann auch eine Verbindung über die IP-Adresse oder den DNS-Namen herstellen.

Vielen Dank für diese Info. Damit kann ich ohne größere Umwege Arbeiten bis das Problem vollständig gelöst wird.

Posted by Oleksandr
Electron

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

Last version TV, Windows 10 Pro 1703 - same problem. Not connected without logon

Posted by DomLan
Heptagon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

Hi to all,

An information: your systems are equipped with the patch KB4016240 (build 15063.250) post Creators Update?

From change-log: Fixed a bug that prevented Lock Screen from being disabled through Group Policy in Professional Edition. Fixed a problem with the Windows Forms configuration options that cause a startup anti-virus software block.

Thanks in advance.

Regards

Domenico Langone
MCSD: App Builder
Posted by Bauer
Digon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

Yes, we've tested patch KB4016240 and the result is that it behaves even weirder.

If my target computer is within our LAN, it does not make a difference. It's the same as before that patch, connection via IP/DNS is possible, via address book or Teamviewer-ID it is not. The computer icon in the address book only turns blue once someone logs in locally. Funny thing is, after logging out locally, the icon now stays blue, suggesting the remote computer is still reachable, yet I cannot connect anymore.

OTOH, if my target computer is outside our LAN, it seems to be back to normal. The computer icon in the address book turns blue once the TV service starts and connection is possible.

I would still prefer though to be able to connect to internal mobile devices with the help of the TV-ID, since we use several sub-domains and always stating the full DNS name is a bit annoying...

Posted by TeamViewer Staff
TeamViewer Staff

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

@Bauer: Is the target computer the same computer? And if it's outside your LAN, is it connected through WiFi or LAN? If that really makes a difference I'd like to know what exactly the difference is in network infrastructure that would cause such a problem.

Maurice
Software Developer
Posted by Bauer
Digon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

Ok, I did a few tests. The guest PC I used is always within our LAN, wired. The host PC is a win 10 rel 1703 notebook, its TV-ID is added to the contacts list. The host is able to connect via one of the following methods: wired (LAN), wifi (LAN) or wifi (3G modem, separate direct internet access)


Host is in LAN (wired or wifi):
As long as nobody has logged in on the host after a reboot, connection is only possible via IP / fully qualified DNS name. TV-ID does not work, icon in contact list is black.

User has logged in, icon turns blue immediately, all access methods work.

Without KB4016240 the icon turns black after logging out
With KB4016240, once the user logs off, the icon stays blue, but access via ID doesn't work anymore. IP/DNS still work, connection is established immediately. Even after waiting for 6 minutes, the icon stays blue. It takes about 2 minutes to turn black after I completely disconnect the host from any network.


Host is outside of LAN (3G over wifi):
Host is showing expected/desired behaviour, icon turns blue right when the service starts after a reboot, TV-ID access does work and keep working.


Just to state the obvious, for all our other Win7 hosts or hosts with Win10 up to 1607, access was (and still is) possible by IP or TV-ID.

Posted by infoworxx
Henagon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

Hello,

same problem here; Win 10 1703, KB4016240 installed, connected with wired LAN Port (not Wifi!), no Teamviewer accessible until the user logs on.

I can provide a test-machine(s) for the teamviewer support team.

Sebastian

 

Posted by TeamViewer Staff
TeamViewer Staff

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

Hi,

I would like to inform you what we know so far and where exactly we are on this problem.

First, I would like to dispense some false information that I read here in this thread:

  1.  The problem is not about the TeamViewer service startup not working or about incorrect service settings. The service starts fine after the PC is booted. You should not enable the interactive mode for the service as this can prevent the service from running on some PCs.
  2.  The Windows 10 Creators update doesn't always break TeamViewer. Actually, we are still not able to find a single device here that had any problems after the Creators update, which makes this problem very hard to analyze or fix.

 So what is the problem?

As far as we can tell the TeamViewer service cannot open outgoing TCP connections while there is no user logged in. And if that doesn't work you'll not see the device as “online” and won't be able to connect to it using the TeamViewer ID. Incoming connections on the other hand are completely fine, which is why connections using the IP or hostname work. Existing connections will stay alive if the user logs out, and that's why devices stay online in TeamViewer. However, connecting to it will not work as in this case the TeamViewer service would try to create a new outgoing connection.

This all doesn't seem to be a bug in TeamViewer and therefore we also probably cannot fix it. It's much more likely that this is a bug in Windows and therefore we assume it might be a Microsoft issue.

Which devices are affected?

At first, we only received reports from users with Lenovo or Fujitsu devices. However during the last few days, we also received some reports about devices from HP, Dell and ASUS. This means that in general there doesn't seem to be a common factor on the manufacturer side. We assume that the fact that the issue occurred only on devices from two manufacturers at the beginning might be related to the rollout strategy for the Windows Creators update.

The hardware and software on the devices is also very diverse, so we cannot pinpoint it to anything more specific there either. Right now, our best guess is that it's a setting on those devices or in the network they are connected to that is causing this problem. But we don't have enough data to see what exactly that setting could be.

What might help to fix this problem?

So far, we have received three cases where a user reported that something fixed the problem.

We did not find USBPcap on any of the other devices that are affected by this problem. Also, the Windows update that was installed is also installed on all the other device that still have the problem. Most users also didn't use a proxy to connect to the Internet once they were logged in. So, while this might work for some other people, none of this sounds like the real solution.

What did we do so far?

  • We checked and compared a lot of support collector data from different users. As stated above so far there's no real common theme anywhere.
  • We inspected our network code to see if anything there might be wrong and could explain the errors we see, but could not find anything.
  • We tried to raise this issue with Microsoft, yet so far they are not aware of any problems. We will continue to stay in touch with them as we believe this might be where the issue may be raised.
  • We set up different PCs and notebooks with Windows 10 + Creators update in different network environments, but so far all of them work as expected. We still have a few notebooks left though and will continue to try to reproduce it here.

How can you help?

In order to solve this issue as quickly as possible we kindly request you to support us with your help:

  • Please post this problem in the Windows 10 feedback app from the PC where it occurs. This helps us to broaden the awareness about this issue on the Microsoft side so that they also start investigating it. It can also give Microsoft some data for the PCs that are affected by it that we don't have yet.
  • If you can provide some additional information about your network settings and infrastructure that would also help:
    • Are the PCs in a domain (I think that was already answered as "doesn't matter")?
    • Did you configure the PCs in any special way to be able to join your network or do you have anything in your LAN that blocks unknown devices?
    • Please check the firewall (local and hardware firewall, if available) for error messages / ports being blocked / etc. for destination *.teamviewer.com. Is there anything being blocked? And if so, why?
    • Are there any port limitations for local ports of outgoing connections (for example: only allow port starting at 32765, or similar)?
    • Please check the output of the following two commands and post them here if they don't match the expected values:
      1) netsh int ipv4 show dynamicportrange tcp
      2) netsh int ipv4 show excludedportrange tcp
      The first command should show a starting port of around 49152 and a total count of about 16384.
      The second command should show an empty list.
    • Run autoruns (https://technet.microsoft.com/de-de/sysinternals/bb963902.aspx) and check the Winsock Providers and Network Providers tab. Is there anything in there?

Thank you very much for your collaboration and understanding!

Maurice
Software Developer
Posted by kevinleesmith
Henagon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

 fyi I am having the same issue on windows 7 ultimate 64bit - so is suspect it has nothing to do with windows 10.......

Posted by kevinleesmith
Henagon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

To be a little more clear....

 

I have a win10 and a win7 machine, both running the same version of teamview (12.0.77242) and both having "start teamviewer with windows" and "Full access control when a partner is connecting to the windows logon screen"

If i try to connect to the win7 machine (that is sitting at the windows login prompt) from the win 10 machine it CANNOT connect.

 If i try to connect to the win10 machine (that is sitting at the windows login prompt) from the win 7 machine it DOES connect.

 

 

Posted by kevinleesmith
Henagon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

I downgraded the teamview on the win7 machine and that did not fixe the problem -

 

so its like its not a win 10 problem and its not a teamviewer problem - so it must be a config problem ???

Posted by JedenTag
Trigon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

I haven't been having any trouble with TeamViewer 12 and Windows 10 when using this script linked here:

https://community.teamviewer.com/t5/TeamViewer-12/Unable-to-connect-to-TeamViewer-ID-LAN-only/m-p/62...

Add the following outgoing firewall rules in Windows 10... you can do so by running the following in an elevated PowerShell window:

New-NetFirewallRule -DisplayName "!Allow Outbound UDP svchost.exe" -Enabled True -Direction Outbound -Profile ANY -Protocol UDP -Program "C:\WINDOWS\system32\svchost.exe" -Action Allow -Description "Allows Outbound UDP svchost.exe."
New-NetFirewallRule -DisplayName "!Allow Outbound TCP TeamViewer_Service.exe" -Enabled True -Direction Outbound -Profile ANY -Protocol TCP -Program "%ProgramFiles% (x86)\TeamViewer\TeamViewer_Service.exe" -Action Allow -Description "Allows Outbound TCP TeamViewer_Service.exe."
New-NetFirewallRule -DisplayName "!Allow Outbound 5938 UDP TeamViewer_Service.exe Local Port" -Enabled True -Direction Outbound -Profile ANY -LocalPort 5938 -RemotePort ANY -Protocol UDP -Program "%ProgramFiles% (x86)\TeamViewer\TeamViewer_Service.exe" -Action Allow -Description "Allows Outbound TeamViewer_Service.exe communication via 5938 UDP."

 

Posted by Mulsambe
Digon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

Here are additional information from my PC :

  • Are the PCs in a domain (I think that was already answered as "doesn't matter")?
    • NO
  • Did you configure the PCs in any special way to be able to join your network or do you have anything in your LAN that blocks unknown devices?
    • NO
  • Please check the firewall (local and hardware firewall, if available) for error messages / ports being blocked / etc. for destination *.teamviewer.com. Is there anything being blocked? And if so, why?
    • Nothing of this type
  • Are there any port limitations for local ports of outgoing connections (for example: only allow port starting at 32765, or similar)?
    • No limitation
  • Please check the output of the following two commands and post them here if they don't match the expected values:
    1) netsh int ipv4 show dynamicportrange tcp
    2) netsh int ipv4 show excludedportrange tcp
    The first command should show a starting port of around 49152 and a total count of about 16384.
    The second command should show an empty list.
    • First command OK
    • Second command : shows port 19455-19455
  • Run autoruns (https://technet.microsoft.com/de-de/sysinternals/bb963902.aspx) and check the Winsock Providers and Network Providers tab. Is there anything in there?
    • Network providers : empty
    • Winsock providers : shows 2 entries :
      mdnsNSP    Bonjour Namespace Provider    Apple Inc.    c:\program files (x86)\bonjour\mdnsnsp.dll   
      mdnsNSP    Bonjour Namespace Provider    Apple Inc.    c:\program files\bonjour\mdnsnsp.dll   
Highlighted
Posted by chrullrich
Digon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

Well, I think I know what happens, but I have no idea why.

This is an excerpt from a WFP event capture on 1703:

<netEvent>
    <header>
        <timeStamp>2017-05-09T22:12:26.351Z</timeStamp>
        <flags numItems="9">
            <item>FWPM_NET_EVENT_FLAG_IP_PROTOCOL_SET</item>
            <item>FWPM_NET_EVENT_FLAG_LOCAL_ADDR_SET</item>
            <item>FWPM_NET_EVENT_FLAG_REMOTE_ADDR_SET</item>
            <item>FWPM_NET_EVENT_FLAG_LOCAL_PORT_SET</item>
            <item>FWPM_NET_EVENT_FLAG_REMOTE_PORT_SET</item>
            <item>FWPM_NET_EVENT_FLAG_APP_ID_SET</item>
            <item>FWPM_NET_EVENT_FLAG_USER_ID_SET</item>
            <item>FWPM_NET_EVENT_FLAG_IP_VERSION_SET</item>
            <item>FWPM_NET_EVENT_FLAG_PACKAGE_ID_SET</item>
        </flags>
        <ipVersion>FWP_IP_VERSION_V4</ipVersion>
        <ipProtocol>6</ipProtocol>
        <localAddrV4>192.168.92.134</localAddrV4>
        <remoteAddrV4>192.168.92.6</remoteAddrV4>
        <localPort>49950</localPort>
        <remotePort>3128</remotePort>
        <scopeId>0</scopeId>
        <appId>
            <data>5c006400650076006900630065005c0068006100720064006400690073006b0076006f006c0075006d00650034005c00700072006f006700720061006d002000660069006c00650073002000280078003800360029005c007400650061006d007600690065007700650072005c007400650061006d007600690065007700650072005f0073006500720076006900630065002e006500780065000000</data>
            <asString>\.d.e.v.i.c.e.\.h.a.r.d.d.i.s.k.v.o.l.u.m.e.4.\.p.r.o.g.r.a.m. .f.i.l.e.s. .(.x.8.6.).\.t.e.a.m.v.i.e.w.e.r.\.t.e.a.m.v.i.e.w.e.r._.s.e.r.v.i.c.e...e.x.e...</asString>
        </appId>
        <userId>S-1-5-96-0-2</userId>
        <addressFamily>FWP_AF_INET</addressFamily>
        <packageSid>S-1-15-2-95739096-486727260-2033287795-3853587803-1685597119-444378811-2746676523</packageSid>
        <enterpriseId/>
        <policyFlags>0</policyFlags>
        <effectiveName/>
    </header>
    <type>FWPM_NET_EVENT_TYPE_CLASSIFY_DROP</type>
    <classifyDrop>
        <filterId>66432</filterId>
        <layerId>48</layerId>
        <reauthReason>0</reauthReason>
        <originalProfile>3</originalProfile>
        <currentProfile>3</currentProfile>
        <msFwpDirection>MS_FWP_DIRECTION_OUT</msFwpDirection>
        <isLoopback>false</isLoopback>
        <vSwitchId/>
        <vSwitchSourcePort>0</vSwitchSourcePort>
        <vSwitchDestinationPort>0</vSwitchDestinationPort>
    </classifyDrop>
</netEvent>

This is the TeamViewer service attempting an outbound connection to an HTTP proxy. The attempt fails, as can be seen from the FWPM_NET_EVENT_TYPE_CLASSIFY_DROP.

The event references the filter rule with ID 66432. This is it:

<item>
    <filterKey>{9a00657e-fe37-47c1-818c-f643513fc2fe}</filterKey>
    <displayData>
        <name>Block Outbound Default Rule</name>
        <description>Block Outbound Default Rule</description>
    </displayData>
    <flags/>
    <providerKey>{4b153735-1049-4480-aab4-d1b9bdc03710}</providerKey>
    <providerData>
        <data>6000000000000000</data>
        <asString>`.......</asString>
    </providerData>
    <layerKey>FWPM_LAYER_ALE_AUTH_CONNECT_V4</layerKey>
    <subLayerKey>{b3cdd441-af90-41ba-a745-7c6008ff2300}</subLayerKey>
    <weight>
        <type>FWP_EMPTY</type>
    </weight>
    <filterCondition numItems="1">
        <item>
            <fieldKey>FWPM_CONDITION_ALE_PACKAGE_ID</fieldKey>
            <matchType>FWP_MATCH_NOT_EQUAL</matchType>
            <conditionValue>
                <type>FWP_SID</type>
                <sid>S-1-0-0</sid>
            </conditionValue>
        </item>
    </filterCondition>
    <action>
        <type>FWP_ACTION_BLOCK</type>
        <filterType/>
    </action>
    <rawContext>0</rawContext>
    <reserved/>
    <filterId>66432</filterId>
    <effectiveWeight>
        <type>FWP_UINT64</type>
        <uint64>549755813888</uint64>
    </effectiveWeight>
</item>

This rule applies whenever its single condition matches. The condition is that the "package ID" of the packet's (actually, the connection's) originator is not S-1-0-0 (no identity), or in other words, it matches everything that has a package ID.

In the event trace, we see that the TeamViewer service process has a package ID, wherever it may have acquired it, hence it matches this rule and its traffic is blocked.

I have no idea where the rule comes from (except that it is a Windows Firewall rule per its provider ID) or what it may be intended to do. My current guess is that "modern" apps are not supposed to communicate when no user is logged on.

I cannot prove that this is any different on 1607, because apparently WFP captures do not include permitted packets. According to Process Explorer, the service process has no application package SID in either version.

58 Replies
Posted by chrullrich
Digon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

chrullrich wrote:

In the event trace, we see that the TeamViewer service process has a package ID, wherever it may have acquired it, hence it matches this rule and its traffic is blocked.

 From the WFP trace:

<packageSid>S-1-15-2-95739096-486727260-2033287795-3853587803-1685597119-444378811-2746676523</packageSid>

From the list of app containers:

Container:
SID: S-1-15-2-95739096-486727260-2033287795-3853587803-1685597119-444378811-2746676523
Name: microsoft.windows.fontdrvhost
Display name: Usermode Font Driver Host

That is clearly the same SID. So how does the TeamViewer service get stuck with the "font driver host"'s package identity?

Posted by TeamViewer Staff
TeamViewer Staff

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

@chrullrich That's a very interesting bit of information. The fact that the service is using the SID  of a different user is definitely not correct if there's no user logged in. We will fix that but before that could you test if that would solve the problem?

To test it you need to disable the Windows Firewall service.

Maurice
Software Developer
Posted by chrullrich
Digon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

@Maurice, yes, with the service disabled, the computer shows up immediately after rebooting, and I can connect to it.

Also, there is plenty of other evidence that the firewall is interfering: The TV log says something about "connection failed" due to "bad access", the Security event log is full of events 5152 (firewall blocked packet) and 5157 (firewall blocked connection), both referring to teamviewer_service.exe, and my network trace clearly shows that the connection attempts do not reach the switch.

Please be aware that this SID is not a user SID, and is not used as one by the firewall. An application package identifier is a SID that is used for sandboxing processes, both "modern" apps and such others as opt in to this protection. As the name says, it identifies an application, not a user.

Posted by mandfmike
Henagon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

I turned the windows firewall service off on one of my computers with windows 10 1703 on the domain and rebooted. It did show up on the list and I was able to log in to it like normal unattended access. Turned windows firewall service back on, rebooted and can't access it until someone logs in.

Posted by Bradb21
Henagon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

I've upgraded a couple machines to 1703 and one machine is fine and the other never appears in my console after boot. I've noticed the service does not start, and so far I've been able to fix it by setting the service to "delayed start" and it then appears in my console as online automatically. I had to have a user manually start it on the other end every time.

Posted by hubran
Henagon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

For me this didn't work. It doesn't make any difference whether the Windows firewall is stopped or running, only after someone is logged on (either locally or remote via rdp) the machine shows up as online under TV computer and contacts.

It is w10-x64 v1703 updated from v1607

Posted by TimCFT
Henagon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

Confirmed here too. I had previously tried turn off the firewall in the GUI with no effect, but disabling the service shows the workstation online immediately after reboot, without user interaction.

I've tried turning off the firewall in the GUI for each connection type in turn (in case it wasn't immediately identifying as a domain connection, etc) and for all three at once, but only disabling the service has the desired effect.

Posted by TimCFT
Henagon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

Hopefully TeamViewer can confirm that they are working on a fix for this, or talking to Microsoft? As disabling the FW is obviosuly not an option and TV is therefore not currently fit for purpose.

Posted by mandfmike
Henagon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

I disabled the Windows Firewall service and it is available after reboot without anyone having to log in. I didn't use the firewall GUI. When I re-enabled the Windows Firewall Service and rebooted, I was back to having to have someone login or RDP to the machine.

Why can't TeamViewer come up with a solution? I bet LogMeIn doesn't have this problem.

Posted by mandfmike
Henagon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

I agree, teamviewer should of had this problem fix by now. I know they said none of their machines have this problem when they rolled Win10 1703. I find that hard to believe when I installed it on 5 computers and I have this problem on all 5. I rely on unattended access several times DAILY. I would be forced to switch to a more reliable solution very soon. Guess time to start looking for an alternative at least.

Posted by kevinleesmith
Henagon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

Basically Teamview people do not care. That is obvisous.

Our response is also obvisou, to find another provider who does offer functionality you would expect t find in a v0.0.0.01 of a product.that is not present is Teamviewer.

Can any suggest altenratives? Let use their messeaging system to find a competitor.....

Posted by hubran
Henagon

Re: Windows 10 sieht nicht zum Starten des Dienstes bis Anmeldung

The latest build offered by TV support team seems to fix this problem. Guess this version will be released soon to public