Registered here just to post this. I manage the IT department for a mid-size business. Many of our machines use Windows 10. Many of our machines use AMD Radeon R7 250 video cards for dual monitors. I downloaded the latest driver yesterday (whql-radeon-software-crimson-relive-17.9.3-win10-64bit-oct2.exe). When I went to install it it did the usual check and gave me the option to install 17.10.1, instead. I chose this and chose "Clean install", as I've been doing for years. After the systems rebooted and driver installation finished I noticed that they were missing all their printers. No error messages, no services stopped, rebooting again did not help. It was as if every printer on the system had simply been right-clicked and removed. This problem is identical and consistent on six different machines (all Dell OptiPlex business-class systems with a variety of network-connected HP enterprise printers, also running the latest drivers from HP).
Not sure what the issue is, nothing shows up in the event logs, but I'm having to reinstall a lot of printers today. :(
Solved! Go to Solution.
I know silly question maybe, but did you notice if the printers were already gone before you installed the driver, the reason I ask is that Patch Tuesday is today, and MS started pushing out "2017-10 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4041676)" late Monday night actually, there were some changes particularly for Citrix based or Redirected Printer environments that caused the removal of printers or inability to print, there were also a lot of changes that were not described and this may have just been a coincidence between your AMD installation and the Cumulative update, especially if they were downloaded and the computer was in a ready to update state upon shutdown/restart.
Did you notice at all when they were restarting that it took longer and was doing the "Windows is updating Files" shebang? If so it may have been that Patch update from MS that did this, or very distant possibility that the mix of the two things, that update pending for commit and the clean install of the AMD driver just colliding in a bad and unforeseen way. Are you running an Active Directory Domain, Tree, or Forest? Were these printers locally installed or are they running from a print server or are they objects in an Active Directory container?
This would be the first time I've seen a GPU software update/change cause something to go wrong in the Print Render Subsystem or Spooler/Print Server arena, but nothing really shocks me anymore to be honest, so many of these classically isolated systems are becoming so intertwined and woven that who knows anymore to be honest...
BTW did you check the following logs as well in the following branches of the Event Viewer in the "Windows" sub-branch as shown?
Anyway let me know, this is an interesting one for sure!
This is the issue that SPIKEYPUP was mentioning about in the new Patch Tuesday update:
Addressed issue where the ServerSecurityDescriptor registry value does not migrate when you upgrade to Windows 10 1703. As a result, users might not be able to add a printer using the Citrix Print Manager service. Additionally, they might not be able to print to a client redirected printer, a Citrix universal print driver, or a network printer driver using the Citrix universal print driver.
BTY, Thanks for reminding me about Patch Tuesday update. Forgot all about it ( Spikeypup).
Hi! Thanks for the followup. Those are some good suggestions, especially about the Patch Tuesday updates. I think one of PC's had already run them, and five more PC's ran them later, but I didn't notice if they might've been directly related to all the printers disappearing. That would be quite a collison - the patches + the clean install, but I can see what you're getting at!
To answer some of your other questions, we're not running anything Citrix related. Standard Windows Active Directory domain, but the printers are all added with the HP universal printer driver directly via their IP addresses (not through AD). Everything was gone though not just the HP stuff -- even the generic Microsoft "Print to PDF" printer was gone.
As a test I think I'll try reinstalling the AMD driver again but am not sure I'll be able to duplicate these exact conditions. Maybe Uninstall 17.10.1, reinstall an older version, then try the installer update again with the same options? Stay tuned, this could be exciting! ;)
Latest version of Crimson also freeze on a CLEAN window Creator 1703 installation.
These drivers are getting buggy by the release
No problem! Yeah gotta watch those 2nd Tuesdays, they can be quite treacherous! glad I could be of some help, well at least a reminder minder
Very intriguing, keep me posted! Strange about the MS PDF, but at the same time not really, they were trying to update it to a new renderer and there was a bug in their deployment appx package, lol, so it could cause the printer to be uninstalled, with no replacement driver/renderer installed. Oh MS...how I love thee sometimes.
Interesting, I'm familiar with the HP Universal, in fact it is one of my favorite Universals, I suppose it could be considered a redirected printer situation, but perhaps the issue extends beyond Citrix Universal drivers and into the HP ones and who knows what other vendors as well, it wouldn't shock me; because if the server( in this case print) security descriptor is invalid or not migrated, then the system doesn't have the SID/GUID for the printer server object (which the universals could be considered as), which just like in AD, if you don't have a SID or if it gets orphaned, your account/user/object for that SID just doesn't exist ( such as when you open a security window for an object and it just says Unknown Account/SID or ???-????-???? kind of jazz), which is why it is always a bad idea to mess with SIDs or GUIDs. This happens such as when you erase an account from AD or the local user store that is a principal or owner of an object and you don't change that principal to another account before deleting the current principal, and you end up screwed out of access from it.
Essentially that is what they did here by failing to migrate those keys and descriptors. I could only imagine the horror for the IT person who has a sprawling 20 building campus serviced by Citrix Metaframe and Citrix Print services... I'd call out sick but that'd only last so long I suppose lol.
Now time for my evening scotch and some youtube to lull me to sleep zzzz.....
Hope all is back in order for you Mike, let me know what you find out!
I confirm that there's something in the 17.10.1 package that deletes windows printers. It's not related to the last CU installation process (I'm on 15063.674).
Unlike in the OP, in my system it's not related to driver installation, but Windows Printers are immediately deleted after running the 17.10.1 uninstaller. I've tried it two times with the same result.
17.9.3 isn't affected (tried it in the middle of 17.10.1 installations).
Also, on the OP situation, even if the 17.10.1 drivers were never uninstalled, it could have been their setup that was used to clean the previous 17.9.3 (instead of 17.9.3's uninstaller that seems fine on my system). So it prematurely resulted in missing printers, as I can reproduce on my system via uninstall.
I find really difficult to understand, how a Graphics driver, can delete or uninstall a printer from a computer. What relationship does a Graphic driver have with a printer driver in a computer?