Inbox means the drivers shipped with the Operating System. What printer do
you have?
--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
This posting is provided "AS IS" with no warranties, and confers no rights.
"powerray" <powerray@discussions.microsoft.com> wrote in message
news:9DC70EB9-6CE4-4892-BE32-EC14D2FA6B58@microsoft.com...
> Alan I don't know what your talking about inbox drivers. Apollo is the
> first
> mfg on the list. Do you understand that as far as my computer is
> concerned I
> do not even have a printer connected? It sees nothing. I believe it may
> be
> a part of another problem in that I cannot load soft ware, I cannot update
> Windows Defender. Most everything I try to do is rejected. I brought
> that
> probem out on another thread but I must be stumping folks 'cause that
> thread
> just died. I'm gonna go over there and ratttle some cage.
>
> "Alan Morris [MSFT]" wrote:
>
>> Thanks for the detailed information Tom.
>>
>> PowerRay, what inbox driver are you attempting to install? None of the
>> inbox should require this?
>>
>> I am attempting to determine if you hit a setup bug where the vendor
>> install
>> deletes a file on your system and the system PnP setup stuff fails to
>> regenerate this file properly. If the first manufacture in the list is
>> NOT
>> Apollo, you have hit this issue and any PnP installs will fail for all
>> USB
>> hardware that use inbox drivers.
>>
>> --
>> Alan Morris
>> Windows Printing Team
>> Search the Microsoft Knowledge Base here:
>> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Tom Ferguson" <tom.msmvp@gmail.com> wrote in message
>> news:%23HkAZDs1HHA.1184@TK2MSFTNGP04.phx.gbl...
>> > This would seem to be a problem with the printer co-installer.
>> > http://search.msdn.microsoft.com/sea...=00&lang=en-us
>> >
>> > If so, the solution lies outside your hands.
>> > -----------------
>> > 000005B3: ERROR_REQUIRES_INTERACTIVE_WINDOWSTATION
>> > Issue:
>> > The driver installation requires an interactive window due to issues
>> > such
>> > as the co installer about to show some user interfaces like a dialog
>> > box.
>> > This failure generates the following entries in the Setupapi.dev.log
>> > file.
>> > dvi: {DIF_INSTALLDEVICE} 11:02:29.804
>> > dvi: CoInstaller 1: Enter 11:02:29.804
>> > !!! dvi: CoInstaller 1: failed(0x000005b3)!
>> > !!! dvi: Error 1459: This operation requires an interactive
>> > window station.
>> > dvi: {DIF_INSTALLDEVICE - exit(0x000005b3)} 11:02:29.804
>> > dvi: {DIF_DESTROYPRIVATEDATA} 11:02:29.820
>> > dvi: CoInstaller 1: Enter 11:02:29.820
>> > dvi: CoInstaller 1: Exit
>> > dvi: Class installer: Enter 11:02:29.835
>> > dvi: Class installer: Exit
>> > dvi: Default installer: Enter 11:02:29.835
>> > dvi: Default installer: Exit
>> > dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 11:02:29.835
>> > ump: Server install process exited with code 0x000005b3
>> > 11:02:29.835
>> > ump: {Plug and Play Service: Device Install exit(000005b3)}
>> >
>> >
>> > Solution:
>> > Solve the root cause problem that requires an interactive window
>> > station.
>> > (The problem might be an I/O problem, a File Access denied problem, and
>> > so
>> > on.) Co installers cannot require an interactive window station
>> > outside a
>> > finish-install action or finish-install page. Ensure that the co
>> > installer
>> > uses a finish-install action or a finish-install page to show UI.
>> > For diagnosing the co install error details, see Debugging Device
>> > Installation in Windows Vista, available online at:
>> > http://www.microsoft.com/whdc/driver.../diagnose.mspx
>> > For implementation details, see Device Finish-Install Actions in
>> > Windows
>> > Vista, available online at:
>> > http://www.microsoft.com/whdc/driver...h_Install.mspx
>> >
>> > --------------
>> > Perhaps Alan has a suggestion for a work-around.
>> >
>> > Tom
>> > MSMVP
>> > Windows Shell/User
>> >
>> >
>> > "powerray" <powerray@discussions.microsoft.com> wrote in message
>> > news:54629515-5DB3-41E0-9C6F-9E91960825C0@microsoft.com...
>> >> Yes. I tried to install the driver with 'File' as the connection point
>> >> and
>> >> got 'Printer driver was not installed. Operation could not be
>> >> completed
>> >> (error 0x000005b3).'
>> >>
>> >> "Tom Ferguson" wrote:
>> >>
>> >>> OK but elect to install a local printer anyway. Select 'File' as the
>> >>> connection. Is the printer listed?
>> >>>
>> >>> Tom
>> >>> MSMVP
>> >>> Windows shell/User
>> >>>
>> >>>
>> >>> "powerray" <powerray@discussions.microsoft.com> wrote in message
>> >>> news:B740745A-3C8F-4B25-9309-DE438BB12CDA@microsoft.com...
>> >>> > OK.
>> >>> > When I click 'Add Printer" I get 2 options. 1. "Add a local
>> >>> > printer.
>> >>> > Use
>> >>> > this option only if you don't have a USB printer. Windows
>> >>> > automatically
>> >>> > installs USB printers when you plug them in." (Guess what? It
>> >>> > didn't)
>> >>> > And
>> >>> > 2. Add a network, wireless or Bluetooth printer. (I'm not)
>> >>> > "Alan Morris [MSFT]" wrote:
>> >>> >
>> >>> >> When you run Add Printer manually are all the manufactures and
>> >>> >> models
>> >>> >> listed?
>> >>> >>
>> >>> >> --
>> >>> >> Alan Morris
>> >>> >> Windows Printing Team
>> >>> >> Search the Microsoft Knowledge Base here:
>> >>> >> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
>> >>> >>
>> >>> >> This posting is provided "AS IS" with no warranties, and confers
>> >>> >> no
>> >>> >> rights.
>> >>> >>
>> >>> >> "powerray" <powerray@discussions.microsoft.com> wrote in message
>> >>> >> news:1D69ED7A-2151-4660-B6B3-579629C933EC@microsoft.com...
>> >>> >> >I connected my computer (Vista) to my printer. Was asked for
>> >>> >> >permission
>> >>> >> > which is another problem. Was not given permission even though
>> >>> >> > I'm
>> >>> >> > the
>> >>> >> > user
>> >>> >> > (like I said another problem). Was directed to go to the mfg
>> >>> >> > site
>> >>> >> > (HP).
>> >>> >> > HP
>> >>> >> > says windows has the driver. Now windows does not even
>> >>> >> > recognize
>> >>> >> > that
>> >>> >> > there's a printer plugged unto the USB port.
>> >>> >>
>> >>> >>
>> >>> >>
>> >>>
>>
>>
>>