Runtime error 482 is caused by the inability of a system to connect to the Windows “Printform” library from applications that still use the VBA (Visual Basic) integration engine.
Although the error is displayed in Windows 10, it usually occurs when using Adobe Acrobat or another “Print to PDF” application.
The solution to Runtime Error 482 is to first make sure you have the correct printer installed (most don’t) and then if the error persists, change / remove any references to the printer settings from any VBA application.
If you see the error when you try to “Print to PDF,” you want to make sure you have the correct PDF drivers installed and that the application you are using is compatible with Windows 10.
The steps outlined in this tutorial should explain how to fix it …
Because
The underlying problem with Runtime Error 428 comes from the way Windows works with its underlying hardware.
When you use Windows, there are several “subsystems” that allow the system to connect with various peripherals and other devices. These subsystems are called “drivers” and require other software to connect to them.
It is the case with this error that the hardware you are trying to connect to your system is not responding, they will appear as error 428. Now, although the error used to be quite common (and still is for Windows 10), most of the people They are unaware of the cause of the problem and that it is actually caused by the Visual Basic runtime environment – a number of different files / applications designed to interface applications with deeper Windows processes.
Visual Basic is an old technology now, but it is still used by companies such as Excel and a number of third-party applications (including Citrix and Adobe Acrobat) to provide integrated functions for a system. It is this integration that is corrupted and corrupted on your PC (causing the error to be displayed). When you try to use the “printer” on your system, the problem is that the application you are using will basically use an outdated or corrupted version of the VBA Printform engine, which causes the error to be displayed.
The solution is to make sure your printer is installed and working properly, and then there are no underlying problems with your system.
Solution
While Microsoft recommends using the SFC (System File Checker) and DISM (Deployment Image Servicing and Management) tools to resolve any underlying issues with the system itself, the issue may be somewhat more acute / simple to deal with than that. .
We have found that it often happens that VBA is the problem, and by updating the application in question, or the underlying application, or the various redistributable VC ++ applications, to solve the problem.
That’s how …
1. Reinstall the printer
The first step is to reinstall the printer on your system.
This may seem drastic, but it is actually a very good way to resolve most “printer” errors, usually due to how printer drivers can sometimes get damaged or corrupted.
To do this, you need to follow the following steps:
-
Right click on the “Start” button (lower left screen)
-
Select “Device Manager”
-
Scroll down to “Printers”
-
Right click on any of the printers causing the problem
-
Select “Uninstall”
-
Follow the steps on screen
-
Restart your PC
After restarting, Windows 10 should automatically start adding the printer again.
To verify this, you can take the following steps:
-
Left click on the “Start” button (lower left screen)
-
In the “charms” menu on the left, select the “gear” (this is for the “settings” applet)
-
Click on “Devices” (top row)
-
In the menu on the left, select “Printers and Scanners”.
-
If the printer does not appear, select “Add a printer or scanner”
-
Follow the steps on screen
Let this process happen and then try printing with it again. If the error is not resolved or your printer is not listed, continue to the next step.
2. Clean the print queue
The next problem could be that the “print queue” has been causing problems.
The print queue is basically a queue through which Windows can manage the various print jobs. Anyone familiar with Windows 95/98 will probably remember the pleasure of dealing with a constantly corrupted print queue.
To resolve one of the most common reasons for a Runtime 482 error, you need to clear the print queue:
- Press the “Windows” + “S” keys on the keyboard
- In the search box, type “CMD”, right click and select “Run as administrator”
- Type: net stop spooler and then hit Enter
- Type (pay attention to spaces): DEL / F / S / Q% systemroot% System32spoolPRINTERS then hit Enter
- Type: net start spooler and then hit Enter
This will restart the spooler, having cleared any of the underlying queues / groups that may have existed on the system.
3. Reinstall the affected software
Several people have reported that the error occurs when using Adobe Acrobat, as well as other tools.
You need to reinstall any affected software because firstly there may be updates available and secondly there may be some underlying issues in terms of compatibility or the like.
Doing this (if you don’t already know) is relatively simple:
- Right-click on the “Start” button (lower left of the taskbar)
- Select “Apps and Features”
- From the list, select the application causing the errors
- Select “Uninstall”
- Allow the process to continue
- Restart your PC
- Install the software again (preferably by downloading the latest version from the Internet)
If you are an experienced computer user, you have probably already tried it. If not, you should at least make sure that the application that is causing the error is running as up-to-date as possible.
4. Reinstall .NET and VC ++
If the above doesn’t work, it * could * be the case that some of Windows’ core dependencies (libraries of software it uses to run) are corrupted, corrupted, or out of date.
There are two systems that are more relevant here: .NET or Visual C ++ (VC ++). Reinstalling both gives you the ability to make sure that your system can use the required files / settings for it to work properly …
- Press the “Windows” + “S” keys on your keyboard
- In the “Search” box, type “Control Panel.”
- Scroll down to “Programs and Features.”
- Look for lists of “Microsoft Visual C ++ Redistributable”
- From the list, make a note of the “year” number for any of the versions you have installed (eg “2012”), as well as the “architecture” version (x86 / x64)
- Right click on each one and select “Uninstall”
Once you’ve uninstalled them all (don’t worry, it won’t cause any harm to your system, although it will likely stop several apps from working until they are reinstalled), find your search engine of choice and type “vc + + download “.
The first result should appear with a page for Microsoft that shows the “latest supported Visual C ++ downloads”; this will give you a complete list of the libraries you just removed.
From the list, you need to download each one and install them again.
When you are done, you need to click “Turn Windows functions on or off” in the left pane.
Several “.NET” listings should appear at the top. Click on version 4.7 and make sure it is installed correctly. If not, we will have to reinstall it:
- Go to your search engine of choice
- Type “Download .NET”
- This should open a Microsoft “.NET Downloads” page
- Click on it and then download the latest version of .NET Framework
- Save it to your hard drive and let it install on your system
This should ensure that any application accessing VBA can access the correct files, etc.
5. Run SFC / DISM
Finally, you should watch the execution of the SFC / DISM tools.
These will not fix the error directly, but they will ensure that you have a system running as smoothly as possible …
- Press the “Windows” + “S” keys on your keyboard
- Type “CMD” and then right click + select “Run as administrator” in the application that shows
- When CMD loads, type “SFC / scannow” and press Enter
- Let the system run (it shouldn’t take too long) and it will resolve any issues it finds automatically
- After this, type the following: “DISM.exe / Online / Cleanup-image / Restorehealth” and hit “Enter”
- This should take much longer than SFC, but it eliminates most of the problems within the Windows system.
If the error persists after doing this, it suggests a more specific problem with your PC. It can be anything from an antivirus to a specific configuration that causes problems; the next step would be to get an opinion from a technician OR get information from the manufacturers of the software causing the problem. In either case, there will be a core problem that will cause the error to be displayed.