Runtime error 482 usually appears when you try to print a document in Windows. The error is caused by the Visual Basic “Printform” component.
As a general rule, “runtime” errors are usually the result of problems within the “Visual Basic” library or its adjacent applications. Most errors are caused by an inconsistency within the code (referencing variables that don’t exist) or by having trouble referencing specific libraries.
Whether you are actively using “Visual Basic” or not is irrelevant; it is probably being used by one of your applications, hence the error.
To resolve the issue, there are a number of steps you can take, though many people end up resorting to “workarounds” to prevent it from displaying. The steps outlined in this tutorial should give you the ability to fully resolve it.
Cause
The error will usually be displayed with the following messages:
- “Run-time error ‘482’: Printer error”
- “Run-time error ‘486’: Unable to print form image on this type of printer”
- “Printer Error”
The most important thing to note about the error is that it is caused by what is known as a “library” in computing. A library is essentially a piece of code that allows a developer to access a particular functionality without having to rewrite the code.
Libraries have been used since the early days of computing. With modern computers, thousands of libraries can be employed at once to provide very high-level functionality to a variety of applications. “PrintForm” is one such library.
Mostly the case is that your system will not have the “Printform” library installed (it’s very old), which causes the error to be displayed. It may also be the case that your printer, or its associated drivers, are damaged.
Solution
The steps to solve the problem are as follows:
-
Remove any reference from PrintForm in VBA
If you’re seeing this error as a result of using a “Visual Basic” technology application (including VBA), you’ll also want to make sure you get rid of any references to the PrintForm component. The best way to do this is to replace it with the Win32 API, which is an updated version of the print library in Visual Basic. If you do this correctly, it should allow printing to work with your apps like Windows 10.
-
Update printer drivers
If you’re not using Visual Basic/VBA, you’ll want to make sure your printer drivers are fully up-to-date and correct. The best way to do this is to completely “uninstall” the printer from your system and let Windows Update find the correct drivers (unlike earlier versions of Windows, the latest Windows Update is actually very good and effective). To do this, simply press the Windows + S keys on your keyboard, type “Device Manager” and select the first option that appears. When you’re in Device Manager, select the printer you’re having trouble with, right-click it, and click “Uninstall.” After the uninstall, restart your PC. It should automatically add the printer again, installing the latest drivers, if effective.
-
Clean system files with SFC
If the above doesn’t work, it *might* be a problem with your computer’s core system files. To fix this, you can use a built-in mechanism to fix it (SFC // System File Checker). To do this, press the Windows + S keys on your keyboard and type “CMD”. When the options appear, right click on the first one and select “Run as administrator”. This will open the black and white CMD window. In it, type “sfc /scannow”. This will scan your system files and repair any that are damaged.
-
Switch to using other printer settings
If all of the above doesn’t work, you’ll want to consider using a different printer. The most typical way to do this is to switch from using the standard “Print to PDF” option to “Microsoft Print to PDF” to make it work.
