Update now to the most recent TeamViewer Remote version 15.59. See the Changelogs here.

[Windows] v15.58.4

JenW
JenW Posts: 1,163 Senior Moderator
edited 8:22AM in TeamViewer Remote

Operating system: Windows

Version: 15.58.4

Release date: 2024-09-24


New features

  • Users can now select how they want to work with devices. An additional "basic" view is now available, which allows users to view all their groups and devices at one glance, without tab-switching.
  • It is now possible to create custom Android Host modules via admin settings. This will streamline the assignment process and avoid the need to share credentials when managing a device.
  • It is now possible to initiate editing of a device, device group, or contact via the Global search results.

Improvements

  • Starting in October, Free users will be upgraded to the new interface, giving them access to our latest features and enhanced security. Licensed users can continue connecting with Free users using their preferred method. Learn more.
  • It is now possible to create and manage custom Android Host modules. The custom module can be linked with a rollout configuration, which allows you to define various configuration options for your deployed managed devices.
  • Free users will now be able to view groups that "require migration" in TeamViewer Remote.
  • It is now possible to select the "Inherit from group" policy option for single or multiple devices within a managed group.
  • The "It's you" pill now has the correct color.
  • The "Assigned to You" pill is now the intended color.
  • Improving signature verification for Windows drivers. (Security Bulletin: TV-2024-1006)

Bugfixes

  • The "Add users to role" dialog now includes a vertical scrollbar.

Modératrice Communauté Francophone / French Community Moderator

