R57.12 Auto-Installed and may have bypassed Windows UAC [Edited]

retird

Started Quicken this morning and Q automatically installed this update.

My system has been setup for years not to auto-install updates. nothing changed by me.

I then checked here and saw this update was available.

Why did it auto-install R57.12 ?

Zeker

Because that's the way they do it despite the complaints. Advice is to enable UAC so you are warned. But that affects the entire computer's system and is really an unacceptable approach.

splasher

I can't explain why, but sometimes the updates get past the UAC settings. My solution is to create a Firewall rule to block quickenPatch.exe outbound. The downside to this is that when Quicken looks at startup to see if there is an update available, Quicken fails to start. Also, you can't do a check for updates from the Help menu. Once you get used to those two issues, you either don't panic at startup and just start Q again or you don't look for updates via the Help menu.

retird

https://community.quicken.com/discussion/comment/20438419#Comment_20438419

UAC has been enabled for years…. thus my question…. WHY…..

Rocket J Squirrel

UAC can be bypassed programmatically. You can search the web for how to do it.

But I would certainly hope the Quicken developers would refrain from doing this on purpose. That would be a violation of trust.

I am guessing that if UAC can be purposely bypassed, it can somehow be accidentally bypassed.

Today QWin updated for me as well, and it did NOT bypass UAC.

retird

https://community.quicken.com/discussion/comment/20438431#Comment_20438431

My thoughts exactly……

Chris_QPW

I have seen this mentioned before where for some strange reason and only for some releases of Quicken the UAC was bypassed.

Since it isn't on every update it tends to quickly get forgotten/lost in the past.

retird

https://community.quicken.com/discussion/comment/20438440#Comment_20438440

I wonder if it could be that Q bypasses UAC while building and testing an update for eventual release? And could Q have released a test update to us instead of the real final update which they quickly took down the test update and then put up the real final update? Possible I guess……

As stated in another thread when I started Q on a second computer later in the day it didn't auto-update which is as it should be because both computers UAC is set to not auto-update. Been that way for years.

splasher

https://community.quicken.com/discussion/comment/20438513#Comment_20438513

If Quicken is doing a staged release, they may have reached their cut-off number of installs between the first and second computers starting of Quicken, so the second didn't get it offered. It doesn't mean that the patch was pulled.

retird

https://community.quicken.com/discussion/comment/20438520#Comment_20438520

I got offered the R57.12 release but it didn't auto-install….. my UAC stopped it from auto-install as it has done for years

Chris_QPW

https://community.quicken.com/discussion/comment/20438513#Comment_20438513

I have never looked into the details of UAC and such, so I can't really say, but I wouldn't think it was anything they did intentionally during the build process.

retird

No reason found as to why R57.12 auto-installed with UAC being set so it would not auto-install: I'm at a loss and puzzled why this took place.

Side note not related to UAC but puzzled : After checking Quicken Preferences I found two settings that were different than my default settings that were in place for years.

Manual Backup: My default has always been 3 times but was set to 1 times so I changed it back to 3 times as after auto-install of R57.12 it was asking to manually backup after every session of Quicken.

My default has always been "Confirm possible transfers…" but was set to "Automatically create transactions…." after R57.12 so I set it back.