Is something missing from step 2? A search on "..." leads to too many entries to be helpful. Also once in regedit and we "go to: ...", what are we supposed to do their? Otherwise it appears the regedit steps are superfluous as there is nothing in the registry that should be edited.
Hey there!
For fix your problem follw these steps:
Has anyone come across a real solution for this that does not involve getting rid of your Xerox printer or print drivers? Most of the posts I have seen on this site indicate to just get rid of the driver and it goes away. That is great if you are getting rid of the printer but that is not the case. While I suspect this is actually a Microsoft issue (it is coming through via Windows Update) I assume Microsoft will just pass the blame and say that it is a Xerox issue.
This has been going on for over a year now. I have another system that is trying to have the Xerox Print Experience 6.0 pushed to it about every 2 hours via Windows Update. What a mess.
This solution solved the continuous installation. This was a temporary solution. With Updates, the Xerox Extension Circus has started again. I have a C405, an it appears this isn't a part of this printer’s software. Again, I suspect Registry Data droppings that never are cleared by manufactures. Most love to bloat the registry or are just too lazy to clear the little piles out.Next round
That worked fine. I was capable of dumping the Xerox 6605 drivers that I no longer have. Xerox should clean up their Data droppings in the registry, when software is deleted. This is something most companies don't invest time in. Again, another Agile Programming ploy
I don't have Windows 11, nor will I install it until Microsoft releases Service Pack 3. Experience since Windows 98 has shown, don't touch the new environment until all have tested it and Service Pack 3 is released. The Hardware limitations Microsoft poses on Windows 11 present no benefits. My 10-year-old Dell works fine, is fast and efficient. An old saying states; "Don't fix a running system"
Thanks. That worked. I had to load the printmanagement extension to windows 11 pro wks, first, however.