bpolson2 said: No, I don't have that many category splits. It's only split among three accounts. I notice in the projected balances that some bills scheduled in the future aren't being deducted close the closing balance column under projected balances. Same with one of the paychecks that is split between two different checking accounts, the total balance is showing only in one account and not in the other. When I look at the splits, they show up, but for some reason aren't being accounted for in projected balances. Hopefully all that makes sense?
Don32@ said: I have the same issue with my paycheck. The auto deposits are not showing on the projected tab. This is very frustrating. Is there a fix?
vic_user said: bpolson2 I was having this same problem. FYI: I had over 10 categories in my split. Boy, I wish my projected income looked like that for the next 12 months. Thanks for the temporary fix of going back to version 44.20. Any idea when Quicken is going to fix this problem? I really depend on the Projected Balances feature of this program.
In case of Patch installation error "Server file failed to load … Index and length …"please follow instructions here:https://www.quicken.com/support/patch-error-unable-check-updates-server-file-failed-loadIf the error message is about a file named "wyserver.wys", the problem is the Windows User Account name. If your Windows User files are located in a folder named, for example, "C:\Users\John Doe\..." (with a blank space between John and Doe) you need to create a new Windows User Account with Admin privileges and a name that does not contain a blank space, e.g., "John". Use the new account to install or update Quicken. Afterwards return to using your regular Windows User Account for running Quicken and doing all other work, as usual.
If the user name is not the cause, try to enable and use the hidden Administrator account. See https://www.howtogeek.com/howto/windows-vista/enable-the-hidden-administrator-account-on-windows-vista/ how to do that. Supposed to work in all Windows versions.
At your next migration to a new Windows version I recommend changing the username to remove the blank space. It appears to be a holdover from old Windows versions using the obsolete "Documents and Settings" folder structure.