Missing Budget (R47.11)

Although the Missing Budget issue is being reported as resolved, I have encountered it again under R47.11. This happened after modifying a reoccurring reminder. When I saved the reminder, I received a message indicating that there was no budgets. Quicken was then not responsive and I had to close the App. When I reopened the App, the Budget was still not there. I did report the problem via the Quicken "Report a problem" feature.

Comments

  • Quicken Jared
    Quicken Jared Alumni ✭✭✭✭
    edited February 5
    Although the Missing Budget issue is being reported as resolved, I have encountered it again under R47.11. This happened after modifying a reoccurring reminder. When I saved the reminder, I received a message indicating that there was no budgets. Quicken was then not responsive and I had to close the App. When I reopened the App, the Budget was still not there. I did report the problem via the Quicken "Report a problem" feature.
    Hello @pspottswood,   

    We are sorry to hear about this issue with missing Budgets that seems to be continuing. Thank you for looking to the Quicken Community for more information.

    Currently, there is a new Open Alert regarding missing Budgets that is very likely relevant to your situation. You can view the link here for additional details and any future updates. We do not have an ETA on a resolution, for the moment, but our teams are working toward this as we speak.

    We are sorry for the inconvenience, and we thank you for your patience.

    Regards,

    Quicken Jared 
  • pspottswood
    pspottswood Member ✭✭
    For me, Quicken has gotten to the point where it is not functional. I have been trying to do 15 minutes of work over the last two hours and I am getting nowhere due to crashes, reminders that change on their own, the budget being lost, and crashes that as a result of clicking on the "OK" button after a backup. I've submitted numerous problem reports over the last several days pertaining to these issues. Quicken has simply not been functional for me since R47.7 was released.
  • BobbyP
    BobbyP Member ✭✭
    This has happened to me as well with the last release. Quicken is no longer the dependable app is used to be. I can't wait for someone to introduce a comparable app. I will jump ship from Quicken in a HEARTBEAT> All they every recommend is install new buggy releases and the one that makes me the most crazy, restore from backup which never solves anything. Their support has gone downhill as fast as their development team. They should see the handwriting on the wall and get their act together before the mass exodus and they will be gone, like every other company that stopped caring about their customers. Only if MS Money was only a little better.. I'd jump in a second.
  • kmc00
    kmc00 Member ✭✭
    You might argue this is off-topic but I don't know where to put it. I agree with the comments above. I haven't messed with budgeting it over a year but tried to get back into the swing this past weekend. Everything about budgeting seems so broken, I'm not even sure where to begin. You can't print a simple annual budget, the sub-categories have disappeared, if you don't select every single budget sub-category the budget will not roll up the total to the parent category--it just shows as 0 budget.

    I have been using Quicken since the days of Windows 3.1 (early 90s) but I'm reaching the point where this simply is no longer worth it.
  • StanleyK
    StanleyK Member
    Concerning the issue with the budget disappearing, when I opened my budget on 2/6/23, the first time after the 47.11 update, my budget was not totally gone, but corrupted. Some categories were there, others missing, and some had gibberish characters. I deleted the budget and all budget data and created a new one from scratch. So far it seems stable
  • pspottswood
    pspottswood Member ✭✭
    Although it does not clear up the issues, I found that installing the Mondo Patch for R47.11 and running Validate, an error was found that was not was not found prior to running the patch and there was a single issue that I was encountering that I was finally able to overcome.
This discussion has been closed.