Comments

  • Posted from discussion at: https://community.teamviewer.com/English/discussion/136943/windows-v15-57-5#latest

    JeeveStobs Posts: 13 

    10:03AM

    Faulting application name: TeamViewer.exe, version: 15.58.4.0, time stamp: 0x66e9e29f

    The latest TeamViewer version crashes when opening a Windows shortcut of a LAN-only device:

    Faulting application name: TeamViewer.exe, version: 15.58.4.0, time stamp: 0x66e9e29f
    Faulting module name: KERNELBASE.dll, version: 10.0.19041.4842, time stamp: 0xe6d00f33
    Exception code: 0xc000041d
    Fault offset: 0x000000000003b699
    Faulting process id: 0x3bc0
    Faulting application start time: 0x01db0ec6b235c439
    Faulting application path: C:\Program Files\TeamViewer\TeamViewer.exe
    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
    Report Id: 448dd107-a338-47e3-8f37-3d7708e46679
    Faulting package full name:
    Faulting package-relative application ID:

    The TeamViewer Windows shortcut is simply the following:

    "C:\Program Files\TeamViewer\TeamViewer.exe" -i 192.168.1.2 -- Password $password"

    Any chance we can get this fixed in the next update?

  • LS_BOL
    LS_BOL Posts: 3

    We also experience this.

    When TeamViewer is closed and we use the command, then one log is recorded in the Event Viewer:

    Faulting application name: teamviewer.exe, version: 15.58.4.0, time stamp: 0x66e9e29f
    Faulting module name: KERNELBASE.dll, version: 10.0.22621.3958, time stamp: 0xfbc3a4f6
    Exception code: 0xc000041d
    Fault offset: 0x000000000005fabc
    Faulting process id: 0x0xE21C
    Faulting application start time: 0x0x1DB0FEFB974C3E8
    Faulting application path: C:\Program Files\TeamViewer\teamviewer.exe
    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
    Report Id: 0d4d46d5-2673-474d-b1ee-7aa2a7c646c7
    Faulting package full name:
    Faulting package-relative application ID:

    I tried opening TeamViewer and run the commands again. Then I got 2 log entries:

    Faulting application name: TeamViewer.exe, version: 15.58.4.0, time stamp: 0x66e9e29f
    Faulting module name: KERNELBASE.dll, version: 10.0.22621.3958, time stamp: 0xfbc3a4f6
    Exception code: 0xe06d7363
    Fault offset: 0x000000000005fabc
    Faulting process id: 0x0xADB4
    Faulting application start time: 0x0x1DB0FF0D6396940
    Faulting application path: C:\Program Files\TeamViewer\TeamViewer.exe
    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
    Report Id: d61ba409-5efe-4227-b246-825011532efe
    Faulting package full name:
    Faulting package-relative application ID:

    and then 3 seconds later

    Faulting application name: TeamViewer.exe, version: 15.58.4.0, time stamp: 0x66e9e29f
    Faulting module name: KERNELBASE.dll, version: 10.0.22621.3958, time stamp: 0xfbc3a4f6
    Exception code: 0xc000041d
    Fault offset: 0x000000000005fabc
    Faulting process id: 0x0xADB4
    Faulting application start time: 0x0x1DB0FF0D6396940
    Faulting application path: C:\Program Files\TeamViewer\TeamViewer.exe
    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
    Report Id: e33c6c09-f2b1-4d13-8218-d512f5614abb
    Faulting package full name:
    Faulting package-relative application ID:

    We use the program Remote Desktop Manager to execute the commands.

  • Having exactly same problem :( It is impossible start remote connection via command line.

  • develop_hax
    develop_hax Posts: 2
    edited September 26

    We are having the same problem with LAN shortcuts or command line.

    Same on 64 or 32-bit.

    Faulting application name: TeamViewer.exe, version: 15.58.4.0, time stamp: 0x66e9de03
    Faulting module name: KERNELBASE.dll, version: 10.0.22621.4111, time stamp: 0xb2651143
    Exception code: 0xc000041d
    Fault offset: 0x0014a892
    Faulting process id: 0x0xA068
    Faulting application start time: 0x0x1DB104511E6EF96
    Faulting application path: C:\Program Files (x86)\TeamViewer\TeamViewer.exe
    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
    Report Id: [removed per Community Guidelines]
    Faulting package full name:
    Faulting package-relative application ID:

  • MJ89
    MJ89 Posts: 5

    Same issue for everyone in our org.

    "C:\Program Files\TeamViewer\TeamViewer.exe" -i XXXXX

    2024/09/27 10:18:01.496 57144 70216 G2!!!CRASH: Unhandled C++ exception at 00007FFF1914FABC: Type unknown (Exception Code: 0xE06D7363)
    2024/09/27 10:18:01.504 57144 70216 G2!!!CRASH: Starting process to save dump file as 'C:\Users\user\AppData\Local\TeamViewer\Logs\TeamViewer_15_58_4_x64_20240927T101801.mdmp'

  • SebMie
    SebMie Posts: 1

    Same thing here. Very annoying…

  • Same here, my whole support team is broken. Because of that feature stopped working. I`m serching where to find the previous verion to downgrade and resume bussines as usual!

  • JenW
    JenW Posts: 1,163 Senior Moderator

    Hi all,

    Thank you for bringing this issue to our attention.

    Our teams are aware of it and are doing their best to investigate and resolve it. We will update this thread as soon as we have more information.

    We apologize for any inconvenience this may have caused and appreciate your patience and support.

    Best,

    Jen

    Modératrice Communauté Francophone / French Community Moderator

  • We are having the a similar issue using command line parameters example:


    TeamViewer.exe -i 123456789 -p example1234


    The logs shows a "TeamViewer terminated unexpectedly" error. I have contacted support too, so hopefully it can be fixed soon.

  • TeamViewer terminated unexpectedly

    We are having the a similar issue using command line parameters example:
    TeamViewer.exe -i 123456789 -p example1234
    The logs shows a "TeamViewer terminated unexpectedly
    I have contacted support too, so hopefully it can be fixed soon

  • tiva
    tiva Posts: 1

    Since the update, many of my managed devices are showing as online (Green), but they are not.

  • Pardalll
    Pardalll Posts: 3

    Hi @JeanK
    I updated Yesterday to this version and every time that I close my TeamViewer or reboot my PC, I need to login again even keeping the option to keep me sign in check.

    Updated from 15.23.9 to 15.58.4

  • MJ89
    MJ89 Posts: 5

    Hi @JenW, It's been a few days. Have the team had a chance to investigate the issue yet? We are eager to get back up and running, and downgrading is not an option for everyone.