came across this thread, didnt help me..... THIS worked for me :(https://helpdeskgeek.com/how-to/remove-uninstall-a-printer-driver-from-windows/) so thought id close the loop.
Open Settings>Devices>Printers and Scanners on the left pane.
Scroll down to Related settings and click Print Server Properties
Select the Drivers tab. From the list, click on the old printer entry and select Remove
Since my previous post, not only was I still getting the update problem but I was also having unpredictable problems with printing (e.g. too large right margin on page 2 of duplex). After online research, I used a Xerox tool to update my drivers. Unfortunately, the tool gave me the wrong drivers and I lost the control interface save for some bare bone options. Worse, the new app kept wanting to install additional software but failed and rolled back every time. So I got in touch with Xerox by phone.
The guy was great. We spent almost three hours sorting out the driver mess and services that the Xerox tools had gotten me into. I now use the ps3 drivers (though I have to live with a ghost printer device sitting in my menus - if I delete it, I'll lose the PS version also). Printing works brilliantly and I no longer have this new app trying to install additional software that, it turns out, is incompatible with my printer model.
I'm still being offered Extension 18.104.22.168. Not as often (not every time I check updates) but at least once a day. The Xerox guy had no idea what the extension was nor Component 22.214.171.124. He checked with his backroom tech-heads and they didn't know either. He checked online and saw that other people were having the same problem and realised this was a bug Xerox knew nothing about - which suggests they don't look at this forum very often. He told me he would escalate the problem and that Xerox will get round to fixing it. He also told me someone from Xerox would post on this board, acknowledging the problem. But that was around a week ago - I've been checking and they've posted nothing, so I thought I would bring back this report. I should add that contrary to what some people seem to be saying, the reappearance of the Extension in update should not block any Windows Updates, and certainly I've had no trouble downloading and installing them.
Summary: I'm glad my printing problems and app/driver nightmares are over, Extension Update has not been resolved but it is a bug that Xerox now know about and said they would do something about (we will see) but my experience of Xerox tech support was great and perhaps undeserving of some of the harsher messages on this thread. Encouraging if nothing else.
The "tool" you refer to I suspect was the "Xerox Smart Start" driver installer which supposedly makes the best choice of driver for your system. It does not. It only considers if you are a Windows 10 user then defaults to use the "type 4" drivers which, as you found, are horribly crippled, designed for wireless printing from cell phones and for "Windows Store Apps" which are brain-dead apps also designed for super simplistic small screen use.
You can use that tool to opt for installation of the "type 3" drivers, the ones that give you full controll over all your printing parameters; they are designed for "desktop applications like Microsoft Office". But you still get the failure on the installation of the "Xerox Print and Scan Experience". This app looks like it would be more compatible with "type 4" but it fails regardless of which driver type you install, and it fails if you try to install it from the standalone "Xerox Desktop Print Experience" download. This is a Xerox bug. However, I don't think that app really does anything or provides any more info than you can get from the printer driver / properties interfaces or the printer's built in web service.
The Xerox Extension bug is possibly Microsoft's issue - i.e. trying to force a driver extension that meets both the "type 4" driver interface and a new firmware update you are supposed to install (which I am avoiding like the plague) which FORCES you to add and periodically change a convoluted uid/password to access the printer through its web interface. DUMB - but that's what happens when ignorant legislators try to pretend they are doing something about "privacy protection".
Yes, it was indeed Xerox Smart Start. As you say, it was trying to install Print and Scan Experience. The Xerox guy said I didn't need the latter as it would have mainly added scanner controls.
The tech support phone call took forever partly because whenever he told me to uninstall printers, stop the spool service etc. Windows would immediately see my printer as a new device and install the drivers/app that then wanted to download the Print/Scan Experience. He had me manually install PS3 (I think) drivers. This briefly resulted in two printers appearing in devices. He told me not to uninstall the 'wrong one' as this would also remove PS3. However, the phantom printer has now vanished itself from devices - though I still do see it as a pull down option when I sent printer preferences etc. My printer is actually working like a charm - best it ever has because I was having margin problems etc. with the original drivers I had before using Smart Start. We just have this repeated update problem to solve.
I have not seen the firmware upgrade you mention requiring a password, and hope I don't.
One thing I would add, is that while this printer is probably the best quality printer I've ever owned, using it has been a hassle: settings remembered in one app that are lost in another, or defaults not quite working. I feel I have to check everything, everywhere before sending a print job. Also I connect by USB, so see a network error on the printer all the time. I downloaded a pdf manual for the printer, it's 114 pages long but doesn't tell you what most of the settings do. The manual says click on "?" which, when you do, sends you to a Xerox web page with all the settings listed. It's like Xerox went out of their way to turn what should be a simple device into an obstacle course.
But, as I say, it's mostly working now (refused to print one page yesterday until I powered on and off) but we still have the Windows Update issue which I hope Xerox will, as they said, get to the bottom of.
On 25 Feb Windows 10 updated the following:
Xerox - Software Component - 126.96.36.199
Xerox - Extension - 188.8.131.52
My printer is Phaser 3330. I am not online continuously. Every time I reconnect, Windows Update finds and installs Extension 184.108.40.206. On one occasion it found the same extension multiple times during a single online session and queued them all for install, showing them as: Xerox - Software Component - 220.127.116.11 (3), so it added the bracketed figure. This install is being made every single day and is a nuisance, particularly when during shutdown or boot a message appears telling me a driver update is still pending installation.
Note: the Software Component - 18.104.22.168 installed the same day as the original install of the extension is not displaying this bad behaviour.
This works really well for us, thank you! Facing same issue here. again thank you everyone for sharing your valuable solution's.
I have the same issue and I did run the show or hide updates tool. It does now show the Xerox driver as hiden but Windows Update still brings it up to install. I don't even have a Xerox printer installed on my computer. There are Xerox printers on the network, though. What can I do to get that to either install or stop trying?
Had similar challenge...running Windows 10 and driver update for "Xerox - Extension - 22.214.171.124" failed repeatedly.
Solved this by opening Widows Administrative Tools and launching the Print Management application. Double-clicked on "All Drivers" at the left of the screen...then, a list of printer drivers appears at the right. There were two Xerox drivers installed (even though I had previously deleted/uninstalled all Xerox printers). I right-clicked on both of those drivers and selected the option to "Delete" each driver. Once this was done, Windows update didn't generate an error.
THANK YOU @hello787, this is exactly what fixed this issue for me.