Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

I keep getting Express.exe error when I shutdown PC.

larsjensenkbh
over 4 years ago

I keep getting Express.exe error when I shutdown PC. Using 7.3.0.0 - What to do?

  • Former Member
    0 Former Member over 4 years ago

    Same problem to me.

  • 0 over 4 years ago

    me also !! 

    Sinds de laatste update krijg ik elke keer een foutmelding bij het afsluiten van Windows m.b.t. Express. (7.3.0.0)

    Toepassing: express.exe
    Framework-versie: v4.0.30319
    Beschrijving: het proces is beëindigd als gevolg van een onverwerkte uitzondering.
    Uitzonderingsinformatie: uitzonderingscode c0000005, uitzonderingsadres 11A3B522
    Stack:

    When trying to use the 'send a mail' option on the website ....isn't working as well Disappointed

  • 0 over 4 years ago

    I have 2 PCs, one is working fine an HP Laptop, the other a new Dell Desktop having the issue.

    Turning off the background task, does fix the issue; but, would like it to run at startup.  Maybe a termination issue with some dependencies with a shared DLL or .NET framework issue with other applications that use the same interface at shutdown.  But, same exact error as everyone else here that has it.

  • 0 over 4 years ago

    At this point i would have expected that someone from Garmin wrote "Hey guys we have seen this and we will do something about it in ver. 7.3.01."

    But no. Apparently this is not a Garmin Forum but a user forum. 

  • 0 over 4 years ago

    I have done the latest Windows update. For a test, I put back "on" the background task. Reboot my PC twice to see and the problem seems fixed.

  • 0 over 4 years ago

    Also getting error when restarting windows, Express version 7.3.0.0,  error message:

    express.exe

    The instruction at 0x000...... referenced memory at

    0x000.....The memory could not be read.

    Click on OK to terminate the program

  • 0 over 4 years ago in reply to Wim_Kion

    Since the latest Windows 10 Update ,...problem looks to be gone

  • 0 over 4 years ago in reply to Wim_Kion

    When did you last update Windows 10? I've looked and my last update was on 11th February. I've checked today and my computer is up to date so there are no pending updates.

    I've definitely seen the error since Windows updated on 11th February.

    I don't get the error every time I shutdown my computer, but I do get it most times.

    Incidentally, one of the updates installed on 11th Feb was this:

    "Release Date:
    February 9, 2021

    Version:
    .NET Framework 3.5 and 4.8

    Summary
    This security update addresses a denial of service vulnerability in .NET Framework. For more information please see CVE-2021-24111.

    Known issues in this update
    Symptom

    After installing this update, WPF apps may crash with a callstack similar to

    Exception Info: System.NullReferenceException at System.Windows.Interop.HwndMouseInputProvider.HasCustomChrome(System.Windows.Interop.HwndSource, RECT ByRef)
    at System.Windows.Interop.HwndMouseInputProvider.GetEffectiveClientRect(IntPtr)
    at System.Windows.Interop.HwndMouseInputProvider.PossiblyDeactivate(IntPtr, Boolean)
    at System.Windows.Interop.HwndMouseInputProvider.Dispose()
    This occurs when disposing an HwndSource whose RootVisual is null, a situation that arises in Visual Studio when docking or splitting windows, and could arise in other apps.

    Workaround

    To work around this problem, set two AppContext switches using one of the methods described in AppContext Class (System) under the heading “AppContext for library consumers”. The switches are named Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix and Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix and both should be set to “true”. The first switch avoids the crash, but re-introduces the bug fixed in the KBs. The second switch is currently ignored, but will be recognized in a future .NET update that contains a fix for the null-reference crash; it restores the original bug fix.

    For example, using the app.config file method to apply the workaround at application scope:

    <AppContextSwitchOverrides value="Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix=true; Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix=true " />"

    Not sure if this is relevant or not.

  • 0 over 4 years ago in reply to Tourer

    I've rebooted my computer 3 times in quick succession just now to test and I got the error once. I have to admit I see the error less frequently now, but it's still there.