Re: Teamviewer Windows
Genciana Haggins
TeamViewer crashes 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 ??
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 run Windows 10 on a headless HP Gen8 Microserver.
I have Teamviewer 13 (13.0.6447) installed, I have setup Unattended Access, I have ticked the Start With Windows box, I have copied the shortcut to the Startup Menu... and it WILL NOT start with Windows.
The application runs fine if manually started, but this is no good given the server is headless, I really can't be doing with hooking it up to the television every time Windows has updated and restarted, just so I can get an application running again.
Same problem, tried uninstall/reinstall, tried different settings in firewall, nothing works. TV used to start with Windows OK, now not. Submitted feedback to TV a couple of times during uninstall, no response there of course. May have to use alternative.
It seems like Microsoft has in issue with timing services. You need to do this for you to workaround their issues with timing, when I figured this out it put an end to hours of trial and error for other critical services and Teamviewer ofcoz.
Press "win key + R" then type "services.msc". It should open the services manager. Now find Teamviewer from the list and set the service to start "Automatic(delayed start)" instead of just "Automatic". This will cause the Teamviewer service to be started a little bit later, maybe 2 or even 5 mins later, but it will start. This works for any version of windows even server.
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?
It sounds like you will need to utilise a reserved IP address to ensure that between VM cycles you will ensure you keep the same address. You can find details on how to do this here: -us/documentation/articles/virtual-networks-reserved-public-ip/
I was trying to figure out on teamviewer support how to make the ID fixed after a deallocate/start cycle. They send to me a reg file to apply in one machine using Teamviewer/Extras/Options/Advanced import reg files.
The relevance has been fixed so that it is only applicable on x64bit and we are looking to add 32bit teamviewer as soon as possible since it is a pretty common application, that said, we do prefer 64bit software as the default when available.
I have setup a teamviewer Connector in MS endpoint manager and after i connected to a managed iPhone then the only thing i could see that i can request screen shots, share screen, transfer a file, import config file ( XML ) but i can not manage the iOS settings in spite of i read on some MS sites that the intune admin can do list of actions on iOS. Did i miss anything in the setup may be that i can not manage the iOS settings?
@Sarmad15 I understand what you are looking for, but I think you should raise that question on the Teamviewer forum. The integration with Intune is not the problem here, it's the features of Teamviewer. It might also depend on your Teamviewer License.
03c5feb9e7