nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Quicken Update Program - it gets confused

Dana Netherton

I'm running Quicken Classic Deluxe R52.28, on Windows 10.

Today I manually installed the patch to bring Quicken from R52.20 to R52.28. When the patch opened up, I read this:

"The version of Quicken installed on this computer is R1. The latest version is R52.28. Listed below are the changes and improvements." (then followed 52+ entries about "What's New")

This looked familiar, so I thought - and then remembered. Oh yes, I also saw this when I (manually) updated to R52.20. That time, I shrugged and moved on. But …

R1? Really? Clearly something's wrong. I wonder what.

Perhaps this might be relevant: for several months now, when I start Quicken for the first time in the day, I get this pop-up from the Quicken Update Program:

"An error occurred - Unable to check for updates, the server file failed to load. (Show details)"

Click to see details and get: "We are unable to contact the Quicken server. Please check your internet connectivity and try again. If the problem persist [sic], try again later."

"Internet connectivity" is a red herring. Both Windows and all my other software tell me that I'm firmly connected to the Internet. Including a resource-intensive video game I was running in the background.

Once again - clearly something's wrong with the Quicken Update Program. I wonder what.

Find more posts tagged with

Windows

Update

Comments

splasher

Update reporting that the current version is R1 is a long standing issue that for some reason Quicken has never been able to resolve.

UKR

If you are getting "Oops, something went wrong" or "Check Internet Connection" …

To make sure that Quicken is allowed to update and save its configuration files please check if Windows Defender Controlled Folder Access feature Ransomware protection is enabled.
If it is, configure it to add Quicken as an "allowed app" without turning off Ransomware protection. Perform the last step in
https://community.quicken.com/discussion/7857675/faq-windows-defender-controlled-folder-access
Have you recently enabled a VPN?
If so, this might be the problem. Try turning the VPN off, reboot with VPN disabled and see if that helps.
Is there a corporate or otherwise external firewall getting in the way? Contact the IT people maintaining the firewall and ask for permission.
Does your Antivirus software allow Quicken to connect to the Internet?
Quicken needs to be able to establish outbound Internet connections for the program to work.
For example, in McAfee Firewall, one user states "By editing the Quicken Firewall entry Selecting Incoming and Outgoing, and changing it from "Default" to "Open to all devices" it now works without having to turn off the entire firewall!"
See Check your firewall settings and ensure the following three entries are present:
If necessary, contact the Antivirus / Firewall vendor's Support Center for assistance.
In Windows 11 or older Windows systems go to Windows Control Panel and select Internet Options (or in Internet Explorer, click on Tools / Internet options.)
Click the Advanced tab.
Scroll down the list to "Use TLS 1.x" and click to put checkmarks on all available choices even though some of them are no longer supported "Use TLS 1.0, 1.1, 1.2 and 1.3 (if available)"
Turn off "Use SSL 3.0"
Click Apply. Reboot.
If all else fails: Try rebooting your network router. When done reboot your PC
Please let us know which of the above solved your problem.

Dana Netherton

Thanks, splasher. If the "R1 version" bug is that widespread, then it's probably a separate matter from my problem with connecting to "the Quicken file server."

Thanks, Ukr. I'm working my way through your list. This is complicated, a little, by the fact that I don't use Windows Defender - I use AVG Antivirus. So I've been learning how AVG handles ransomware (and other things).

Since I only get the "can't connect" complaint once a day - the first time I start Quicken, each day - I have to make a change (if applicable) … wait for the next day to see if I still get the complaint … and so forth.

If one of the steps solves the problem, I'll pipe up here. Otherwise, I'll keep grinding through them until either it's solved or I run out of steps.

Again, thanks.

Dana Netherton

Hmm. Since the "quote" feature reproduced ukr's whole post as a single long object - unable to insert responses following each suggestion - I'll just plow through it here.

Before I tell the story of stuff I did etc, here's where my installation of Quicken is:

On the one hand, it no longer balks during the day's first startup with a vague complaint.

On the other hand, when I go to the menu - Help/Check For Updates, that's when it complains. With the same old complaint. (See screenshot, attached)

Check Update Screenshot 2023-10-08 133418.jpg

So it's still unable to contact the Quicken server. But it's slightly less annoying about that.

Oh, all this is with Quicken Deluxe "Classic" version R52.28.

Now then. What you suggested, what I did.

1. Check status of Windows Defender's "Ransomware protection" feature

My laptop uses AVG's Antivirus software, rather than Windows Defender. On checking it, I discovered (1) that AVG AV has a "block or allow" feature you can apply to a computer's apps and (2) Quicken was not mentioned explicitly in that feature. I put it in the "Allow" column for "Ransomware" protection (and some others).

2. VPN?

Yes, I am using Proton VPN. As you requested, I turned it off, rebooted with VPN disabled.

3. Corporate or other external firewall?

No, this is a personal computer on my home's LAN.

4. "Does your Antivirus software allow Quicken to connect to the Internet?" You identified three entries that the software should have.

My AVG Antivirus had had the relevant entries for QW.exe and QuickenPatch.exe. I added an entry for QWSubprocess.exe.

5. In Windows 11 & older, go to Windows Control Panel and (detailed instructions) and put checkmarks for TLS 1.0, 1.1, 1.2, and 1.3 (if available). Turn off SSL 3.0.

When I got there, SSL 3.0 was off and TLS 1.2 & 1.3 were on. I added checkmarks to TLS 1.0 and 1.1. Then I rebooted.

6. If all fails: try rebooting your network router. When done reboot your PC.

Since I was still getting that error message (when I tried to check for updates after Quicken had started up smoothly), I did this. Actually, I rebooted my modem, which feeds my router. Then I rebooted my router. Then I rebooted my PC.

Still getting that error message (see above).

Overall status:

I'm not getting that annoying complaint on startup, so that's good.

My PC is also running a little more smoothly. (Something not-Quicken-related that had been annoying me for several weeks is no longer happening.) Here's hoping some of the tweaks accomplished that!

Still unable to connect to Quicken's server to check for updates, though. Still relying on the Manual Patch web page to keep it updated.

So it's a little better - just not completely resolved.

Again, thanks for these suggestions, ukr.