locked
W2k8 just will NOT install print drivers RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have tried everything I can think of with assistance from one of our enterprise printing SMEs (Fortune 50 company), and am unable to get print drivers installed on a Windows 2008 R2 VM. The error I continue to see is this:

    "Add Printer Driver Wizard" --> "Unable to install <driver name>, Type 3 - User Mode, x64 driver. Operation could not be completed (error 0x000005b3)."
    The above dialog is followed by another: "Print Management" --> "Failed to add driver. Operation could not be completed (error 0x00000578)."

    The type of driver / printer doesn't matter. This dialog prompts on just about every printer type I try.

    My fresh windows/inf/setupapi.app.log...

    [Device Install Log]
     OS Version = 6.1.7601
     Service Pack = 1.0
     Suite = 0x0012
     ProductType = 3
     Architecture = amd64
[BeginLog]
[Boot Session: 2012/06/18 11:48:54.037]
>>>  [Import Driver Package - c:\printdrivers\lmud0540.inf_amd64_neutral_e6daa7923257a525\lmud0540.inf]
>>>  Section start 2012/06/18 12:19:44.436
      cmd: "C:\Windows\system32\mmc.exe" "C:\Windows\system32\printmanagement.msc" 
     sto: Importing driver package into Driver Store:
     sto:      Driver Store   = C:\Windows\System32\DriverStore (Online | 6.1.7601)
     sto:      Driver Package = c:\printdrivers\lmud0540.inf_amd64_neutral_e6daa7923257a525\lmud0540.inf
     sto:      Architecture   = amd64
     sto:      Locale Name    = neutral
     sto:      Flags          = 0x00000000
!    sto: Driver package 'lmud0540.inf' already exists in Driver Store:
!    sto:      Filename = C:\Windows\System32\DriverStore\FileRepository\lmud0540.inf_amd64_neutral_e6daa7923257a525\lmud0540.inf (oem43.inf)
     sto: Imported driver package into Driver Store:
     sto:      Filename = C:\Windows\System32\DriverStore\FileRepository\lmud0540.inf_amd64_neutral_e6daa7923257a525\lmud0540.inf
     sto:      Time     = 156 ms
<<<  Section end 2012/06/18 12:19:44.618
<<<  [Exit status: SUCCESS]

    Last 30 lines or so of my windows/inf/setupapi.dev.log...

         flq: CopyFile: 'C:\Windows\System32\DriverStore\FileRepository\lmud0540.inf_amd64_neutral_e6daa7923257a525\x64\LMUD054Z.DLL'
     flq:       to: 'C:\Windows\system32\spool\DRIVERS\x64\{5E5F26E4-7B08-4D9F-ADAF-5AC8E5689668}\SET565C.tmp'
     flq: MoveFile: 'C:\Windows\system32\spool\DRIVERS\x64\{5E5F26E4-7B08-4D9F-ADAF-5AC8E5689668}\SET565C.tmp'
     flq:       to: 'C:\Windows\system32\spool\DRIVERS\x64\{5E5F26E4-7B08-4D9F-ADAF-5AC8E5689668}\LMUD054Z.DLL'
     flq: CopyFile: 'C:\Windows\System32\DriverStore\FileRepository\lmud0540.inf_amd64_neutral_e6daa7923257a525\LMUD0540.INI'
     flq:       to: 'C:\Windows\system32\spool\DRIVERS\x64\{5E5F26E4-7B08-4D9F-ADAF-5AC8E5689668}\SET5738.tmp'
     flq: MoveFile: 'C:\Windows\system32\spool\DRIVERS\x64\{5E5F26E4-7B08-4D9F-ADAF-5AC8E5689668}\SET5738.tmp'
     flq:       to: 'C:\Windows\system32\spool\DRIVERS\x64\{5E5F26E4-7B08-4D9F-ADAF-5AC8E5689668}\LMUD0540.INI'
     flq: CopyFile: 'C:\Windows\System32\DriverStore\FileRepository\lmud0540.inf_amd64_neutral_e6daa7923257a525\english\x64\LMUD054C.DLL'
     flq:       to: 'C:\Windows\system32\spool\PRTPROCS\x64\1\SET5823.tmp'
     flq: MoveFile: 'C:\Windows\system32\spool\PRTPROCS\x64\1\SET5823.tmp'
     flq:       to: 'C:\Windows\system32\spool\PRTPROCS\x64\1\LMUD054C.DLL'
     flq: CopyFile: 'C:\Windows\System32\DriverStore\FileRepository\lmud0540.inf_amd64_neutral_e6daa7923257a525\x64\softcoin.dll'
     flq:       to: 'C:\Windows\system32\SET59AB.tmp'
     flq: MoveFile: 'C:\Windows\system32\SET59AB.tmp'
     flq:       to: 'C:\Windows\system32\softcoin.dll'
