You are here

Teamviewer is not starting

7 posts / 0 new
Last post
jcn50
Offline
Last seen: 2 months 5 days ago
Joined: 2023-05-11 11:54
Teamviewer is not starting

After the upgrade this morning: the Teamviewer app is starting with a white window "Starting Teamviewer..." for hours and nothing happens.. See screenshot here:
https://snipboard.io/uif89y.jpg
Am I the only one with this problem?

John T. Haller
John T. Haller's picture
Online
Last seen: 35 min 15 sec ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
More Details

It works fine here on Windows 10 x64. Please include complete system details, install path, etc. And try a fresh install temporarily. The most recent release is a major upgrade despite the version numbers not indicating such.

Sometimes, the impossible can become possible, if you're awesome!

jcn50
Offline
Last seen: 2 months 5 days ago
Joined: 2023-05-11 11:54
I have uninstalled and re

I have uninstalled and re-installed: same problem.

Using Windows 11 x64 on a Ejectable Media, path is:
D:\PortableApps.com\PortableApps\TeamViewerPortable

jcn50
Offline
Last seen: 2 months 5 days ago
Joined: 2023-05-11 11:54
I found the bug in the logs

I found the bug in the logs located at C:\Users\$USER\AppData\Local\TeamViewer\Logs\TeamViewer15_Logfile.txt, it is trying to connect via the proxy set-up in Mozilla Firefox (?!!!) which aren't the current proxy settings:
2023/05/16 16:12:38.361 3824 8692 G1 Logger started.
2023/05/16 16:12:38.361 3824 8692 G1 CustomConfigurationUpdaterImplWin::ReadInitialConfigurationId: Loading from machine
2023/05/16 16:12:38.376 3824 8692 G1 CRemoteReboot::IsServiceRunning() (1) CService::CService(): OpenService failed, Errorcode=1060
2023/05/16 16:12:38.376 3824 8692 G1 ProxySearch::GetCurrentTVProxySettings: did not find settings in path #1
2023/05/16 16:12:38.376 3824 8692 G1 ProxySearch::GetCurrentTVProxySettings: did not find settings in path #2
2023/05/16 16:12:38.408 3824 8692 G1 ProxySearch: found Mozilla HTTP setting: ***REDACTED***:8080
2023/05/16 16:12:38.408 3824 8692 G1 ProxySearch: found Mozilla HTTPS setting: ***REDACTED***:8080
2023/05/16 16:12:38.413 3824 8692 G1 ProxySearch: no PAC script detected via WPAD
2023/05/16 16:12:38.413 3824 8692 G1 ProxySearch: no PAC script detected via WPAD
2023/05/16 16:12:38.413 3824 8692 G1 HttpCustomConfigurationDownloader::SetProxyList: Set proxy settings
2023/05/16 16:12:43.207 3824 8692 G1 Monitors: Generic PnP Monitor, \\.\DISPLAY1, 1366x768 (0,0), flags=3, dpi=96
2023/05/16 16:12:43.222 3824 8692 G1 GetWebView2RuntimeVersion: got runtime version 112.0.1722.68

jcn50
Offline
Last seen: 2 months 5 days ago
Joined: 2023-05-11 11:54
OK I deleted this folder in

OK I deleted this folder in regedit.exe:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\TeamViewer

It's not looking for a proxy anymore, however I still have the loading screen... the logs became:
2023/05/16 16:55:56.373 11992 8012 G1 Logger started.
2023/05/16 16:55:56.375 11992 8012 G1 CustomConfigurationUpdaterImplWin::ReadInitialConfigurationId: Loading from machine
2023/05/16 16:55:56.377 11992 8012 G1 CRemoteReboot::IsServiceRunning() (1) CService::CService(): OpenService failed, Errorcode=1060
2023/05/16 16:55:56.377 11992 8012 G1 ProxySearch::GetCurrentTVProxySettings: did not find settings in path #1
2023/05/16 16:55:56.377 11992 8012 G1 ProxySearch::GetCurrentTVProxySettings: did not find settings in path #2
2023/05/16 16:55:56.397 11992 8012 G1 ProxySearch: no PAC script detected via WPAD
2023/05/16 16:55:56.398 11992 8012 G1 ProxySearch: no PAC script detected via WPAD
2023/05/16 16:55:56.398 11992 8012 G1 HttpCustomConfigurationDownloader::SetProxyList: Set proxy settings
2023/05/16 16:55:56.906 11992 8012 G1 Monitors: Generic PnP Monitor, \\.\DISPLAY1, 1366x768 (0,0), flags=3, dpi=96
2023/05/16 16:55:56.915 11992 8012 G1 GetWebView2RuntimeVersion: got runtime version 112.0.1722.68
code>

jcn50
Offline
Last seen: 2 months 5 days ago
Joined: 2023-05-11 11:54
I have downloaded the non

I have downloaded the non-portable Teamviewer from the official website and I am getting the exact same problem, so it must be a Teamviewer problem!

jcn50
Offline
Last seen: 2 months 5 days ago
Joined: 2023-05-11 11:54
Meh

I tried previous versions (13, 14) but none of them are working~

Log in or register to post comments