One step update.... moving me one step closer to ditching this program, once again.
Why is this so hard?
Why does it get stuck so often? (Like, every time I try it?)
Sigh.....
Quicken 2009 H&B, R6.
Hit One Step Update... enter my Vault PIN.
All arrows just go into circle mode. No institution will update.
All stuck on "Update".
My internet connection is fine. Nothing has changed with any firewall settings.
Exit Quicken. Of course, qw.exe is still running.
End Task that.
Go back in.
Pick any random instituion off the Online Center dropdown.
Update just that one. It works, of course.
Re-run One Step Update. It works, of course.
It's *like* quality software. But completely different.
And don't get me started on the obscene amount of screen flashing that goes on (that Quicken has never acknowledged as a problem, to anyone on the planet).
This problem seems to be quite uncommon but you are not alone. It plagued me on and off after I switched to Vista on a new Dell computer. It would mysteriously appear, stay around for a month or two, disappear for a month or two, reappear, disappear, ...
Finally I saw a Quicken Forum post that noted a correlation between this problem and Scheduled Bills & Deposits with "How Often:" set to "Estimated Tax". I changed all of these to "Quarterly"; this error immediately disappeared and I haven't seen it again in the 5 months since I made this change. Since the payments aren't actually quarterly, I just adjust the next date each time I make a payment - a nuisance but not as bad as the problem that *seems* to be fixed.
I'd appreciate you and others posting back whether or not this works for you. Credit or blame goes to the Quicken Forum poster.
I see the same thing with Q 2009 Deluxe. For me, it is the stock quotes. If I remove that from one step update, the rest of the update works perfectly. I've taken to running stock quotes by themselves. They still hang sometimes, but they don't prevent updates of my banking and investment accounts.
Eric - I can't help you with the updating except to say mine works fine QD2009 on XP Pro.
The flashing however has been discussed here a number of times. It has to do with the Intellipiont mouse driver. I can not remember what exact version causes the issue but if you go back to one later it will disappear. This I was able to resolve. Perhaps someone else can remember the version details if you can't find it in the forum.
I think there can be multiple causes for "flickering"; one of which is, I believe, a shortage of some memory/memory-related resource. Quicken itself may be a faulty consumer of that resource. One workaround would be to shut down all applications, including Quicken, then restart Quicken.
I had lots of flickering with a logitech wireless mouse. As soon as I took it off the system, Quicken ran much better, even though it was still using a Logitech wired mouse.
Many reports of problems with Logitech wireless mice and Quicken if you search Google.
I've been through this for years. I've seen nothing but horror stories on the Quicken Communities boards regarding screen flickering - going back to version 2007, and maybe earlier. I just had an opportunity to take 2009 Deluxe for a test spin and found the same problem. My screen flickers and redraws so often this application is totally unusable - unless experiencing epilectic seizures is your idea of a good time.
Suggested fixes there included and entire gamut of possibilities, including changing PDF driver settings, changing fonts, lowering screen resolutions & video driver acceleration, removing USB devices, and uninstalling MS Intellipoint. None of these "solutions" came from Intuit mind you, just users, as Intuit seems content to pretend the problem doesn't even exist.
From all the different "solutions" posted there, two things seem to be clear; .. that Intuit has absolutely no idea what's causing this problem, and that they have absolutely no intention of fixing it. None. Zero.
I run dozens of applications on XP-SP3 & Vista systems here and NONE of them seem to have this problem. CLEARLY this is an issue with Quicken, even though it is more expedient and fashionable these days to place blame elsewhere. (I especially liked one post there that contained a reply from Intuit claiming that this was "not a known issue" - why then the dozens of pages in their forums stating otherwise??) Besides, why should I have to reconfigure my hardware just to accomodate one ill-behaved (poorly written) application?
It looks as though once Quicken development moved offshore, all semblance of customer support and quality control went with it...
Of course the usual tribe of self-appointed Intuit apologists will be showing up any time now to refute all this...
dieHard® wrote in news: snipped-for-privacy@4ax.com:
Right.... if the solutions are all different, and bordering on voodoo, then it's clearly not a mouse driver or screen driver or Firefox or SP3 or Dell or keyboard problem.
The one constant in the flickering is Quicken.
It's really a shame that that just took their marketing dominance, killed MSFT Money, and then stopped giving a shit about their customers.
There is truth in both of the above apparently contradictory opinions. Sometimes a logical fix works, sometimes voodoo, all too often neither.
The vast majority of users seem to have none of these mysterious problems. But when they do occur, it seems that only Quicken is affected.
Why Quicken? Perhaps because it's a heavy resource user that is more heavily coupled to the OS than most other applications. Both Quicken and the user's machine place great stress on each other.
I've had several of these problems (one-step update hangs, won't print, won't terminate) and I've found "voodoo" fixes for *all* of them. But I have yet to see sufficient evidence to either blame or exonerate Quicken for
*any* of them.
It's unfair to blame Quicken without more proof. But it's equally unfair to claim that there is anything even remotely approaching a satisfactory solution to these frustrating problems.
Jerry Q08 H&B, Vista SP2, IE8, Lexmark X5495, Dell XPS410, lots of other flakey applications, drivers and ActiveX controls :-)
sQueezBox® wrote in news: snipped-for-privacy@4ax.com:
I have had only occasional issues with Quicken. But it is by far not what it should be, witness the complaints here. However, because of the nature of PC computers with the almost infinite number of combinations of hardware and software (some of it really less than compatible with the OS), it is hardly surprising that there are intractable problems.
Maybe one way to separate hardware and software problems is to reboot in safe mode and see whether the problem persists. I am clearly not giving solutions here. Sorry about that. I am relatively satisfied with what Quicken does for me ... In fact, it is one of the few things (but definitely not the only one) that keeps me from switching to Linux/Ubuntu.
This is a great troubleshooting idea. You may get less fancy but much more reliable generic drivers for things like your screen and mouse. All sorts of startup applications that could be causing your problems may not be running, such as your firewall and antivirus programs.
In addition, if you use Safe Mode with Networking, you get (with Vista SP2 and IE8 at least) an instance of IE with most toolbars and ActiveX controls eliminated - these are notorious causes of system instability. Quicken probably isn't fully functional, but everything I tried, including One-Step Update, seemed to work OK. It's dangerous to go online with no firewall or A/V protection but it may be worth the risk for brief troubleshooting tests.
There was a problem with Quicken and scrolling a while back; virtually every Quicken user with the problem claimed that it only affected Quicken. Trouble was, the claims weren't true.
It's not that the users weren't telling the truth: they undoubtedly were being truthful when they said they did not see the problem with any other software they checked, but they clearly didn't check all the software out there (who could?).
Eventually a developer of game software published the cause of the problem (because it was afftecting gamers big time); Microsoft had changed their mouse driver logic for Vista. They changed it so that the example code for processing scroll wheel movement that Microsoft had provided to developers for Windows XP ... would no longer work in Vista ... and MS didn't send out any notification of the change. Any developer who had followed the example code from Microsoft, which worked in XP, would find their code would not work in Vista. Neither developers nor users expect their devices to stop working correctly when they change operating systems ... though device driver problems are notorious when a new os is released.
HP released (or is still releasing) new printer drivers for another print problem that Quicken users were experiencing ... only in Quicken.
Testing to see whether a problem occurs in more than one application is a good start to analyzing the problem ... but it is not definitive. PCL (Printer Control Language - which is what most all HP printers use) has hundreds of instructions; just because Word and Excel do not experience problems printing doesn't mean that, if Quicken does, it must be a Quicken error. Quicken is not necessarily using only the exact same PCL instructions that Word or Excel use. If one application uses a PCL instruction that is broken, it may appear that the application is at fault when it is the printer driver. HP has a history of introducing bugs into new printer drivers going way back (but they eventually fix them).
I agree.
Some of those problems (one check printing issue in particular, for example) have Intuit kb articles available; and quite a few users have found the kb articles correctly address their problem and provide a workaround. The specific printing kb article makes it clear that Quicken IS the cause. I have seen no evidence that Intuit tries to hide problems that they know they have caused. Like any good software developer, they want to know about bugs, contrary to claims by malcontents. [Just in case you don't already know it: I definitely do not put you in that league at all.]
My beef is with the claim that no non-Quicken causes of the problem exist. I did not say (nor do I believe) that everyone has found a solution, just that those who have publicly posted that they found non-Quicken solutions to the problem can not be ignored or thought of as liars. Their public statements disprove the claim by the poster I replied to. There are multiple causes/contributors to the problem and denying their existance is just plain bull.
Finding and fixing software problems can sometimes be much more complex than users want to believe; but that's no excuse for making false claims. Folks who don't have the necessary evidence, shouldn't even be drawing conclusions, much less publicly stating those conclusions as facts.
BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.