Teamviewer Qs Windows 7

[Hermalindo Lepicier]

TeamViewercrashes often on my Surface Pro X which runs Windows 10 on ARM (arm64). This device can run 32-bit apps through emulation when no native arm64 is available, which is the case for TeamViewer. So TeamViewer runs in 32-bit on this device.

When a crash occurs (e.g. when remotely controlling a customer's device), a log is visible in the Windows Event Viewer.

Would be great if TeamViewer was available natively on Windows on ARM though, instead of running as an emulated 32-bit application. CPU usage is quite high currently, and the battery life would definitely benefit from a native ARM version.

I'm planing to purchase a Microsoft surface pro x device, but I'm hesitated because as you've mentioned most of the windows applications runs on the Surface uses the 32-emulator, the most important application I need is teamviewer & without confirming it runs on the Surface without any problems there is no point of purchasing it except wasting my money.

I gotta say that the 32-bit version of TeamViewer has been working fine on my Pro X - I had issues with hardware acceleration in the beginning, but those have been resolved in the meantime (I believe through a display driver update on Microsoft's side).

Tried the 64-bit version two weeks ago on Windows 11 (which supports 64-bit emulation) but it crashed when I tried to connect to another computer. The 64-bit emulation in Windows 11 is slightly buggy still, so I expect that to improve over time.

I think it's just a matter of time for TeamViewer to come up with a native ARM64 version of Windows. As a developer I know that a lot of toolchains/dependencies have been updated to support ARM64 lately (which I've been contributing to myself as well), so it should become easier and easier for TeamViewer to port things to ARM64 ??

I came to my computer today and have not been here since monday afternoon. I am using windows 7. There were some error messages showing even on the log in screen about memory violations done by spotify and one more (I can't remember), and I just clicked them away, even though it is not normal on my PC. Sometimes it freezes on the login screen and I have to reboot, but this was different. But I did not take a note of the messages as I just didn't care.

After logging in, I noticed that my Teamviewer client was running (the GUI was showing). I thought this was odd, since I haven't been using it lately. I was a bit curious, so I checked the log. I will not include it here, as I don't know how to read it and I do not know what could identify me. It seems that it was an update leading to this, but I am not sure. Probably, but I don't like the fact that the GUI was showing with my ID and password showing. They could have silently updated it or have given me a message...

So, this leads me to the question: How to figure out if someone has been using TeamViewer 8 to access my computer when I was not here? What to look for in logs and perhaps the Windows 7 event logs? And a bonus Q: Is it safe to have TeamViewer 8 running in the background at all?

We connect to the Standard account and try to switch to one of the administrator accounts, but when we do so, we lose connection to Teamviewer. And the only way to get it back, is if there is someone physically on the other end to log back into the standard account.

It's sounds like a problem with the service.

Could you please try to install TeamViewer again, on the admin account with admin rights?

Please keep me informed if i can be of any further assistance.

Same here. Multiple users of which several are admins. I am not. I can set up remote connection when logged in to my account, but cannot log in when have switched user and am at the users login page. Have Teamviewer 12 installed on both machines. Must I have the connection allowances set to administrators only? Would I be able to log on then?

It was working fine for the last couple of years, but now I had to install my relatives' computers (believe it or not, the insisted on Windows 7; they are very old and don't want to change!) - and using the latest TV versions I end up having precisely the issues described above.

TV looses connection upon logging off from Windows on the remote computer (remoter computer status and TV status both confirmed as ON). (We are not using Windows credential to auto log on but separate passwords). This is super-annoying, because the only way to come back is to phone the other (abroad!) side up and make them log into the computer, and then remote access is re-gained. This is independent of the Windows logon setting in the TV options and it is independent of whether or not the user has administrator rights (irrespective on whether on host or remoter computers).

Experiencing this issue on multiple systems after upgrading them silently from version 12.x to 15.40.x Changing the windows logon selection does not seem to make a difference. system is normally logged on as the local user, then when attempting to switch to the Administrative windows user the session immediately disconnects. i've checked everything as well as manully re-installing while phycally at the machine. i did find that updating from 12.x to 15.27.x seems to not have the issue, but as soon as the version is updated to current it reappears. occasionally we can log onto another restricted admin user account but it always fails when trying to go from either to the administrative user account. ***Note the windows logon screen with the administrative user does load locally but the remote user is disconnected by then. so the staff member has to cancel and login again as the local user.

2024 and still having this same issue. I have a remote computer I'm trying to access, but keep getting booted from TV when I log out of a user account. I don't have physical access to the PC, so I have to call and have someone on site log in before TeamViewer will work again. Kind of defeats the purpose. Very frustrating.

Out of curiosity I decided to compare the configuration of TV on my PC with the configuration of the remote PC I'm trying to access. I found that there is an option missing: "Full access control when a partner is connecting to the Windows logon screen".

i presume this is a windows 10 safety/security feature, it leaves full access for anyone on the remote computer but until they finish the install or change etc my remote control is frozen out, i can still see all but not actually do something

The "check for updates" option is a great hint. Unfortunately in my version (12.0.92876) there is only an update option for a certain timeframe (shortest is "weekly"). Can I use TeamViewer now only once a week? Please provide a feasable workaround - we pay for a license...!

This initially started happening with Skype, then SkypeForBusiness and Now Teams. It is pretty much Identical to TeamViewer. Except TeamViewer has the Update option to bring the windows back. The only way to get the MS Teams back is to Quit and restart.

I cant help but think they might be related? Both have the main window dissapear, cannot select the main window to bring to front or anything. Unfortunatly Teams does not have anny other menu options that will being up a window/dialog. they are all Links to Web pges.

My guess is that somehow the windows has closed - but the app has no function to bring back the window - therefore settings are remembering that the window wasn't open - so when you restart its not opening a NEW window.

The issue also is there should be an "teamviewer" link in th window menu item. I used this same trick check for updates and the window "magically" pops up. Then under window their is the Teamviewer window. Feels like they totally forgot something.

Just updated Teamviewer to 15.34.4 and am unable to connect to remote comp (Windows). Gives me following message. I don't think ID is a problem as the ID was working perfectly in previous version of TV, just before I updated it.

And by the way I tried connecting to that same Windows remote comp via the latest version of TV on a Windows comp, and it works fine for same ID. So it's definitely a "Teamviewer 15.34.4 for Mac OS" version problem. Any help is appreciated.

I've created an Azure VM with Windows server 2016, and I have teamviewer installed. I want to be able to access the VM via Teamviewer, however, if I am not connected to the VM by Remote Desktop Protocol (RDP), then my teamviewer listing for the Azure VM shows as offline. If I connect to the VM via RDP, it comes online.

stata rilasciata, anche se per ora in fase Preview disponibile solo agli utenti registrati nel circuito Windows Insider, TeamViewer QuickSupport, un'app di che permette di controllare da remoto uno smartphone Windows 10 Mobile.

La configurazione ha la solita impostazione semplice e intuitiva a cui il servizio ci ha abituati: basta installare l'app su smartphone e lanciarla per ottenere un ID temporaneo da nove cifre. Questo ID va inserito nel client per PC (che potete scaricare a QUESTO indirizzo) e dopo pochi secondi avrete il display del vostro smartphone riprodotto in una finestra del vostro PC.

L'interazione piuttosto lenta e scattosa, e la grafica un po' sgranata, ma per quelli che sono gli obiettivi primari del servizio (fornire assistenza) pu andare pi che bene. Se volete provarla eccovi il link per il download - ricordiamo ancora una volta, dovete essere Insider nello Slow o Fast Ring.

li si va sul gusto che soggettivo, ma non una killer feature la start screen secondo me.

Poi magari ci fosse una parit di app...il problema proprio questo, bisognava avere della app esclusive che su altri os non ci sono...con tutti i servizi ms su gli altri os, anche chi legato a questi pu non prescindere da un terminale windows, mentre a parti inverse per chi legato alle gapps non pu valere lo stesso discorso perch queste non son presenti.

Ok alla vendita dei servizi...ma bisognerebbe cercare di farlo senza pestare i piedi all'os mobile

3a8082e126