Printer GUID logged in Operational log


  • Client:

    Windows 7 SP1 x64


    Windows 2008 R2 SP1
    Latest UPD drivers from HP, Xerox, Ricoh, etc.


    In the Microsoft-Windows-PrintService/Operational log, the printer's GUID instead of name is getting logged for events during GPP actions.  By actions, I mean when the printer is recreated (since the GPP setting is REPLACE).  Happens for all vendors.

    Sample event (there are plenty more for other EventIDs too with ID 300, 304, 306, 302, 301)

    Log Name:      Microsoft-Windows-PrintService/Operational
    Source:        Microsoft-Windows-PrintService
    Date:          5/28/2013 4:45:23 PM
    Event ID:      300
    Task Category: Adding a printer
    Level:         Information
    Keywords:      Classic Spooler Event,Printer
    User:          SYSTEM
    Computer:      MYPC.MYDOMAIN
    Printer {01930C4C-5D21-4D1B-BC75-EC927AA8E293} was created. No user action is required.
    Event Xml:
    <Event xmlns="">
        <Provider Name="Microsoft-Windows-PrintService" Guid="{747EF6FD-E535-4D16-B510-42C90F6873A1}" />
        <TimeCreated SystemTime="2013-05-28T23:45:23.032258100Z" />
        <Correlation />
        <Execution ProcessID="1536" ThreadID="4372" />
        <Security UserID="S-1-5-18" />
        <PrinterCreated xmlns:auto-ns3="" xmlns="">

    Why isn't windows logging the real printer name? The GUID isn't useful at all.

    Wednesday, May 29, 2013 12:42 AM

All replies

  • Bump.
    Thursday, June 06, 2013 10:36 PM
  • I asked the Group Policy team about the Replace functionality of the feature.

    I do agree that the GUID printer label is not useful to print admins. 

    Alan Morris Windows Printing Team

    Friday, June 07, 2013 1:33 AM
  • Any feedback from the GPO team about this issue?
    Thursday, June 20, 2013 11:30 PM
  • Any feedback from the GPO team about this issue?
    Tuesday, August 06, 2013 4:42 PM
  • None from GPO group.

    If you have a list of the events that log the GUID printer name, that would be helpful in tracking down in the spooler when we can dig just a bit more for the printer name rather than just logging the GUID information

    Alan Morris Windows Printing Team

    Wednesday, August 07, 2013 12:33 AM
  • Microsoft-Windows-PrintService/Operational EventID: 

    • 219
    • 300
    • 301
    • 302
    • 304
    • 306
    • 842

    All have logged the GUID instead of queue name on the Win7 client.

    • Edited by BSOD2600 Wednesday, August 07, 2013 10:54 PM add more IDs
    Wednesday, August 07, 2013 12:39 AM
  • Any new information about this issue?
    We have sometimes problems with printing. It is not usefull for Printserver Admins.

    The GUID isn't useful for us. Can we have back the printer names for Windows 2008R2/Win 7 (like Windows 2003) ?

    Thursday, August 29, 2013 6:58 PM
  • Alan, any new information about this issue?
    Tuesday, November 19, 2013 6:41 PM
  •  Someone is taking a look to determine why we are dropping to the GUID name.


    Alan Morris Windows Printing Team

    Monday, November 25, 2013 9:40 PM
  • Checking in to see if the 'someone' has found a reason why this is occurring?
    Tuesday, December 24, 2013 8:00 PM
  • Not any traction on this yet.  If we get a resolution on the next version of Windows, then the support team would need a customer request to consider porting any changes to previous versions.

    Alan Morris Windows Printing Team

    Monday, December 30, 2013 4:48 AM
  • Bump. Any traction on this issue yet?
    Thursday, February 13, 2014 12:43 AM
  • Not much. Without more customers requesting this, the next OS release has a much higher priority.

    Alan Morris Windows Printing Team

    Thursday, February 13, 2014 1:01 AM
  • Heard back from a printer vendor, who opened a MS case log on on this issue on my behalf.  Just as you've stated Alan, MS has pegged the software change to the Windows Next software release, which is not in the near future. :(

    Really unfortunate MS will not fix an issue they created on Win7.

    Friday, April 25, 2014 6:21 PM
  • I guess you work a bunch with the X printer company.   The group I work for can only address versions of Windows that have not yet been released.  Released stuff goes to another team and they make the call. 

    That said, print vendors actually have a fairly loud voice in getting changes into the current releases.

    Alan Morris Windows Printing Team

    Friday, April 25, 2014 11:21 PM
  • The vendor also mentioned that MS has changed their KB process and has declined to write a KB article about this issue :-/

    Can you shed any more light on that aspect?

    Friday, April 25, 2014 11:38 PM
  • I'm normally not a part of the KB article process.  I don't know who writes these but the support group has requested reviews to a few recently but these also include a binary download.  Suggested changes have not always made it to the articles. 

    Alan Morris Windows Printing Team

    Saturday, April 26, 2014 12:14 AM