I am using QB Pro 2012. Aparently after a recent Win10 update I am unable to preview or print invoices. I am able to print reports. I am unable to get to the screen that verifies the attributes of the invoice form and the printer to send it to. I have uninstalled and reinstalled QB. I have restored to a previous backup date and back. I have downloaded and run QB printer tool repair. This actually did get me to the screen but could not find the printer and then stopped working again. Also in printer setup it defaults to ‘print reports’ when I check ‘print invoices’ and make changes it posts a message apologizing for the unconvinced and give an code 15185 xxxxx (it changes) I would upgrade to QB2018 if I could be sure this would over come the issue. Where can I find answers?
(Title has been edited by moderator for clarity)
Solved! Go to Solution.
Ray, Thank you for your response. To be clear, I have been operating QB Pro 2012 within Windows10 for maybe close to a year. There are a few glitches, but nothing I couldn’t work around. This problem areared after an update to Windows10. Does that still sound like QB2018 upgrade would be the answer? I am fine with keeping my Quickbooks program current if it will work. Can I step up thru QB 2015 to QB 2018 without purchasing both?
I have this same issue with QB2018 desktop.
Extremely frustrating because it is eating up my time and preventing me from sending invoices- on paper or via email.
Renaming the file did not fix it. Using the download tool did not fix it.
What do I do now?
My issue came from some sort of corruption to my customized invoice template, according to QB Support. All I need to do is recreate my template. OK, not thrilled but at least now I can get back to work. How did it happen? I suspect that QB was open when my system updated.
Here's how we discovered the problem, in case it helps anyone else.
Try printing using the preinstalled QB invoice template. If that prints, it's the same problem I have. Also, whenever having problems, see if the same problem exists in the Sample Company file. That, too, sheds light on the source of the problem.