Symptoms

Consider the following scenario:

  • You have a client computer that is running Windows 7 or Windows Server 2008 R2.

  • You try to create a Point and Print connection to a remote printer from the client computer.

In this scenario, the operation fails and you receive the following error message:


=================
Title: Add Printer
Text: Connect to Printer
Windows cannot connect to printer.
Details: Operation failed with error 0x0000007e.
=================
Note: 0x0000007e/ERROR_MOD_NOT_FOUND: The specified module could not be found.



Therefore, the printer driver cannot be installed and you cannot share the printer with the client computer.

Cause

This issue occurs because, after the printer is installed, Windows 7 or Windows Server 2008 R2 incorrectly looks for the Mscms.dll file in a subfolder different than the windows\system32 subfolder.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. 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, visit the following Microsoft Web site:

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 be running Windows 7 or Windows Server 2008 R2 on the computer.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

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 notes


Important 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 MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. 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.7600.20707

768,000

05-May-2010

07:05

x86

Winprint.dll

6.1.7600.16385

29,696

14-Jul-2009

01:16

x86

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

File name

File version

File size

Date

Time

Platform

Localspl.dll

6.1.7600.20707

954,368

05-May-2010

07:21

x64

Winprint.dll

6.1.7600.16385

39,424

14-Jul-2009

01:41

x64

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.7600.20707

2,051,584

05-May-2010

05:49

IA-64

Winprint.dll

6.1.7600.16385

90,624

14-Jul-2009

01:50

IA-64

Status

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

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

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_1ed35da7eb57b41939c4d551f901f90a_31bf3856ad364e35_6.1.7600.20707_none_37e805b1b11de3bc.manifest

File version

File size

718

Date (UTC)

05-May-2010

Time (UTC)

10:46

Platform

Not Applicable

File name

X86_microsoft-windows-p..ooler-core-localspl_31bf3856ad364e35_6.1.7600.20707_none_30d3d6900cdc98b1.manifest

File version

File size

4,844

Date (UTC)

05-May-2010

Time (UTC)

11:43

Platform

Not Applicable

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

File name

Amd64_1ed35da7eb57b41939c4d551f901f90a_31bf3856ad364e35_6.1.7600.20707_none_9406a135697b54f2.manifest

File version

File size

720

Date (UTC)

05-May-2010

Time (UTC)

10:46

Platform

Not Applicable

File name

Amd64_a82d49de4a58d02f63929c78e95ed2ee_31bf3856ad364e35_6.1.7600.20707_none_a3c47bd6b960ba03.manifest

File version

File size

722

Date (UTC)

05-May-2010

Time (UTC)

10:46

Platform

Not Applicable

File name

Amd64_microsoft-windows-p..ooler-core-localspl_31bf3856ad364e35_6.1.7600.20707_none_8cf27213c53a09e7.manifest

File version

File size

4,845

Date (UTC)

05-May-2010

Time (UTC)

12:01

Platform

Not Applicable

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

File name

Ia64_73672fa56aea7a3054afaab3375ebd81_31bf3856ad364e35_6.1.7600.20707_none_d40885115ecd51cc.manifest

File version

File size

720

Date (UTC)

05-May-2010

Time (UTC)

10:46

Platform

Not Applicable

File name

Ia64_microsoft-windows-p..ooler-core-localspl_31bf3856ad364e35_6.1.7600.20707_none_30d57a860cdaa1ad.manifest

File version

File size

4,844

Date (UTC)

05-May-2010

Time (UTC)

10:46

Platform

Not Applicable

Need more help?

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

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×