badger411 said: As an aside, does anyone know why EVERY automatic update causes a meltdown in my program? I have taken to updating my data files in 4 different locations (C: drive, OneDrive, Carbonite, Dropbox) in case one of them gets corrupted. I never considered that the Quicken file itself could become corrupted and needed to have back-ups in multiple locations.
Frankx said: Hi @badger411,That being said, I am not convinced that the problem you are currently having was caused by the version update, as I have not seen any other reports (nor can I remember any similar posts that may have appeared here) that caused a previously "unlocked" (my phrase for a datafile that doesn't have a password) to become locked simply because it is opened in a different (newer) Quicken version.Frankx
mshiggins said: That is strange. I've been seeing posts about patches causing data files to suddenly have a data file password when there was previously no data file password for several months now.
That is strange. I've been seeing posts about patches causing data files to suddenly have a data file password when there was previously no data file password for several months now.
Frankx said: mshiggins said: That is strange. I've been seeing posts about patches causing data files to suddenly have a data file password when there was previously no data file password for several months now. Yes, there were posts back in early July after R34.20 was released that referenced a password problem. However R34.24 - which went live on 7/21/21 - fixed that issue (according to this Q Support post LINK.Since that time, I have seen no reports of this problem.The OP indicated that he last updated om 9/16/21, which presumably is to R35.31 which is 3 versions hence, which is why I suggested he reconnect with Support.Frankx
https://community.quicken.com/discussion/7898633/my-quicken-suddenly-doesnt-recognize-my-password
https://community.quicken.com/discussion/7897551/data-file-locked-with-a-password-the-forgot-password-link-doesnt-work
https://community.quicken.com/discussion/7898276/file-password-wasnt-accepted-after-update-to-35-26
badger411 said: > @Boatnmaniac said: > A couple of suggestions:* You are updating your data files in 4 different locations? I suggest you stop doing that. Updating data files in cloud accounts is a recipe for file corruption for a number of reasons, not the least of which is that a corruption in one of those files can and very possibly will pass that corruption on to the other data files. Each of those data files (assuming they are copies of the same data file) shares the same Quicken Cloud Account so there is some cross-talk that does occur. If you want to save back up files on some cloud accounts, then that should be safe. But you should only be opening and updating your Quicken data file from a local drive like C. > > * Change your User Account Control Settings to "Always Notify." This will then cause Windows to notify you when a program (like Quicken) is trying to update and you will then have the opportunity to stop it from updating or to allow it to continue. I am updating in multiple locations because I have experienced in the past that my local backup (and even my Carbonite backup) is overwritten when I am trying to recover data after an automatic Quicken update. It changes the file date to the current date and time, which makes it unusable as a representation of past data. It is a longstanding problem I have had with automatic downloads from Quicken.
volvogirl said: You can search your hard drive for all files ending in .QDF to find where they are stored.
badger411 said: > @Chris_QPW said: > In the current version of Quicken you can also use File -> Find Quicken Files... > It brings up this dialog: Finding my most recent files is not the problem. I have them on my Carbonite, Dropbox, OneDrive, and C: drive. After a Quicken automatic subscription update was downloaded last Thursday, my most recent backup won't open because they claim to need a data file password. They were NOT saved with a password. Password recovery link is inactive. Support stated explicitly that they cannot unlock the data file in question after 30 minutes. I have tried to revert to 2 previous Mondo patches, but the file still requires a data file password.