This article was previously published under Q293889
This article has been archived. It is offered "as is" and will no longer be updated.
If you run System Restore to return to a checkpoint that you created before you installed your current, problematic printer driver, which has some files in common with a previously-installed printer driver, System Restore does not automatically roll back the driver to the previously installed driver.
This problem occurs because the architecture for printer drivers does not define exclusive file extensions that are used when you create printer drivers. Therefore, it is impossible to define a list of file extensions that exclusively represents printer drivers.
If you perform a search for Microsoft-provided printer driver file extensions, the results yield:
additional files with no extensions
This list is not exhaustive. There are additional extensions that are in use by driver manufacturers, most of which represent binary information that the printer driver needs. Unfortunately, some of these extensions are also in use as data files, and there is no exclusive way to decipher them from those files.
To resolve this problem, open the printer properties, on the Advanced tab click the last driver that you installed from the Driver list, and then click OK to apply.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
You have a working printer driver installed.
You use System Restore to create a checkpoint to preserve the current configuration.
You upgrade the driver or install a new driver with files that are in common with the currently installed driver.
After the installation, you cannot print because one of the printer driver files has a problem or is otherwise incompatible with the other drivers that are installed on the computer.
You restore the computer to the checkpoint that you created before using System Restore.
The printer still does not work.
For troubleshooting steps and an automatic fix for common printer problems in Windows, please see the following Microsoft web page: