Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. An update that improves the performance of the Printbrm.exe command-line tool in Windows 7 or in Windows Server 2008 R2 is available

An update that improves the performance of the Printbrm.exe command-line tool in Windows 7 or in Windows Server 2008 R2 is available

View products that this article applies to.

Symptoms

This article introduces an update that improves the performance of the Printbrm.exe command-line tool on a computer that is running Windows 7 or Windows Server 2008 R2. After you install the update, the following issues that you experience on the computer are resolved:

Issue 1
Consider the following scenario:
  • You connect a printer to a computer that is running Windows 7 or Windows Server 2008 R2.
  • You change some security settings of the printer on the computer.
  • You back up the printer settings by using the Printbrm.exe command-line tool.
  • You restore the printer settings on a second Windows 7-based or Windows Server 2008 R2-based computer by using the Printbrm.exe command-line tool. The security settings of the printer are restored correctly.
  • You back up the printer settings on the second computer by using the Printbrm.exe command-line tool.
  • You restore the printer settings on a third Windows 7-based or Windows Server 2008 R2-based computer by using the Printbrm.exe command-line tool.
In this scenario, the security settings of the printer on the third computer are restored incorrectly. Specifically, the printer is configured to default settings on the third computer.

Note To resolve this issue, install the update that is described in this article on the second and on the third computers.

Issue 2
Consider the following scenario:
  • You create several print queues on a computer that is running Windows 7 or Windows Server 2008 R2. For example, you create more than 500 print queues on the computer.
  • You use the Printbrm.exe command-line tool to back up the print queues on the computer.
  • You restore the backup by using the Printbrm.exe command-line tool.
In this scenario, the time that is required to restore the backup is longer than expected.

Issue 3
Assume that you use the Printbrm.exe command-line tool to back up or restore the printer settings on a computer that is running Windows 7 or Windows Server 2008 R2. During the restore or backup operation, a nonfatal error occurs, and the operation is aborted unexpectedly.

Notes
  • In this situation, the nonfatal error relates to the print forms, the language monitors, the plugins or the print processors.
  • After you install the update on the computer, the restore or backup operation continues even when a nonfatal error occurs. After the operation is completed, all the nonfatal error messages are logged in the Event Viewer as a collective list.
Issue 4
Assume that you use the Printbrm.exe command-line tool to back up a printer server on a computer that is running Windows 7 or Windows Server 2008 R2. The file size of the export file is larger than 2 gigabytes (GB). In this situation, the backup operation fails. Additionally, the following event is logged in the System log:Notes
  • The backup file is exported as a .cab file. The file size of a .cab file cannot exceed 2 GB by design.
  • After you install the update on the computer, the backup file is exported as an .opc file. The exported .opc file can be larger than 2 GB.
  • A backup file that is exported as an .opc file cannot be used by older versions of the Printbrm.exe command-line tool. After you install the update on the computer, the BrmDisableOpc registry entry is created to configure the file format of the exported backup file. You can set the DWORD value of the BrmDisableOpc registry entry to 1 to revert the file format of the exported backup file to the .cab file format. The registry entry is located under the following registry subkey:
    \HKLM\SYSTEM\CurrentControlSet\Control\Print

↑ Back to the top

Resolution

↑ Back to the top

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 website:
http://support.microsoft.com/contactus/?ws=support
Note 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 one of the following operating systems:
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, 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 global 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 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:
    VersionProductMilestoneService branch
    6.1.760
    0.16xxx    		Windows 7 and Windows Server 2008 R2RTMGDR
    6.1.760
    1.17xxx    		Windows 7 and Windows Server 2008 R2SP1GDR
    6.1.760
    1.22xxx    		Windows 7 and Windows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical 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 for Windows Server 2008 R2" 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 nameFile versionFile sizeDateTimePlatformService branch
Localspl.dll6.1.7601.22104775,16831-Aug-201216:46x86X86_MICROSOFT-WINDOWS-P..OOLER-CORE-LOCALSP
Winprint.dll6.1.7601.1751430,20820-Nov-201012:21x86X86_MICROSOFT-WINDOWS-P..OOLER-CORE-LOCALSP
Printbrm.exe6.1.7601.2210420,99231-Aug-201215:56x86Not applicable
Printbrmengine.exe6.1.7601.22104243,20031-Aug-201215:56x86Not applicable
Printbrmps.dll6.1.7600.1638513,31214-Jul-200901:16x86Not applicable
Printbrmui.exe1.0.0.066,04831-Aug-201215:56x86Not applicable
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatformService branch
Localspl.dll6.1.7601.22104965,12031-Aug-201217:42x64AMD64_MICROSOFT-WINDOWS-P..OOLER-CORE-LOCALSP
Winprint.dll6.1.7601.1751439,42420-Nov-201013:27x64AMD64_MICROSOFT-WINDOWS-P..OOLER-CORE-LOCALSP
Printbrm.exe6.1.7601.2210421,50431-Aug-201216:47x64Not applicable
Printbrmengine.exe6.1.7601.22104295,93631-Aug-201216:48x64Not applicable
Printbrmps.dll6.1.7600.1638519,45614-Jul-200901:41x64Not applicable
Printbrmui.exe1.0.0.071,68031-Aug-201216:48x64Not applicable
Localspl.dll6.1.7601.22104775,16831-Aug-201216:46x86X86_MICROSOFT-WINDOWS-P..OOLER-CORE-LOCALSP
Winprint.dll6.1.7601.1751430,20820-Nov-201012:21x86X86_MICROSOFT-WINDOWS-P..OOLER-CORE-LOCALSP