!!!  flq: MoveFile: FAILED!
!!!  flq: Error 32: The process cannot access the file because it is being used by another process.
!!!  flq: Windows could not copy a boot file 'C:\Windows\system32\softcoin.dll' due to the presence of an in-use file.
!!!  flq: Error installing file (0x00000005)
!!!  flq: Error 5: Access is denied.
!    flq: SourceFile   - 'C:\Windows\System32\DriverStore\FileRepository\lmud0540.inf_amd64_neutral_e6daa7923257a525\x64\softcoin.dll'
!    flq: TargetFile   - 'C:\Windows\system32\softcoin.dll'
!!!  flq: SPFQNOTIFY_COPYERROR: returned SPFQOPERATION_ABORT.
!!!  flq: Error 1459: This operation requires an interactive window station.
!!!  flq: FileQueueCommit aborting!
!!!  flq: Error 1459: This operation requires an interactive window station.
>>>  [DIF_DESTROYPRIVATEDATA]
>>>  Section start 2012/06/18 12:19:54.465
      cmd: "C:\Windows\system32\mmc.exe" "C:\Windows\system32\printmanagement.msc" 
<<<  Section end 2012/06/18 12:19:54.467
<<<  [Exit status: SUCCESS (DI_DO_DEFAULT)]

    I'm totally and completely stuck. Been working at this for over a week trying a combination of driver installation methods, in-box drivers, mfg drivers, printers, self-extracting installation executables. Nothing works.

    Desperate for an answer here. High profile project and mgrs with little patience.

    Monday, June 18, 2012 7:36 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    This particular error C:\>winerror 0x000005b3
      1459 ERROR_REQUIRES_INTERACTIVE_WINDOWSTATION <--> No NTSTATUS matched

    Occurs when the driver is requesting some sort of response in session zero.  Any drivers that performed this function were blocked from inclusion in 2008 R2.

    Since the event specifically states that the operation requires the interactive windows station, I will assume that you have already enabled this.  Is there an actionable UI?

    If you have yet to enable the feature, start there.  I looked for a link with instructions but found none in a quick search so here a quick lesson.

    services.msc

    Interactive Services Detection

    I normally enable startup type to Automatic since Lexmark and HP both throw session zero UI.  Start at Manual and start the service, then install the driver and see what pops up in session zero.

    Once again, you will not see this a prompt when installing a printer that uses one of the drivers included with Windows.

    Alan Morris Windows Printing Team

    Monday, June 18, 2012 8:18 PM
    Answerer
  • Question
    Sign in to vote
    0
    Sign in to vote

    As promised, I'm posting my results to this issue.

    While I *still* don't know the cause of my driver installation issues, I walked through the steps on each of the solutions here (apparently cut-n-paste from other threads where this seems to be a common problem). At the end of the day, for my particular environment, the solution to the problem appeared to be permissions and NOT (NOT!!!) an in-use file (or 10).

    In C:\windows\inf\setupapi.app.log you'll see 2 lines that reference a source and destination file copy operation (scroll to the bottom). A few lines above that it provides an error message that leads you down the wrong path for troubleshooting (in use file). By simply copying the source file to the destination directory, attempting driver installation again, rinse, repeat, you can get your drivers installed. Not sure why the account used for driver installation was not able to move files from one location to another, but it kept failing. Using a domain account (member of local admins), I was able to copy the file.

    The really crappy part about this is that we have [what should be] identical W2k8 servers being stagged in another department with the same restrictions, yet those server have zero issues installing drivers. The only logical difference between the two is group policy which are, again, very similiar, but not totally identical. Should problems like this surface again, I'll be focusing on GPOs instead of the boxes themselves.

    EDIT: wanted to also state that I was able to perform the driver installation along with manually copying source files to destination as noted above via RDP. I did not need the "interactive services detection" service running and didn't need to be logged on to the console.

    Friday, July 13, 2012 5:05 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    This particular error C:\>winerror 0x000005b3
      1459 ERROR_REQUIRES_INTERACTIVE_WINDOWSTATION <--> No NTSTATUS matched

    Occurs when the driver is requesting some sort of response in session zero.  Any drivers that performed this function were blocked from inclusion in 2008 R2.

    Since the event specifically states that the operation requires the interactive windows station, I will assume that you have already enabled this.  Is there an actionable UI?

    If you have yet to enable the feature, start there.  I looked for a link with instructions but found none in a quick search so here a quick lesson.

    services.msc

    Interactive Services Detection

    I normally enable startup type to Automatic since Lexmark and HP both throw session zero UI.  Start at Manual and start the service, then install the driver and see what pops up in session zero.

    Once again, you will not see this a prompt when installing a printer that uses one of the drivers included with Windows.

    Alan Morris Windows Printing Team

    Monday, June 18, 2012 8:18 PM
    Answerer
  • Question
    Sign in to vote
    2
    Sign in to vote

    Did you notice in setupapi.app.log, Windows thinks 'lmud0540.inf' already exists in Driver Store?  I ran into almost this exact problem (HRESULT 0x80070057) with multiple vendors.  The solution for me was:

    1. Interesting that it still thinks the driver exists when that FileRepository path does NOT exist.  After reading Remove a Driver Package from the Driver Store, I used: pnputil -e and sure enough, oem52.inf was present.  I then used: pnputil -d oem52.inf to delete the inf from the driver store.
    2. Finally, installing the driver from Print Management worked!

    You might try the same but substitue lmud0540.inf for oem52.inf.

    Monday, June 18, 2012 10:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Alan, thanks so much, man. No, I wasn't aware of the "interactive Services Detection". Lot's of functionality mapping between 2003 <-> 2008 and other changes I haven't been confronted with yet.

    Enabling that service did allow me to install the one other Lexmark driver I needed to get on there. Still having issues with the HP Universal, but I'm going to walk through the post from BSOD2600 to see if that will work.

    I'll post back here with results. Thanks guys.

    (edit: reposted this under BSOD2600's post)

    Tuesday, June 19, 2012 5:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    As promised, I'm posting my results to this issue.

    While I *still* don't know the cause of my driver installation issues, I walked through the steps on each of the solutions here (apparently cut-n-paste from other threads where this seems to be a common problem). At the end of the day, for my particular environment, the solution to the problem appeared to be permissions and NOT (NOT!!!) an in-use file (or 10).

    In C:\windows\inf\setupapi.app.log you'll see 2 lines that reference a source and destination file copy operation (scroll to the bottom). A few lines above that it provides an error message that leads you down the wrong path for troubleshooting (in use file). By simply copying the source file to the destination directory, attempting driver installation again, rinse, repeat, you can get your drivers installed. Not sure why the account used for driver installation was not able to move files from one location to another, but it kept failing. Using a domain account (member of local admins), I was able to copy the file.

    The really crappy part about this is that we have [what should be] identical W2k8 servers being stagged in another department with the same restrictions, yet those server have zero issues installing drivers. The only logical difference between the two is group policy which are, again, very similiar, but not totally identical. Should problems like this surface again, I'll be focusing on GPOs instead of the boxes themselves.

    EDIT: wanted to also state that I was able to perform the driver installation along with manually copying source files to destination as noted above via RDP. I did not need the "interactive services detection" service running and didn't need to be logged on to the console.

    Friday, July 13, 2012 5:05 PM