Quicken Community is moving to Single Sign On! Starting 1/22/21, you'll sign in to the community with your Quicken ID. For more information: http://bit.ly/CommunitySSO
After upgrading to 19.52, Quicken crashes when doing one-step update (edited)

I sent in the Quicken Crash Report. I have no other information and can't do any update
0
Best Answer
-
Sherlock SuperUser ✭✭✭✭✭
The published work around does not require us to be able to get to the menu to edit the one-step update. If you haven't already, you may want to review: https://community.quicken.com/discussion/7855812/update-6-25-19-fix-for-crashes-experienced-in-quicken-for-windows-19-52-release#latest
If the issue persists, revert to an earlier patch release. I suggest you perform a clean uninstall, install while disconnected from the internet, update by applying the appropriate Mondo Patch, and restore a data file saved prior to updating from the earlier patch release. If you haven’t already, you may want to review: https://www.quicken.com/support/using-qcleanui-uninstall-quicken. To update Quicken, I recommend you download and apply the appropriate Mondo Patch: https://www.quicken.com/support/patching-updates-windows or http://www.quicknperlwiz.com/quickenpatches.html
To prevent Quicken from automatically applying an update, I suggest you set Windows UAC settings appropriately.
Quicken user since 1997
Premier on Windows 105
This discussion has been closed.
Answers
Quicken also gives error " We could not retrieve your Quicken profile information" when clicking "Quicken ID, Sync & Alerts". Attempting to sign out of my currently signed in account causes Quicken to crash. My Quicken.com account is valid as I am able to sign in via a browser.
"Webmethod call didn't succeed and the failure response is: - AuthHeader is missing"
Application: qw.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Exception
at EO.Internal.bae.a(System.String ByRef, Int32 ByRef)
at EO.Internal.jq+o.a(EO.Internal.bae)
at EO.Internal.jq.a(Boolean ByRef, EO.Internal.bae[], System.String, System.String)
at EO.Internal.jq.a(EO.Internal.bae[], System.String, System.String)
at EO.Internal.aqa.a(System.String, System.String)
at EO.Internal.av5.b()
at EO.Internal.av5.a(System.Security.Principal.WindowsIdentity)
at EO.WebEngine.Engine.Start(System.Security.Principal.WindowsIdentity)
at EO.Internal.av5.c()
at EO.Internal.ct..ctor(EO.WebBrowser.WebView)
at EO.WebBrowser.WebView.y()
at EO.WebBrowser.WebView.a(IntPtr, Boolean)
at EO.WebBrowser.WebView.Create(IntPtr)
at EO.Wpf.WebViewHost+a.a()
Exception Info: System.Reflection.TargetInvocationException
at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
at System.Delegate.DynamicInvokeImpl(System.Object[])
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at <Module>._WinMainCRTStartup()
Sorry, to hear that you're experiencing this difficulty.
Do you by chance have any firewall or 3rd party security software or antivirus?
https://www.quicken.com/support/configuring-firewalls
If that isn't the case have you tried restoring a backup file from prior to the update or validating the current file https://www.quicken.com/support/advanced-data-file-troubleshooting-correct-problems-quicken-windows
Please let us know if any of these options help correct the crashing you're experiencing.
-Quicken Tyka
https://community.quicken.com/discussion/7855784/quicken-crashes-on-19-44-is-there-a-way-to-revert-to-a-version-newer-than-14-23#latest
Unfortunately I've lost some trust in the software and will have to maintain a parallel installation in a VM to test all new patches before I apply them to my "real" machine.
Premier on Windows 10
https://community.quicken.com/discussion/7855812/update-6-25-19-fix-for-crashes-experienced-in-quicken-for-windows-19-52-release#latest
I agree their testing and QA controls are not worth much at this point. My file is worthless right now.
It didn't work, it also made Quicken crash. I hope the next release (that fixes this) is quick.
Go to Edit > Preferences > Quicken ID, Sync & Alerts
Click Sign in as a different user
Type "yes" to confirm
Click Sign Out
After you sign out, sign back in with the same Quicken ID
Once I did that, I was able to rename the file back to its original name and open it without Quicken crashing.
To prevent Quicken from automatically applying an update, I suggest you set Windows UAC settings appropriately.
Premier on Windows 10
If the issue persists, revert to an earlier patch release. I suggest you perform a clean uninstall, install while disconnected from the internet, update by applying the appropriate Mondo Patch, and restore a data file saved prior to updating from the earlier patch release. If you haven’t already, you may want to review: https://www.quicken.com/support/using-qcleanui-uninstall-quicken. To update Quicken, I recommend you download and apply the appropriate Mondo Patch: https://www.quicken.com/support/patching-updates-windows or http://www.quicknperlwiz.com/quickenpatches.html
To prevent Quicken from automatically applying an update, I suggest you set Windows UAC settings appropriately.
Premier on Windows 10