Error 0x0000bcb attempting to share Samsung printer

Hi,

Thank you for posting your query in Microsoft Community. I understand the inconvenience caused to you and will assist you in solving the issue.

I suggest you to follow the steps provided below:

1.  Go into the print management (Administrative tools in control panel)
2.  Go to “Print servers”
3.  Go to your pc listed as “computer name (local)"
4.  Right click the driver name you are having issues with and select “Remove driver package”
5.  Reinstall the printer you are trying to install

Also, refer the link below and check if it helps.

http://www.samsungsetup.com/TS/Client/en/Install.html

Hope the information is helpful. Keep us posted on the status for further assistance.

 

 Thank you for the reply.  When I tell it to remove the driver for the Samsung ML-191x 252x Series, I get the message:

"The following driver(s) cannot be deleted:

Driver Samsung ML-191 252x Series (x64) is in use.  It is used on:

Samsung ML-191 252x Series "

 New info.  As I mentioned before, I have two copies of Win 10 Pro on this desktop, one installs the printer, the other doesn't.  The one that doesn't is at 10586 build, the one that does is at 10240. 

  Now that sure is strong evidence we're dealing with a bug in the 10586 build, don't you think?.  I just tried it with the 11082 build and got the same error.  :-(

M a j o r    n e w    f i n d i n g

The problem appears to occur when Windows 10 is on an SSD!

I have 2 test desktops.  Each has 2 copies of Win 10 installed.

One system is on a HDD. the other on an SSD.

On both desktops the system on the HDD has no problems.

On both desktops the system on the SSD does have the problem.

 So, as is often the case with networking problems, we have a timing problem it appears.  FWIW my suspicion is that there's some kind of time dependent code when installing a shared printer where things happen too quickly when Windows 10 is on an SSD, and Windows 10 incorrectly thinks there's been a timeout.  That's just my theory, so feel free to disagree if you do.  However I do believe the problem occurs only when Windows 10 is on an SSD. 

 As I mentioned earlier, I've had this problem for about 6 months, so it would sure be nice if MS would fix it.  See my July post here:

http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_devices/cant-access-networked-printer-samsung-ml-2525/b0bb0cca-b674-44f0-a98d-d8b0c6ea3cdd?auth=1

 I was tempted to title this finding eureka, but I'll wait and reserve that for when the problem gets fixed.  :-)

Installing a printer as "shared" is for USB cable only connection, or the old cable that connected to the parallel port on a computer. You install it connected by USB or the parallel port to the first computer, set it as "shared" and then, with that computer left on and connected to the printer, install the printer on the second computer as "shared", and it prints through the first computer (which must be running). You don't want that kind of a mess unless you are stuck with a printer that can only connect via a USB cable or to a parallel port.

You didn't mention the model of your Canon, but your Samsung is a network printer (if I remember correctly), so you connect it to your network cable, and install as "local printer", and set its port to its IP address on your network. You then install it on each of your computers as "local printer", using the same IP address. Every computer that it's installed on sees it as "local", not via another computer. 

All printers on your wired network that you have installed the printer on will print directly to the printer without regard to whether or not any other computer is running. 

Then, if you have a wireless network, and it is tied to your wired network through your router, you can also install the printer on every computer that you allow access to your wireless network, porting the printer to the same IP address as before, and they will all print to it without regard to whether or not any other computer is running.

The type of drive you're running in a computer has no relationship to the above.

If your Canon printer has a network cable jack, you can also install it as described above, and print to whichever one you choose. Win 10, by default, sets the last one printed to as the default printer. You can manually select one as your default, though.

 Thanks for the reply but both printers in this scenario ARE USB attached.  Neither is a network printer, and neither is wireless. 

 

 The problem is simple.  If I boot Windows 10 from a hard drive, printer sharing works.  If I boot Windows 10 from the SSD, it gets the error. 

 

 File & printer sharing is enabled on all with password protected sharing turned off since this is strictly a home network behind both hardware and software firewalls.  I only share a couple of junk folders, and if someone were to try printing to my printers, I'd certainly be aware of it.

OK, if your setup suits you, I'm happy for you.

 I don't know what other setup option I have.  It doesn't suit me when I can't boot 10 from an SSD and access that ML-2525 printer.

  There's no doubt in my mind it's a Win 10 bug since booting any OS from Vista to 7 to 8.1 to 10 from a hard drive works just fine.  It's just when I boot 10 from an SSD that's the problem.  This is the case on TWO DIFFERENT TEST DESKTOPS.  If that's not a Win 10 bug, somebody sure needs to explain to me why not.

 I have ways of CIRCUMVENTING the problem, but that's a pain when I see no reason to believe it's other than a bug in Win 10.

Edit: Dunno if this will help, but here's a diagram of my configuration:

http://imgur.com/wg8fNXW

Eshwar, you said you'll assist me in solving this issue.  However I tried your suggestions with no success and reported that.  I also reported additional info about how the problem only occurs when I boot from an SSD.  Booting from a hard drive (on the same PC with dual boot) works fine.  Therefore I strongly believe this is a Windows 10 bug.  Since I've been reporting this problem since JUNE, I really think it's time for a fix from Microsoft.  By the way I've also reported the problem via Feedback.

 Comments?

Funny thing, but I'm getting the same error on HDD

 Maybe it's just a matter of an uninitialized variable somewhere, and the result just depends on what happens to be at that location in RAM.  It would sure be nice if we could get an intelligent answer from Microsoft.  So far all we've gotten is these 7th grade level novice suggestions to install or uninstall drivers.  Methinks the folks claiming to be "Microsoft engineers" are nowhere near the education level of a real engineer, but more of entry level clerks who know just enough to look up something in a database and post it here.  I'd love to be wrong about this, but after dealing with this for 6 months now, that conclusion jumps out at me.  :-(