TeamViewer Forum

General Category => Teamviewer for Windows => Topic started by: ATeam on April 04, 2012, 04:57:14 AM

Title: TeamViewer7 doesn't want to start automatically
Post by: ATeam on April 04, 2012, 04:57:14 AM
Hello,
I just installed teamviewer 7 on a new computer and defined it to start with windows+my team viewer account, but the program doesn't start with the welcome screen and when i log into windows it always gives me a 'UAC' window asking to approve 'teamviewer.exe --dre'.
My system is Vista x64 home and i tried Google but could not find anything about '--dre'.
If i need to upload a screenshot of this just ask.

How can i resolve TV start from the login screen?

Thanks!
Title: Re: TeamViewer7 doesn't want to start automatically
Post by: ERS on April 04, 2012, 11:39:54 AM
Try right clicking on the teamviewer icon and choose "run as administrator" , type in your windows password and see if that help on subsequent starts.
Title: Re: TeamViewer7 doesn't want to start automatically
Post by: ATeam on April 05, 2012, 12:10:52 PM
It doesn't work for me, i also checked all settings to allow starting with windows and logon screen for all users, but nothing.
I still think there is a link to that UCA message i got with 'teamviewer.exe --dre' requesting permission to change things... ???, btw it is gone now and i don't know what the change was...

 
Title: Re: TeamViewer7 doesn't want to start automatically
Post by: ATeam on April 06, 2012, 08:51:01 AM
To be more exact, it says:
TeamViewer.exe" --dre

Does anyone know why this keeps happening? i must note its also happening on my other computer with vista home 32bit...

Title: Re: TeamViewer7 doesn't want to start automatically
Post by: ERS on April 08, 2012, 12:23:47 PM
Make sure you are logged on in an administrator account when you do this:
try completely uninstalling teamviewer and then reinstalling, choose the options to start with windows during that initial installation.
Title: Re: TeamViewer7 doesn't want to start automatically
Post by: ATeam on April 14, 2012, 03:49:29 AM
Update:
Problem solved, it was Comodo firewall that caused it, the new versions block communications until the user logs in to windows.

Thanks anyway!  :)