Error when printing from Toolkit 6 in some versions of Windows

 

When trying to print from Toolkit 6, you might see an error regarding trouble printing. Sometimes the error will include a code 380 or 482, but more commonly, the error box will simply state that there is a serious error:

 

If you run into a printing error when using Toolkit 6, our primary suggestion is to use the Toolkit 6 Non-Admin icon. The steps to find the icon will vary, depending on your copy of Windows. Please check the heading below for your copy of Windows, to see the steps you will want to follow.

For Windows Vista or 7

  • Click the Windows logo Start button in the bottom left corner of your screen.
  • Click All Programs.
  • Click Toolkit6 from the list.
  • You will see four entries: Toolkit 6, Toolkit 6 Non-Admin, Toolkit 6 Manual, and unInstall Toolkit.
  • Choose the Toolkit 6 Non-Admin icon.
  • Toolkit 6 will open, and you should be able to print.

For Windows 8

  • If you are not already on the Windows Start Screen, click the Windows logo in the lower left-hand corner of the computer screen.
  • From the Start screen, click the Magnifying Glass icon, near the top right-hand corner of the screen
  • In the search box, type Toolkit; you will see at least four results: Toolkit 6, Toolkit 6 Non-Admin, Toolkit 6 Manual, and unInstall Toolkit.
  • Choose the Toolkit 6 Non-Admin icon.
  • Toolkit 6 will open, and you should be able to print.

For Windows 10 or 11

Note that Toolkit 6 was not tested on Windows 11, and use of Toolkit 6 on Windows 11 is not supported. The following steps may work, but we strongly suggest Windows 11 users transfer their information to the BetterInvesting online tools.

  • Click the Windows logo Start button, usually in the lower left-hand corner of the list of icons in the Task Bar.
  • Click All apps, If you don't see a list of currently installed programs.
  • Scroll down to the letter T, and look for an entry named Toolkit 6; it will look a bit like a manilla folder.
  • Click the entry for Toolkit 6, to reveal its contents, which will usually be: Toolkit 6, Toolkit 6 Non-Admin, Toolkit 6 Manual, and unInstall Toolkit.
  • Choose the Toolkit 6 Non-Admin icon.
  • Toolkit 6 will open, and you should be able to print.

If this does not resolve the printing issue, there are a few other steps we have seen work in some cases:

 

Try printing/saving to a PDF first:

  • Go to File > Printer Setup
  • From the drop-down list of printers, select Microsoft Print to PDF
  • Click OK

Using a PDF printer should allow you to create a PDF file, which, in turn, could be opened and printed where Toolkit was not able to do so.

 

Turn off Printer Spooling:

  • On most printers, you can turn off the spooler by going to Start > Printers.
  • Right-click on the icon of the printer you're using, and then left-click Printer Properties. (there are two 'properties' listings in the menu, make sure you are clicking on the one that says Printer Properties)
  • Select the Details or Advanced tab.
  • In the Spool settings, select Print Directly to the Printer.
  • This will tie up your application until the printer has all the data, but can result in slightly faster printing.

 

Another option:

  • Go to Start > Control Panel, and click on View Devices and Printers under the Hardware and Sound heading.
  • Right-click on the printer, but instead of looking for any note about it being default, left-click on Printer Properties (there are two 'properties' listings in the menu, make sure you are clicking on the one that says Printer Properties)
  • This will open a new window that will usually have between five and eight tabs, depending on the printer, and how it's set up.
  • Click the Ports tab, and then look near the bottom of the window.
  • Look for a check-box titled Enable bidirectional support.
  • If this box is blank, then close the Window, and try a different option; if it does have a check mark though, then click to un-check that box, and then click OK at the bottom of the window.
  • Restart the computer, and try Toolkit again.