Print jobs fail in Windows 7 and Windows Server 2008 R2

Work anywhere from any device with Microsoft 365

Upgrade to Microsoft 365 to work anywhere with the latest features and updates.

Upgrade now

Symptoms

When you try to print on a system that's running Windows 7 or Windows Server 2008 R2, the print job fails.

Cause

This problem occurs when the DependentFiles registry key for the driver that's used by the printer is overwritten by a NULL string.

The DependentFiles registry key is located under the following subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\<architecture>\Drivers\Version-3\<driver_name>Note The <driver_name> placeholder represents the name of the driver in question.

Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Service Pack 1 for Windows 7 or Windows Server 2008 R2 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information and notesImportant Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    Version

    Product

    SR_Level

    Service branch

    6.1.760
    1.
    17xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    GDR

    6.1.760
    1.
    22xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    LDR

  • GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7 and Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows 7

File name

File version

File size

Date

Time

Platform

Localspl.dll

6.1.7601.22816

777,216

22-Sep-2014

01:41

x86

Winprint.dll

6.1.7601.17514

30,208

20-Nov-2010

12:21

x86

For all supported x64-based versions of Windows 7 and Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Localspl.dll

6.1.7601.22816

967,168

22-Sep-2014

02:05

x64

Winprint.dll

6.1.7601.17514

39,424

20-Nov-2010

13:27

x64

Localspl.dll

6.1.7601.22816

777,216

22-Sep-2014

01:41

x86

Winprint.dll

6.1.7601.17514

30,208

20-Nov-2010

12:21

x86

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Localspl.dll

6.1.7601.22816

2,081,280

22-Sep-2014

01:24

IA-64

Winprint.dll

6.1.7601.17514

90,624

20-Nov-2010

10:28

IA-64

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

File name

X86_728d524815737c24fcc21f0e88806092_31bf3856ad364e35_6.1.7601.22816_none_f4f0564e77ae045e.manifest

File version

Not Applicable

File size

718

Date (UTC)

22-Sep-2014

Time (UTC)

18:42

SHA-1 hash

Not Applicable

MD5 hash

Not Applicable

File name

X86_microsoft-windows-p..ooler-core-localspl_31bf3856ad364e35_6.1.7601.22816_none_32ae524a0a0c184d.manifest

File version

Not Applicable

File size

4,844

Date (UTC)

22-Sep-2014

Time (UTC)

18:55

SHA-1 hash

Not Applicable

MD5 hash

Not Applicable

Additional files for all supported x64-based versions of Windows 7 and Windows Server 2008 R2

File name

Amd64_728d524815737c24fcc21f0e88806092_31bf3856ad364e35_6.1.7601.22816_none_510ef1d2300b7594.manifest

File version

Not Applicable

File size

720

Date (UTC)

22-Sep-2014

Time (UTC)

18:42

SHA-1 hash

Not Applicable

MD5 hash

Not Applicable

File name

Amd64_fdbd0839a6782b689f5c4e3919eecfb0_31bf3856ad364e35_6.1.7601.22816_none_b16a6d6fddf8423a.manifest

File version

Not Applicable

File size

722

Date (UTC)

22-Sep-2014

Time (UTC)

18:42

SHA-1 hash

Not Applicable

MD5 hash

Not Applicable

File name

Amd64_microsoft-windows-p..ooler-core-localspl_31bf3856ad364e35_6.1.7601.22816_none_8eccedcdc2698983.manifest

File version

Not Applicable

File size

4,845

Date (UTC)

22-Sep-2014

Time (UTC)

19:00

SHA-1 hash

Not Applicable

MD5 hash

Not Applicable

File name

X86_microsoft-windows-p..ooler-core-localspl_31bf3856ad364e35_6.1.7601.22816_none_32ae524a0a0c184d.manifest

File version

Not Applicable

File size

4,844

Date (UTC)

22-Sep-2014

Time (UTC)

19:00

SHA-1 hash

Not Applicable

MD5 hash

Not Applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name

Ia64_abd3baa441627b745808780776ce9249_31bf3856ad364e35_6.1.7601.22816_none_423010333a6e86fc.manifest

File version

Not Applicable

File size

720

Date (UTC)

22-Sep-2014

Time (UTC)

18:42

SHA-1 hash

Not Applicable

MD5 hash

Not Applicable

File name

Ia64_microsoft-windows-p..ooler-core-localspl_31bf3856ad364e35_6.1.7601.22816_none_32aff6400a0a2149.manifest

File version

Not Applicable

File size

4,844

Date (UTC)

22-Sep-2014

Time (UTC)

18:42

SHA-1 hash

Not Applicable

MD5 hash

Not Applicable


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×