↑ Back to the top

Status

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

↑ Back to the top

More Information

For more information about print services migration, go to the following Microsoft website:
General information about the print services migration
For more information about the Printbrm.exe command-line tool, go to the following Microsoft website:
General information about the Printbrm.exe command-line tool
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 nameX86_008819fbdc5b938b96213bf908abcba8_31bf3856ad364e35_6.1.7601.22104_none_98f4853e62544f6c.manifest
File versionNot applicable
File size711
Date (UTC)04-Sep-2012
Time (UTC)06:00
PlatformNot applicable
File nameX86_149dfa02b693dea7c713089816b77efb_31bf3856ad364e35_6.1.7601.22104_none_f4778213711827ee.manifest
File versionNot applicable
File size712
Date (UTC)04-Sep-2012
Time (UTC)06:00
PlatformNot applicable
File nameX86_8484612beaccdf018693ffc91b209ae4_31bf3856ad364e35_6.1.7601.22104_none_b5f0f6f365fd4145.manifest
File versionNot applicable
File size718
Date (UTC)04-Sep-2012
Time (UTC)06:00
PlatformNot applicable
File nameX86_microsoft-windows-d..le-opc-for-printbrm_31bf3856ad364e35_6.1.7601.22104_none_f98bb72a13f1073a.manifest
File versionNot applicable
File size1,085
Date (UTC)31-Aug-2012
Time (UTC)17:15
PlatformNot applicable
File nameX86_microsoft-windows-p..ooler-core-localspl_31bf3856ad364e35_6.1.7601.22104_none_32b714580a05dd9d.manifest
File versionNot applicable
File size4,844
Date (UTC)04-Sep-2012
Time (UTC)06:04
PlatformNot applicable
File nameX86_microsoft-windows-p..ting-tools-printbrm_31bf3856ad364e35_6.1.7601.22104_none_8455ded0bcac588c.manifest
File versionNot applicable
File size76,920
Date (UTC)04-Sep-2012
Time (UTC)06:04
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_5b20b9fdaad15af1f588d92b32b4ff9b_31bf3856ad364e35_6.1.7601.22104_none_319fb0fd368d871d.manifest
File versionNot applicable
File size716
Date (UTC)04-Sep-2012
Time (UTC)06:00
PlatformNot applicable
File nameAmd64_8484612beaccdf018693ffc91b209ae4_31bf3856ad364e35_6.1.7601.22104_none_120f92771e5ab27b.manifest
File versionNot applicable
File size720
Date (UTC)04-Sep-2012
Time (UTC)06:00
PlatformNot applicable
File nameAmd64_add98f1aa8750458e6cace3a9be3aac5_31bf3856ad364e35_6.1.7601.22104_none_03cc02372d68a4bf.manifest
File versionNot applicable
File size722
Date (UTC)04-Sep-2012
Time (UTC)06:00
PlatformNot applicable
File nameAmd64_b8ebea2f37cb7858804e8142133de4b6_31bf3856ad364e35_6.1.7601.22104_none_d03d686a1fb358d7.manifest
File versionNot applicable
File size715
Date (UTC)04-Sep-2012
Time (UTC)06:00
PlatformNot applicable
File nameAmd64_microsoft-windows-d..le-opc-for-printbrm_31bf3856ad364e35_6.1.7601.22104_none_55aa52adcc4e7870.manifest
File versionNot applicable
File size1,087
Date (UTC)31-Aug-2012
Time (UTC)18:12
PlatformNot applicable
File nameAmd64_microsoft-windows-p..ooler-core-localspl_31bf3856ad364e35_6.1.7601.22104_none_8ed5afdbc2634ed3.manifest
File versionNot applicable
File size4,845
Date (UTC)04-Sep-2012
Time (UTC)06:00
PlatformNot applicable
File nameAmd64_microsoft-windows-p..ting-tools-printbrm_31bf3856ad364e35_6.1.7601.22104_none_e0747a547509c9c2.manifest
File versionNot applicable
File size76,924
Date (UTC)04-Sep-2012
Time (UTC)06:00
PlatformNot applicable
File nameX86_microsoft-windows-p..ooler-core-localspl_31bf3856ad364e35_6.1.7601.22104_none_32b714580a05dd9d.manifest
File versionNot applicable
File size4,844
Date (UTC)04-Sep-2012
Time (UTC)06:00
PlatformNot applicable

↑ Back to the top

Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced, kb

↑ Back to the top

Article Info
Article ID : 2752259
Revision : 1
Created on : 1/7/2017
Published on : 10/11/2012
Exists online : False
Views : 253