Hi MichelleBh!
Thanks for the post, but for most of us, all those steps, and several others have been tried, with little or no success. Something else we tried early on was the recreation of the Chrome profile in C:\Users\<username>\AppData\Local\Google\Chrome. Ordinarily, this forgives a multitude of Chrome sins, but had no effect on this problem. For my user, at least. If anyone tries this, I'd recommend just renaming the profile to something like Chrome.old, so you can easily roll it back if it doesn't help.
Also, I'm afraid that since Internet Explorer has reached end of life and is no longer supported, its use has become an unacceptable security risk. For testing and verification purposes though, I will briefly change the affected user's default browser to IE and see what happens, but QB should probably address that requirement.
As a bit of background, most of us with this issue seem to be running either QBDT-21 or QBDT-22 via the client-server model. QBDT-18 suffered from none of these problems, but from the day QBDT-22 was installed, for us at least, this has been a problem.
With the frustration many of us are experiencing, and in the interest of good customer service, it's really time for QB developers to dive in and figure out what's going on, and patch it.
