Quicken crashes during program launch

Quicken crashes when the program is started. The opening small splash window appears, and later vanishes without the main program window ever appearing. This problem reoccurs after each and every Microsoft security patch or system update. The problem appears to be a mismanaged dependency on Microsoft's .NET framework. The problem has only been resolved by removing and reinstalling Quicken. Removing and reinstalling Quicken almost every time it is used is an unwanted chore.

The following errors are logged
.NET Runtime - EventID 1026
Application: qw.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.SEHException
at <Module>._WinMainCRTStartup()
Application Error- EventID 1000

Faulting application name: qw.exe, version:, time stamp: 0x6450b99a
Faulting module name: KERNELBASE.dll, version: 10.0.19041.2965, time stamp: 0xf18c1c30
Exception code: 0xc06d007e
Fault offset: 0x0013d6c2
Faulting process id: 0x2c8c
Faulting application start time: 0x01d98355eea108be
Faulting application path: C:\Program Files (x86)\Quicken\qw.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 51c70bbf-d4dd-4dc0-a9fe-9b8d114302b9
Faulting package full name:
Faulting package-relative application ID:

One October 2022 version of the 1st event was recorded by Quicken release that had trace symbols,

.NET Runtime - EventID 1026

Application: qw.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ComponentModel.Win32Exception
at MS.Win32.UnsafeNativeMethods.CreateWindowEx(Int32, System.String, System.String, Int32, Int32, Int32, Int32, Int32, System.Runtime.InteropServices.HandleRef, System.Runtime.InteropServices.HandleRef, System.Runtime.InteropServices.HandleRef, System.Object)
at MS.Win32.HwndWrapper..ctor(Int32, Int32, Int32, Int32, Int32, Int32, Int32, System.String, IntPtr, MS.Win32.HwndWrapperHook[])
at System.Windows.Window.EnsureHiddenWindow()
at System.Windows.Window.SetTaskbarStatus()
at System.Windows.Window.CreateAllStyle()
at System.Windows.Window.CreateSourceWindow(Boolean)
at System.Windows.Window.CreateSourceWindowDuringShow()
at System.Windows.Window.SafeCreateWindowDuringShow()
at System.Windows.Window.ShowHelper(System.Object)
at System.Windows.Window.Show()
at System.Windows.Window.ShowDialog()
at QuickenWindow.ViewModels.MainViewModel.OnSymbolLookupSelection(System.Object, Quicken.Interface.App.SymbolLookupResultArgs)
at QuickenInteropNS.CQWAppManager.raise_SymbolLookUpSelection(System.Object, Quicken.Interface.App.SymbolLookupResultArgs)
at QuickenInteropNS.CQWAppManager.handleSymbolLookUpSelection(System.Object, Quicken.Interface.App.SymbolLookupResultArgs)
at QuickenInteropNS.CQMainManager.raise_SymbolLookUpSelection(System.Object, Quicken.Interface.App.SymbolLookupResultArgs)
at QuickenInteropNS.CQMainManager.FireSymbolLookUpSelection(SByte*)
at <Module>.QMainEvents.SymbolLookupSelection(SByte*)
at <Module>._WinMainCRTStartup()


  • Quicken Jasmine
    Quicken Jasmine Moderator mod

    Hello @Platinum Platypus,

    Thank you for reaching out to the Quicken Community with this issue.

    We do currently have an ongoing active alert regarding users experiencing crashing when performing different functions in their Quicken desktop program. You may follow this link to access that alert where you may bookmark it in order to remain up to date on any new information, ETAs, or resolutions that occur.

    I do apologize for any inconvenience caused in the meantime.

    -Quicken Jasmine

    Make sure to sign up for the email digest to see a round-up of your top posts.

  • Platinum Platypus
    Platinum Platypus Member ✭✭
    Thank you for the link. I think this issue is directly related to Quicken's dependency on .NET Framework V4.0.30319
    Reinstalling Quicken appears to install a deprecated version of the .NET runtime that the monthly Microsoft update promptly removes.

    Quicken currently installs using the package for .NET framework 4.6.1 but .NET Framework 4.5.2, 4.6, and 4.6.1 were retired on April 26, 2022, and support for them has ended.

    Microsoft .NET security updates are pushed to Windows 10 machines at least monthly. Some of these updates alter / disable features of the .NET framework, e.g. KB5022083 disables all XPS documents. The MS update process reapplies all previous updates.

    I think this problem will be related to how Quicken registers or fails to register its affinity for a particular version of the .NET framework when Quicken is installed and the MS update process removing the deprecated version Quicken prefers.

    Before reinstalling Quicken these are the installed versions of .NET Framework that are reported in the registry using the powershell command;

    PS C:\Windows\system32> Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP' -Recurse | Get-ItemProperty -Name version -EA 0 | Where { $_.PSChildName -Match '^(?!S)\p{L}'} | Select PSChildName, version

    PSChildName Version
    ----------- -------
    v2.0.50727 2.0.50727.4927
    v3.0 3.0.30729.4926
    Windows Communication Foundation 3.0.4506.4926
    Windows Presentation Foundation 3.0.6920.4902
    v3.5 3.5.30729.4926
    Client 4.8.04084
    Full 4.8.04084

    I'm not sure how many ways this went
  • Platinum Platypus
    Platinum Platypus Member ✭✭
    ...to pick up where I left off,

    after reinstalling Quicken, two folders were modified
    C:\Windows\Microsoft.Net\Framework\v4.0.30319 and

    in each of these folders the only file modified or created on the current date is ngen.log
This discussion has been closed.