Microsoft's Windows PrintNightmare Patch Breaks Network Printing Functionality

[Steevo]

2006 print issues were known. Shame on hackers for taking so long to utilize it and make it more mainstream.

 

[lexluthermiester]

2006 print issues were known. Shame on hackers for taking so long to utilize it and make it more mainstream.

Funny that, right?

 

[TheUn4seen]

Microsoft seems to have a hate-hate relationship with printers. Even Futurama writers noticed it years ago, a scary story told by B. B. Rodriguez went something like:
-And then she saw... a WINDOWS LOGO!
-That's not scary.
-It is if you're a laser printer.

 

[trparky]

for all who wonder how to reproduce the "Nightmare" well its rather easy as any user whose machine has this patch installed cannot install any network shared printer USB or non USB just shared from any server or machine requiring the installation of drivers from remote location when the user initiating the installation of the printer doesn't have elevated/admin rights will get 0x0000011b printer not accessible during driver installation. users with printers already installed or not requiring driver installation wont be affected.

Maybe that's a good thing. Non-admins shouldn't be able to install devices, only admins should have this ability. From a security standpoint, this is a good thing.

 

[windwhirl]

Maybe that's a good thing. Non-admins shouldn't be able to install devices, only admins should have this ability. From a security standpoint, this is a good thing.

To be honest, while I agree with that idea, I can't help but wonder why a printer of all things requires admin level access to be installed. Like, what specific components of a printer driver need so much privilege.

 

[trparky]

To be honest, while I agree with that idea, I can't help but wonder why a printer of all things requires admin level access to be installed. Like, what specific components of a printer driver need so much privilege.

*looks over at my multifunction HP printer*

You wouldn't believe the amount of stuff that is installed for an HP printer. We're talking the printer driver itself, the driver to handle faxes (yes, that still exists), software to handle incoming scans from the printer, software to initiate a remote scan, OCR software, etc. The whole installation package is about 250 MBs in size.

 

[loo]

I have a work-around that is supposed to work, though it has yet to be verified.

Go into Network adapter properties and disable "Client for Microsoft Networks" and "File & Printer Sharing for Microsoft Networks". Then open the Management Console and change the Print Spooler service Startup Type to Manual. This should solve the problem for most end users until a proper fix can be issued as these step kill remote printing of any kind. This of course solves nothing for networks...

my boss got 3 pc shared 2 different USB ,
i already do disable the print spooler service, also done disable client ....networks n file.... sharing ,also cannot work.
nothing different. still 0x0000011b n 0x00000bcb ?
it's possible to use printing over RDP? safe? or other solution?
Any someone help ? Please! S.O.S . Tq

 

[lexluthermiester]

my boss got 3 pc shared 2 different USB ,
i already do disable the print spooler service, also done disable client ....networks n file.... sharing ,also cannot work.
nothing different. still 0x0000011b n 0x00000bcb ?
it's possible to use printing over RDP? safe? or other solution?
Any someone help ? Please! S.O.S . Tq

Unfortunately, that is a problem that needs an on-site tech. There's just no feasible way to solve a problem that complex over the net.