Teamviwer 10 on Windows 7 won't/didn't start with Windows

Teamviwer 9 on Windows 7 64 Ultimate stopped starting with Windows. I uninstalled and reinstalled Teamviwer 10.0.36897 and each time I did "test reboots" on the new install it worked fine.

Now I need to use it in real world application and it seems on my last reboot the f**king thing did not start again (I didnt check because I thought from all the test reboots that it was working again) which was the reason for my uninstall reinstall in the first place.

Q1 - Why does Teamviwer not start with windows when the check box is checked instructing it do so?

Q2 - Now that Teamviwer has screwed up **AGAIN**, is there any other way besides teamviwer I can access the remote computer?? I need something from the remote computer and dont have time for this BS of programs not following orders (ie: start with windows when told to do so via checkbox) right now.

No idea why TeamViewer won't autostart even if you have the option checked to "start with Windows". Perhaps there's a firewall or anti-virus/anti-malware product running on the host machine that is preventing it from starting.

Have you asked for help from TeamViewer via their support page, submitting an email?

There's also a TeamViewer user forum where you might better get product support from other users.


There certainly are alternatives to TeamViewer for remote control from a client machine to a host/server machine, depending on your needs and whether or not the host machine is behind a router/firewall or not, etc.

TeamViewer happens to not involve a router in its own architecture that establishes a peer-to-peer connection between client and host through security verification (and fixed user machine ID and passwords) initially verified via a middle connection to the TeamViewer web site.

For this precise reason of not requiring router/firewall configuration (i.e. "port forwarding") I use TeamViewer as my "fallback secondary remote connectivity software". But my primary remote connection software is RealVNC, which I (as "the computer guru") use to remotely support the 22 machines for friends and family. RealVNC Personal is not free, but has a modest one-time $30 price for lifetime license per server machine (which includes free software upgrades and maintenance for one year). Client machine software (Viewer and Address Book) is free.

But RealVNC involves router/firewall configuration (if a router is involved) at the host machine location, to provide port-forwarding of RealVNC client requests to the RealVNC host server running on the host machine. If no router is involved then RealVNC installation will make the necessary and sufficient configuration tweaks to Windows Firewall on the host machine itself.

Note that if the host machine does not have a fixed IP address (which the client machine can connect to directly), but instead has a potentially dynamic DHCP-assigned IP address (as is typical of home ISP's), then connection from client to host cannot be done directly via hard-coded IP address since that address is variable. In this case, middle-level symbolic DNS services can solve the dilemma. I use DynDNS Updater as my solution to this specific problem, subscribing to their "pro" service which (for $15/year) gives me up to 30 host server symbolic server names that they provide symbolic DNS translation for. So this works perfectly for my own 22 remotely supported machines.

The DynDNS Updater software is installed on each of the RealVNC host machines, and updates the DynDNS DNS server database periodically with the currently DHCP-assigned IP address of that specific host machine. So when I attempt to connect from my RealVNC client machine to a RealVNC host machine, I actually connect to a symbolic URL which is hosted by DynDNS where it gets resolved and converted to a numeric IP address which is then used for the actual RealVNC connection from client to host.

Both RealVNC host server software and DynDNS Updater software are installed on the host machine, and both start with Windows at boot time. In fact, you can re-boot the host machine from the client machine and enter the Windows Welcome userid/password (same as you can do with TeamViewer).

I'm using the 10.0.36897 in W7 and W8.1, and don't see the problem you have.
I have TV set to NOT auto start, and i have the TeamViewer Service startup type set to manual.

When I run TV, it starts and works.
I login with a Standard account ... I would expect an Admin account would also work.

Check to make sure your TeamViewer 10 SERVICE is not set to disabled.

It's some setting(s) on your PC, not a "global TV" issue ...