Wrong Password

Hi, Robert.

My wireless keyboard often produces the not-recognized problem, too, but Quicken then gracefully allows me to try again and accepts my password on the second try.

As it says in my Sig, I'm using Q2012D in Win7 Ultimate, and I just replaced my older Microsoft Wireless Desktop 6000 with a newer 3000 (because the old one was suffering from cookie crumbs and a spilled milkshake). The two keyboards perform alike.

Are you trying to run OSU immediately on startup of your computer, or of Quicken, before the keyboard driver is fully ready? My system boots up slowly; I have time for coffee and a bowl of cereal before it is fully booted in the morning. But then I just start Quicken and WLM, and OSU is one of the first things I run. (I usually use the + shortcuts to start the apps.) But if I try to start the apps too soon, I just have to wait until Win7 is fully awake before Quicken loads and I can finally type in the password.

RC

-- R. C. White, CPA San Marcos, TX (Retired. No longer licensed to practice public accounting.) snipped-for-privacy@grandecom.net Microsoft Windows MVP (2002-2010) (Using Quicken 2012 Deluxe R 5 and Windows Live Mail in Win7 x64)

When Windows starts up, I'm prompted to enter my password vault password as expected. I have a new computer that doesn't recognize my wireless keyboard as quickly as my previous computer did. This results in it dropping the first character on occasion, which the Quicken baagent.exe process dutifully informs me means my password is incorrect.

Unfortunately, Quicken proceeds on its merry way and I don't see any way to reenter the correct password short of logging out and back in or killing the baagent process and restarting that. Am I missing something?

That's the behavior I see as well, if I'm trying to access the password vault to do an OSU after the machine is up and running.

I have QD2012 running on Win 7/64 Professional, but I check the box in scheduled updates that says enter the password on Windows startup, rather than each time the scheduled OSU runs. Checking that box puts a small program called bagent.exe in one of the run keys of the registry, which in turn prompts for the password vault password when the computer first starts up.

For some reason, that dialog only allows one attempt at password entry. I don't reboot that often, so it isn't a big deal. Just wondered if I was missing something.

Hi, Robert.

OK. This is a significant difference in our use pattern. I don't use Quicken's scheduled updates, although I have been tempted. Quicken is usually started (manually) first thing each morning and stays on - in the background - all day. After running OSU early to see what transactions have occurred overnight, I leave Q running to record transactions during the day and in case I need to check on any history (Where did I buy this keyboard?), and then run OSU again after the markets close (after 4 pm CST to be sure to get closing quotes). I'm prompted for the password every time I use OSU, but not at startup. So I have no experience at all with bagent.exe.

My way works for me, but it doesn't help for your way. :^{

Let us know when you figger it out; I'm sure others will be interested.

RC

-- R. C. White, CPA San Marcos, TX (Retired. No longer licensed to practice public accounting.) snipped-for-privacy@grandecom.net Microsoft Windows MVP (2002-2010) (Using Quicken 2012 Deluxe R 5 and Windows Live Mail in Win7 x64)

"R. C. White" wrote:

That's the behavior I see as well, if I'm trying to access the password vault to do an OSU after the machine is up and running.

I have QD2012 running on Win 7/64 Professional, but I check the box in scheduled updates that says enter the password on Windows startup, rather than each time the scheduled OSU runs. Checking that box puts a small program called bagent.exe in one of the run keys of the registry, which in turn prompts for the password vault password when the computer first starts up.

For some reason, that dialog only allows one attempt at password entry. I don't reboot that often, so it isn't a big deal. Just wondered if I was missing something.