Thanks for letting us know the result.
(and kudos to Tara for recomending msconfig instead of the direct startup and registry editing I suggested.)
Thanks for letting us know the result.
(and kudos to Tara for recomending msconfig instead of the direct startup and registry editing I suggested.)
Dropping the Keylogger Guard setting from High to Medium in Onguard seems to get around the problem.
I've now got the solution from PCTools. Go to the keylogger results screen and you'll see entries for the QB exe file there. Just click on one of them and enable the Allow file option. Alternatively enter the path manually in the keylogger screen.
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.