Locking remote computer at the end of session

Teamviewer has just started to lock some but not all remote computers screens when the session ends. I have check that Lock Remote Computer is set to NEVER. I have made sure it's set on both remote and local PC but this is still occuring. It has only just started to do this as well as not adding some PC's to the Recent Connections list after connecting to them.

I need to fix this ASAP.setting to prevent lock

Find more posts tagged with

Comments

chris_w

a fix for 12 or 13?

Discord37

I reverted to V 12, then let it upgrade but it still locked my computer, maybe if I deleted settings it wouldn't but I'd rather not. I then went back again to v 12 and I guess I'm there until it's fixed.

HaraldRoelse

Could it be this has to do with the latest updates of Windows-10 ?

Anybody with this problem has the latest Windows-10 updates installed ?

Discord37

@HaraldRoelsewrote:
Could it be this has to do with the latest updates of Windows-10 ?
Anybody with this problem has the latest Windows-10 updates installed ?

I just got the update yesterday & it has been happening for weeks that I noticed. I had not tried to turn it off before.

Discord37

I reverted all 3 of the computers I use to 12.0.95388, 2 are Win 10, one is Win 7, I thought it was ok but it's still locking my Win 10 main computer I access. So I have to go back older? I can't believe this issue is still not being fixed. It has ruined the program for me and many others. I do not like using old version of something like this. Old versions may have security holes.

SteveT

As previously mentioned I waited for the next version and installed it hoping that the issue would have been resolved. Installed 13.1.3629 on local & remote PC's and the problem returned once more. Replaced remote PC software with Ver 13.0.1558 and it seems to have disappeared again. Up until I've resisted switching to *bleep*, using only as a fallback solution for when Teamviewer lets me down, mainly because in my location I can only use *bleep* with a VPN which can make it very slow sometimes. I hope the staff at Teamviewer are listening and will perhaps consider that having their system do anything other than disconnect at session end is a bad idea. This also applies to the end of session notice that it puts up right in the middle of the remote PC screen (Very annoying if like me you use it to set up screen recording sessions on a remote PC in another country)

Discord37

I reverted my Win 10 comp that I remote to mostly to 12.0.6447 and it doesn't lock now. I really don't like using older versions for this type of app. I also have feedbacked their notice messages on disconnect. Sometimes 2 come up and if you have more than 2 you cannot log back in remotely unelss you have something else like chrome. So if you reconnect and something kicks you off before you can click them you are locked from your computer until you get to it in person or as I do now have chrome remote as a backup.

warrior161

I've reverted everything back to version 11, having completely removed all references to Teamviewer from Hard Drives and registry. Thought it resolved the issue but it came back. Only cure was to have remote computers log on automatically. Not a good solution. Teamviewer have had a long time to resolve this and haven't. I suspect they have no intention of doing so.

Julia from the Teamviewer Staff posted in March that we would be kept informed on this thread. But we've heard no more.

Julia

Hi all,
Sorry for the late reply.
We will roll out a fix with the next release but we do not know when this will be published. I will of course inform you, when we published it.

Cheers

SteveT

Same problem started with last two upgrades. Seems to be with software on local PC as it can be made to disappear by changing the never option to always and then back again on the local PC. Problem then returns with the next restart. Another indication that it's the local PC that is doing it, is that it never happens if I control the same remote PC with the android version on my phone.

TimNNS

Is there any update to this? It is a pretty big deal causing a great deal of inconvenience.

Julia

Hi all,

Thank you for your patience.

We published an InsiderBuild today with a fix for the problem (find out more about InsiderBuilds in our Knowledgebase). The fix will also be published in our next official release.

Cheers,

glnz

Same issue, using TV from my work Win 7 Pro 64-bit PC to access my home Win 7 Pro 64-bit PC.

ALSO - and I think this is related - Teamviewer will change the screen "Appearance" settings on the target (Master?) PC. It does this erratically but frequently when I'm at my 7 PC and use TV to access my home XP machine - it turns on "Fade" on the XP machine in Display Properties - Advanced - Effects.

ialreadyhaveone

I enabled the insider builds in V12 client and have yet to see any update (>1h since enabling). When searching for updates I only get the misleading "Update to V13 now".

Can you please provide a little more than the bare minimum of information?!

Does this insider build address the issues in V12?
What is the resulting build number/minor version after this "fix".

More questions that need to be answered:

Will V12 receive the fix in the "next official Release"?
When will this Relase begin to be rolled out?

ialreadyhaveone

Can you please tell us the specific version?
Will this fix be available in Version 12?

RHammer

It seems to me to be related to remotely rebooting the computer.

For me, from TeamViewer, rebooting the computer and then coming back to the computer after it boots up, the "Lock Computer" setting is checked (although it is deselected before the reboot).

Hope that helps.

~Hammer

Discord37

When this happens I have not rebooted the remote computer at any point. I have just eneded my session.

mark_mthws

@Julia Is there a fix for Mac on Version 14.2.8352 so that it can be set as default?

mario7711

This worked for me !
Changing to automatic on 'my' PC and then verify the unlock setting on the remote PC (wich was changed to 'lock when session ends'').

Thanks