R39.17/R39.21 Paycheck Corruption [Edited]
Answers
-
@Chris_QPW
For you, does R39.23 also fix the issues with screens displayed by Quicken's web browser, such as the Investing > Allocations Rebalance Portfolio button and the LTP Change Assumptions?
One way to find issues caused by 39.17 and 39.21 is to compare the account balances in the Net Worth and Portfolio Value reports to the account registers and the Accounts bar. If your file has been corrupted, the report balances will be different from the register and Account Bar valances. Are the balances OK for you?QWin Premier subscription0 -
Nope. Still broken.Jim_Harman said:@Chris_QPW
For you, does R39.23 also fix the issues with screens displayed by Quicken's web browser, such as the Investing > Allocations Rebalance Portfolio button and the LTP Change Assumptions?
One way to find issues caused by 39.17 and 39.21 is to compare the account balances in the Net Worth and Portfolio Value reports to the account registers and the Accounts bar. If your file has been corrupted, the report balances will be different from the register and Account Bar valances. Are the balances OK for you?Signature:
This is my website: http://www.quicknperlwiz.com/0 -
I can confirm a similar experience to that of Lloyd Smith above. After 39.17/39.21 all monthly pension splits from 1/1/2005 to 11/1/2021 were damaged as reported by others. Updated to 39.23 this morning and restored data backup from the 38.30 update. Splits from 1/1/2005 to 12/1/2019 were fixed. The splits from 1/1/2020 thru 11/1/2021 now show zeros for all entries, which is different from the scrambled entries that were there previously. Not sure what to do now. At least only 23 entries are messed up now instead of over 200.0
-
In that case I would suggest submitting a problem report with a sanitized data file.PhotoMike said:I can confirm a similar experience to that of Lloyd Smith above. After 39.17/39.21 all monthly pension splits from 1/1/2005 to 11/1/2021 were damaged as reported by others. Updated to 39.23 this morning and restored data backup from the 38.30 update. Splits from 1/1/2005 to 12/1/2019 were fixed. The splits from 1/1/2020 thru 11/1/2021 now show zeros for all entries, which is different from the scrambled entries that were there previously. Not sure what to do now. At least only 23 entries are messed up now instead of over 200.
And then going back to R38.30 EDIT: and of course, going back to a data file before the corruption started).
Also, if anyone is using Sync to Mobile/Web I suggest trying these things with it off. Sync to Mobile/Web has been implicated in causing similar problems for months if not years. This is little chance that the fixes they put in for the R39.17/R39.21 corruption has anything to do with this other corruption that Sync to Mobile/Web was causing.Signature:
This is my website: http://www.quicknperlwiz.com/1 -
Is it possible/reliable to go backwards from R39.23 to R38.30 by simply applying the Mondo Patch, or must one uninstall Quicken, reinstall, and then apply the patch? Being a retired software manager, I'm skeptical about a simple backwards revision process. This question is probably covered elsewhere in the Community. I'll look.0
-
Reverse patch works "most of the time", but not always. In my opinion going from R39.23 to R38.30 will work, but you probably want to remove the C:\ProgramData\Quicken\Cache for the embedded web browser problem.PhotoMike said:Is it possible/reliable to go backwards from R39.23 to R38.30 by simply applying the Mondo Patch, or must one uninstall Quicken, reinstall, and then apply the patch? Being a retired software manager, I'm skeptical about a simple backwards revision process. This question is probably covered elsewhere in the Community. I'll look.
Here are a couple of posts that will help so you don't have to search.
https://community.quicken.com/discussion/7909968/revert-back-to-older-version
Signature:
This is my website: http://www.quicknperlwiz.com/0 -
Update. I removed C:\ProgramData\Quicken\Cache, and it seems to be fine now.Chris_QPW said:
Nope. Still broken.Jim_Harman said:@Chris_QPW
For you, does R39.23 also fix the issues with screens displayed by Quicken's web browser, such as the Investing > Allocations Rebalance Portfolio button and the LTP Change Assumptions?
One way to find issues caused by 39.17 and 39.21 is to compare the account balances in the Net Worth and Portfolio Value reports to the account registers and the Accounts bar. If your file has been corrupted, the report balances will be different from the register and Account Bar valances. Are the balances OK for you?Signature:
This is my website: http://www.quicknperlwiz.com/1 -
I have also tested on 39.23 and all 39.xx problems are fixed for me.1
-
@dalehawaii
I followed your instructions above and restored to R38.30 then restored several backup files dating as far back as 2/28 but continue to find no split transactions of any type prior to 10/28/21. Any further suggestions?0 -
When you restored to R38.30, did auto-update move it to a higher version? I had to disconnect the internet while installing and then turn auto-updates off0
-
@kingmm01
I did validate that my software was restored to R38.30. All split transaction information between 4/12/17 and 12/31/21 is gone.0 -
Just to wrap things up, I want to report that I waited to upgrade to R39.23. I then went to the backups sub-folder and grabbed the one whose filename started with Current-R38.29 (I had skipped R38.30), which was automatically created just before Quicken upgraded from R38.29 and was my last non-corrupt file. FYI, you can just copy this file up a directory and rename it to Current.QDF (the format is the same) rather than going through the Restore process on the menu.
From there, it was an arduous process to re-do every transaction I had done since that backup was taken. It was made a lot easier because I loaded my latest file on to another computer, which I could interact with on a second screen.
A few words about validation: I use it any time something wonky happens. When I had R39.17, it reported damaging thousands of records (forcing me to restore from the pre-validation backup). It did the same to old backups, when I was running from R39.17. Of course, the files were corrupted by this release, and validation only made it more obvious. When I switched to R39.23 and restored the same backup, not only did the transactions that always were bad now look good, but validate was now fine with the file. This was therefore proof that the software and my file were alright. I backed up and ran it several times as I was re-doing my transactions, and it was fine the whole time.
Thank you @Quicken Anja for taking this seriously and escalating. I have one piece of parting advice for you to pass on: The release notes say:
Version R39 R39.23 (Mar, 2022)
What’s Fixed
· Some paycheck splits were disappearing or causing crashes.
· Issues with data file creation and synchronization during some account migrations.
Nowhere does it tell users who may not do a validate and may not inspect their old records for inconsistencies that their data file has been corrupted. It doesn't tell them to see if they ever ran either of the two earlier releases (by checking filenames of automatic backups) and therefore need to stop now, take notes on what they will have to reproduce since their last pre R39.17 backup, and then restore that backup and re-enter those transactions. Without that guidance, each of these users will eventually discover the problem after some unknown amount of time, only after adding more and more records. Then, you will have to pray that they still have those backups, and tell them that they may have to re-enter months or years of transactions after they restore it, when it might have only been days or weeks if they had been told now. If that happens, and Quicken could have prevented it now, then the repercussions could be enormous.1 -
For what it's worth, I had the same problem with the paycheck splits showing the one in the bill reminder rather than the actual one I recorded. After installing R39.23, I used OneDrive to restore the most recent backup that didn't have the messed up Paycheck splits. This was about 5 days old. After that, I performed a Sync just to see what would happen. The newer transactions came back in, and the splits for the paychecks were still showing correctly. Only minor issue is an account I previously didn't have set to sync showed up as Unspecified Account but it was easily fixed.0
-
@George P Agree. That's why I posted this under "new idea".Help us out by up voting. I think there could be quite a few users who won't discover this issue until down the road where it will be way too late to "easily" correct with a revert to R38.30 and a restore to a file prior to R39.17.
0 -
Based on the above comments, it sounds like the general consensus is that the paycheck split problem has been corrected in 39.23 and should not be an issue if I update directly from 37.67. Is that a fair read?
@Chris_QPW
You said you "removed" C:\ProgramData\Quicken\Cache to fix the Quicken browser problem. Did you clear the contents of the folder or trash the whole thing?0 -
I deleted the whole thing. It will just get recreated.mrzookie said:Based on the above comments, it sounds like the general consensus is that the paycheck split problem has been corrected in 39.23 and should not be an issue if I update directly from 37.67. Is that a fair read?
@Chris_QPW
You said you "removed" C:\ProgramData\Quicken\Cache to fix the Quicken browser problem. Did you clear the contents of the folder or trash the whole thing?Signature:
This is my website: http://www.quicknperlwiz.com/0 -
@Jim_Harman, my paychecks did get messed up. I looked and there was my split information and my total wealth seemed correct, but I just compared to an actual pay stub and it was messed up. Now I am sad.0
-
I validate my file weekly with no issues. I installed patch R39.23, after running a validate, my paycheck splits disappear. I backup my file daily, so I restored a backup.0
-
-
> @"Quicken Anja" said:
> Hello All,
>
... The more problem reports we receive, the better.
>
> We apologize for any inconvenience in the meantime! Thank you.
I LOVE this answer :smiley: !1 -
Quicken - this entire fiasco with the botched-up update was just too much. After finding a backup before this release (thanks to Google Drive's version history) I have reverted back to the Quicken 2017 Deluxe version and am now giving up my subscription because of this issue alone. It has given me much more peace of mind, and in the process made me realize that since I do manual entries, I am not missing a single feature from the past 4 years worth of Quicken updates, despite my heavy reliance on investing, budgets, etc.5
-
I updated to R39.23 on 3-12 and the report problems still exist ie. register balance does not agree with Net Worth and Account Balances report for 2 of my checking accounts. The register balance is correct but the NW & AB reports are overstated.2
-
Gck# said:I updated to R39.23 on 3-12 and the report problems still exist ie. register balance does not agree with Net Worth and Account Balances report for 2 of my checking accounts. The register balance is correct but the NW & AB reports are overstated.
@Gck#
Had you previously installed R39.17 or R39.21, which were released last week?
After updating to R39.23, did you revert to a backup from before the first of those was installed? If so, had you previously opened this backup file while R39.17 or 21 was installed?
QWin Premier subscription0 -
I noticed the corruption in the paycheck details after I had installed 39.17 and then ran a Validate and Repair operation. I installed the new version 39.23, and I reverted to a data file that was backed up on March 4, when I had installed 38.30. Before I reverted to the old data file, I took screenshots of all my recent transactions since March 4. So, fortunately, I was able to rebuild the new transactions without too much effort.
I would like to say, though, that this issue is somewhat concerning from a quality control standpoint. The data file should always be preserved, at all costs! We are lucky that we have access to the great support on this community. But what about all the users who don't have access or don't know about this community? I genuinely feel sorry for them.QWin Premier user since 1997. QWin Premier subscription on Windows 10 & 11. I don't use mobile & web or bill pay.2 -
@Roger Miller I agree that this community is actually very good. I would not have known my data file was actually corrupted without all the feedback. I looked at my paychecks and thought they were fine but then I noticed the numbers were off when I went back a few days later.
I spent a lot of time to fix my file - I had a backup from last week so I took a screen shot of every account, then restored my last known working backup, then went through each account to make sure I had all the transactions. It just took a long time to make sure I did it correctly and found the latest working file and it was tedious, but now I am good.
I also agree - I thought a reconciled transaction was "locked" and wouldn't be able to be changed without the data file password, but now I know this is not true.1 -
@Jim_Harman My first communication regarding this was on 3-9-2022 with Quicken Support and at that time I was on R39.17. The support person indicated that R39.21 was the latest, however when I checked Quicken online version 21 was not available to me. During this session we restored a previous backup from Mar 7 and that made no difference, we also did a validate and repair and that made no difference. I have yet to restore a prior backup since installing R39.23.0
-
@Gck#
Once you have installed R39.23, which fixes this problem going forward, you need to restore a backup from before you installed R39.17. This would be about March 4. See this Announcement
https://community.quicken.com/discussion/7909593/windows-r39-xx-release-us
You will have to re-enter any transactions you entered since then.
QWin Premier subscription2 -
> @Sherlock said:
> I cannot explain why customer service would say there is no way to revert. Perhaps they know their instructions, as written, do not work reliably: https://www.quicken.com/support/reinstalling-and-patching-your-quicken-subscription-version-after-your-membership-has
Customer service is quite frankly a joke. I've had these types of issues for years with them... I guess we are the fools for continuing to pay for this junk of a product.> @Quicken Anja said:
> Hello All,
>
> Thank you for taking the time to visit the Community and reporting this issue, though I apologize that you are experiencing this.
>
> I have forwarded this thread and the information you posted regarding this problem to the proper channels, and it is being investigated further. In the meantime, if you are experiencing this issue, we ask that you please submit a problem report by navigating to Help > Report a problem. While you will not receive a response through this submission, these reports will help our teams in further investigating the issue. The more problem reports we receive, the better.
>
> We apologize for any inconvenience in the meantime! Thank you.
Inconvenience? That is what you call it when years of financial data is corrupted? This isn't an inconvenience, it > @Amo1 said:
> I just updated to R39.17 today. Upon updating, my historical paycheck information is not correct. What is odd is that the register still shows the correct total amount deposited into my bank account, but when I click "open the split transaction window" (the green checkmark within the register transaction) that amount no longer ties to the register. Again, very odd that the register shows a different amount than the split transaction window. This issue is not only limited to recent paychecks, as when I click on "open the split transaction window" for any of my historical paychecks, they all show the exact same information and $ breakouts, which also do not tie to the register. In addition, my reporting is now not correct either, as it seems to tie to the split transaction data.
>
> Another important piece of information: I did notice that the itemized breakouts exactly tie to the paycheck reminder that I had set up, appearing that Quicken overwrote all of the split transactions with that reminder data. I tried deleting that reminder, but that did not solve the problem. The issue also only appears to have happened for the paychecks that are related to my current employer (which again makes me assume that this has something to do with the paycheck reminder), but since I have been with this employer since 2018, MUCH of my income data is now not correct. My paycheck amounts vary greatly from month to month, so the differences between the register and the split transaction data is quite large.
>
> I make religious file backups, and I opened some random backups from 2018-2021, and the same issue is happening for all of them, which tells me that this is definitely an issue related to the current release R39.17. In addition, I am positive my data was correct two days ago (prior to the update to R39.17), as I ran a report for 2021 and all of the Quicken report data matched my paycheck data.
>
> Has anyone experienced the same problem? I just spent over two and a half hours on the phone with Quicken support and received different feedback from different people, including two supervisors. One of them mentioned that this may have something to do with an issue with taxable categories. I should also mention that they had me go through the process of "validating" the file, and this did not solve the problem. In order to rebuild all of this data manually would take days/weeks, so I am very concerned. Any help or insight would be greatly appreciated.
Same problem here. I believe you are correct in that the reminder changed actual past transactions. I also validated my file and almost had a heart attack when I saw all the "issues". The things that continue to happen with this software are really unbelievable. The suggestion to restore a backup is awful; it would take hours to redo the work - assuming I knew what all needed to be done. The takeaway is that we are paying for software to track our finances that is completely unreliable and the vendor apparently has no intention of changing it. This has been going on for several years.5 -
@Jim_Harman I restored a backup file from 3-1-2022 and that > @Jim_Harman said:
> @Gck# Once you have installed R39.23, which fixes this problem going forward, you need to restore a backup from before you installed R39.17. This would be about March 4. See this Announcement
>
> https://community.quicken.com/discussion/7909593/windows-r39-xx-release-us
>
> You will have to re-enter any transactions you entered since then.
I have restored a backup from 3-1-2022 and that cleans up the file to where Register, Net Worth and Account Balances reports are showing the correct balances. I will have to input the data going forward but I'm wondering if the reminder transactions that existed at that time for future transactions could be entered to eliminate some of the manual input effort? Also the same question regarding Investment and other financial institution accounts where usually download activity. Do you know if this would cause problems. Also what about future revisions from Quicken? Thanks for your efforts.1 -
Yes, you can accept the Reminders that are waiting in the restored backup. If you use Bill Pay, either bank or via Quicken, be careful not to re-issue bill pay instructions.
Transaction downloads should work normally, without duplicates.
Hopefully future releases of Quicken will not introduce problems like this.QWin Premier subscription2
This discussion has been closed.