The 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 of thumb, “run-time” errors are generally the result of problems within the “Visual Basic” library or its adjacent applications. The errors are mainly caused by an inconsistency within the code (referencing variables that do not exist) or having trouble referencing specific libraries.
Whether you are actively using “Visual Basic” or not is mostly irrelevant; it’s likely one of your apps is using it, hence the error.
To solve the problem, there are a number of steps you can take, although many people end up resorting to “workarounds” to prevent it from showing up. The steps outlined in this tutorial should give you the ability to figure it out completely.
The error will normally show up with the following messages:
- “Runtime Error ‘482’: Printer Error”
- “Run-time error ‘486’: Cannot print form image on this type of printer”
- “Printer error”
The most important thing to keep in mind about the error is that it is due to what is known as a “library” in computing. A library is essentially a piece of code that allows a developer to access 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 used at once to provide very high-level functionality to a variety of applications. “PrintForm” is one of those libraries.
It is mostly the case that your system does not have the “Printform” library installed (it is very old), which causes the error to be displayed. It may also be the case that your printer or its associated drivers are corrupted.
The steps to solve the problem are as follows:
Remove any reference from PrintForm in VBA
If you see this error as a result of using an application powered by “Visual Basic” (including VBA), you will also want to make sure to 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 Visual Basic printing library. If done correctly, it should allow printing to work with your apps in Windows 10.
Update printer drivers
If you are not using Visual Basic / VBA, you will 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 previous versions of Windows, the latest Windows update is actually very good and effective). To do this, simply press Windows + S keys on your keyboard, type “Device Manager” and select the first option that appears. When in Device Manager, select the printer you are having problems with, right-click and click “Uninstall.” After uninstalling, 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 * could * be a problem with your computer’s core system files. To work around this problem, you can use a built-in mechanism to solve it (SFC // System File Checker). To do this, press Windows + S keys on your keyboard and type “CMD”. When the options are displayed, right-click the first one and select “Run as administrator”. This will open the CMD window in black and white. In it, type “sfc / scannow”. This will scan your system files and repair the damaged ones.
Switch to using other printer settings
If all of the above doesn’t work, you’ll want to use 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” for it to work.