TeamViewer hangs on startup (msedgewebview2.exe)

Sander_Bouwhuis · 2023-08-02T13:53:14+00:00

There was an error rendering this rich post.

Sander_Bouwhuis

When starting TeamViewer, it very often hangs.

2023-08-02 15-48-56 237x134 System_Informer_[HOMEBouwhuis].png

I created a dump in the task manager so the developers can hopefully fix this bug:

[removed per Community Guidelines]

Find more posts tagged with

Accepted answers

All comments

.Carol.fg.

Hi @Sander_Bouwhuis ,

Thanks for reaching out to our Community!

When you say "when starting TeamViewer, it very often hangs" do you mean the TeamViewer service closes, or the remote session closes right after connecting with a partner?

Also, what is the OS you're using?

I'm looking forward to your reply. 🙋‍♀️

Best, Carol

Sander_Bouwhuis

Sorry, I do these steps:

I'm on a Windows 10 computer
I press the Start button on the taskbar
I start typing the letters t e a m v i....
The TeamViewer app appears in the start menu
I click on the TeamViewer menu item to start TeamViewer
The TeamViewer window appears, but is grayed out.
The mouse cursor is a rotating circle denoting I have to wait
The CPU usage is 100% of one core
The GUI remains grayish and the (wait) cursor keeps circling forever

.Carol.fg.

Hi @Sander_Bouwhuis ,

Thanks a lot for the additional detail!

A lot of changes happened with the new UI, maybe an old file is the cause of the crash.

Therefore, try to uninstall TeamViewer using our advanced uninstall instructions, and then download it again from our website (follow the instructions on the screen for the installation).

Please let us know if it fixes the issue, or if the problem persists.

Best, Carol

Urmeli

@Sander_Bouwhuis Is it the TeamViewer.exe process which uses one CPU 100%? It would be great if you could provide a CPU based dump using procdump with these steps:

1) Download procdump from ProcDump - Sysinternals | Microsoft Learn

2) Unzip it, open an elevated command prompt and navigate to the folder

3) Execute "procdump -w -c 80 -u -n 10 -s 3 TeamViewer.exe"

4) procdump waits now for the high CPU usage

5) Reproduce the problem ... when TeamViewer starts using the one CPU procdump should write dumps every ~3 seconds

6) Sends these dumps to us (in form of a ticket submitted to support)

Sander_Bouwhuis

As I already said, it's not TeamViewer.exe, but it is msedgewebview2.exe (which TeamViewer uses).

Here is an example where TeamViewer was already hanging for 1.5 minutes on startup when I made the screenshots and the dump file.

2023-08-07 09-27-35 838x137 Administrator_ETempProcDump_-_Original_location_of.png

2023-08-07 09-28-11 1103x513 msedgewebview2.exe_(12136)_Properties.png

Here is the dump file (I uploaded it to Mega because your forum doesn't support large files) :

[removed per Community Guidelines]

Urmeli

Thanks for the info. There is a problem during startup of WebView2 (aka msedgewebview2), not directly related to TeamViewer.

There are some options for analysis.

1) First, can you make a dump of the High-CPU process and would you be fine if we would forward that to Microsoft in case we don't get it resolved?

2) We know that some Anti-Malware applications can cause problems with msedgewebview2.exe processes. Do you have a special Anti-Malware active on your system and could it be deactivated temporarily (or could msedgewebview2.exe be excluded)?

3) One more thing that might help is reinstallation of WebView2 in case your Windows is <11. You can uninstall in Apps & features:

After uninstallation you can run the TeamViewer installer once more which then downloads & installs the most current version of WebView2.