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

JeeveStobs
JeeveStobs Posts: 23
edited October 1 in General questions

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?

Best Answers

  • JenW
    JenW Posts: 1,140 Senior Moderator
    Answer ✓

    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

  • JeeveStobs
    JeeveStobs Posts: 23
    Answer ✓

    Nice, thanks to my superior error reporting skills, they finally fixed it. Go me!

«1

Answers

  • You don't even need to pass the password flag for it to crash:

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

  • Ones_Zeros
    Ones_Zeros Posts: 3
    edited September 25

    Hello

    I just started having an issue with my TeamViewer crashing when attempting to make a remote connection.

    I have version 15.58.4 64-bit installed. I've tried to complete the migration process with no success.

    I appreciate any help with this issue please.

    thanks,

  • BobxT
    BobxT Posts: 4
    edited September 25

    I found I had to revert to TeamViewer 15.57.5 to avoid crashing. I am mostly using local logon connections. Strangely a web connection did work most of the time.

    I have not tried connecting outside my own home though. YMMV.

  • BobxT
    BobxT Posts: 4

    Your problem is exactly what I discovered.

    I found I had to revert to TeamViewer 15.57.5 to avoid crashing. I am mostly using local logon connections. Strangely a web connection did work most of the time.

    I have not tried connecting outside my own home though.

  • muffmolch
    muffmolch Posts: 11
    edited September 25

    can you share the 15.57.5 installer? or tell me, where to find that version? we have the same problem here

  • BobxT
    BobxT Posts: 4
    edited September 26

    I could not find TeamViewer 15.57.5 on TeamViewer website
    [removed per Community Guidelines - Only download trusted TeamViewer installations from TeamViewer.com]


  • with the latest Version my Teamviewer crashes when i type this:

    "C:\Program Files (x86)\TeamViewer\TeamViewer.exe" -i {my ip address} -q 4 --Password {my password}

    (Teamviewer Desktop on Windows 10)

  • How did you rollback to an earlier version?

  • JeeveStobs
    JeeveStobs Posts: 23
    edited September 25

  • JeeveStobs
    JeeveStobs Posts: 23
    edited September 25

    Same issue I reported: https://community.teamviewer.com/English/discussion/137223/faulting-application-name-teamviewer-exe-version-15-58-4-0-time-stamp-0x66e9e29f

  • JeeveStobs
    JeeveStobs Posts: 23
    edited September 26

    Send a DM with the link. These clowns aren't helping.

  • Vesa_75
    Vesa_75 Posts: 2
    edited September 26

    Can you DM link to me?

  • Same issue here: Teamviewer auto-updated and is now crashing when opened using command line parameters. Please fix this latest update as I'm currently running 15.40.8 (the only version I had in my downloads folder).

  • Is nothing being done about this?

  • Doesn't seem like it. They're about as incompetent as the folks at CrowdStrike.

  • EHCanadian
    EHCanadian Posts: 1
    edited September 27

    Confirmed as well via command line.

    Operating System: Windows 11 Pro 64-bit (10.0, Build 22631) (22621.ni_release.220506-1250)

    Faulting application name: TeamViewer.exe, version: 15.58.4.0, time stamp: 0x66e9e29f
    Faulting module name: KERNELBASE.dll, version: 10.0.22621.4111, time stamp: 0x03c619d0
    Exception code: 0xc000041d
    Fault offset: 0x000000000005fabc
    Faulting process id: 0x0x463C
    Faulting application start time: 0x0x1DB10B7DE560A31
    Faulting application path: C:\Program Files\TeamViewer\TeamViewer.exe
    Faulting module path: C:\Windows\System32\KERNELBASE.dll
    Report Id: 290a4709-88c6-47ad-85ea-f9e141871bdb
    Faulting package full name:
    Faulting package-relative application ID:

  • Thanks to BobxT for sending the link!

    Can you imagine being a paid customer and dealing with this issue?

  • JenW
    JenW Posts: 1,140 Senior Moderator
    Answer ✓

    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

  • IanGardini
    IanGardini Posts: 2
    edited September 30

    Hi everyone,
    starting this Friday TeamViewer no longer works with command line parameters.
    If launched with the -i and -P parameters it crashes immediately.
    I report the error recorded in Windows events:

    Nome dell'applicazione che ha generato l'errore: TeamViewer.exe, versione: 15.58.4.0, timestamp: 0x66e9de03
    Nome del modulo che ha generato l'errore: KERNELBASE.dll, versione: 10.0.22621.4111, timestamp: 0xb2651143
    Codice eccezione: 0xc000041d
    Offset errore 0x0014a892
    ID processo che ha generato l'errore: 0x0x20B8
    Ora di avvio dell'applicazione che ha generato l'errore: 0x0x1DB13091DD140A2
    Percorso dell'applicazione che ha generato l'errore: C:\Program Files (x86)\TeamViewer\TeamViewer.exe
    Percorso del modulo che ha generato l'errore: C:\Windows\System32\KERNELBASE.dll
    ID segnalazione: a87e7838-2f51-4a07-a59f-b9b2cc9de14f

    Thank you.

  • sysadmin_oo
    sysadmin_oo Posts: 1
    edited October 2

    Hi,
    We are experiencing the same issue, we integrate teamviewer with a 3:rd party tool and connect to hosts using this command line

    "C:\Program Files\TeamViewer\TeamViewer.exe" -i id -P password

    Also using version 15.58.4.0

  • Peter_Restomax
    Peter_Restomax Posts: 1
    edited October 2

    Same here

    Active teamviewer sessions also close.

    Version 15.58.4 (64 bits) Licence Tensor Basic

    Anyone a solution?

  • rfromano
    rfromano Posts: 2
    edited October 2

    Same here.
    It was after updating to version 15.58.4.
    Does anyone have the previous version to downgrade until they update or fix it?

  • Capito
    Capito Posts: 1
    edited October 2

    Same problem here.

  • rfromano
    rfromano Posts: 2
    edited October 2

    I temporarily resolved this by downgrading.
    Teamviewer support staff are aware of the issue.

  • muffmolch
    muffmolch Posts: 11
    edited October 1

    Now it's 2024-10-01 and there's still no bugfix … and not even the possiblity to downgrade to the last working version … no good

  • I have reverted back to version 14 now.
    Seems to be workign there still

  • muffmolch
    muffmolch Posts: 11

    I found a 32 bit 15.57.5 installer. Seems to help us out for the moment

  • JeeveStobs
    JeeveStobs Posts: 23

    They still haven't fixed this?

  • This is becoming quite annoying. I'm a user attached to a licensed account (and also the holder of the license under my corporate email) and am supporting a network with 50+ workstations. Having TeamViewer close whenever I try to link to one of the workstations when there is an issue that my customer facing staff is having is more than a little annoying… almost as annoying as the new user interface is.

  • mtiele
    mtiele Posts: 2
    edited October 2

    We have the same problem and I think that TeamViewer has changed something because of the vulnerabilities,
    which is why we switched to this new version.
    Since we also don't want to go back to the vulnerable version (for security reasons), we would appreciate it if TeamViewer would make a post on how to connect to TeamViewer via Commandline (or PowerShell or similar) in the future.

    A quick remedy would be good here.