There are several conditions that may cause Quicken 2014 to crash when using One Step Update.
Before troubleshooting, make sure your version of Quicken 2014 is up-to-date.
Make sure the most recent version of QW.exe has been granted access to the internet through any firewall, hardware or software, by configuring your firewall and allow full access.
Note: Some corporate (Enterprise) level firewall applications may prevent individual users from performing these steps. Please see your network administrator, local IT, or the firewall vendor's website for further assistance.
Make sure the correct DLL versions for the latest release of Quicken are installed by running the Mondo Patch install for Quicken.
If the files are already up-to-date, you'll see a message "you have the latest version."
Windows 7 systems that have .NET Framework 4.0 installed as native may have received an incomplete or partially installed Microsoft Update for the .NET Framework Client Profile. This same patch may also have been downloaded to other versions of Windows (Vista or XP) that have .NET Framework 4.0 installed.
To repair this update
Microsoft has published updates and repair tools for currently available versions of .NET Framework. For these resolutions, please see:
The titles may not pertain to your exact problem, but the resolution(s) will be correct for .NET issues.
NOTE: Quicken 2014 & newer will rely on .NET 4.0, Quicken 2013 & older will rely on .NET 2.0. A problematic .NET installation for any version can cause problems for your version of Quicken. Following the Fix It instructions at Microsoft Support site should resolve any of these issues, but may require using different Fix It versions.
Some Quicken Users have reported on the Community Forums that they had modified their Windows Language settings to something other than English (US) and they resolved the crash issue by changing back.
Quicken Product Development is aware that a crash can be caused by this setting, and is working toward a resolution of that issue in a future version of Quicken. The current work-around is to leave the Windows Language at the default of English (US).
For more information, please visit Quicken Live Community and search for keywords "Unicode Language" or "One Step Update Crashes Quicken."
NOTE: See this article for other possible solution steps for this specific Permissions condition. The exact error can be found in the last session of the Dot Net Log (Help > Log files in Quicken) and used to select the correct option on this additional article.