This time around Google Chrome messed around with the printer settings. I closed the SystemSettings.exe app and captured another trace.
Set pdf default printer windows#
The thing about the " Let Windows manage my default printer" policy is that it is actually not a policy setting, but a group policy preference, meaning it deletes the specified registry value before setting it again. Just a few entries later, svchost.exe set the LegacyDefaultPrinterMode value back to 1.Īha! Now I was getting somewhere. The next hit offered the next clue: SystemSettings.exe set the "missing" registry value to zero, thus enabling modern printer management. The first hit was a RegDeleteValue by svchost.exe (it hosts the group policy process), followed by a RegQueryValue operation initated by the SystemSettings.exe (Immersive Control Pane), which resulted in NAME NOT FOUND error. Then I stopped the capture and looked at what Process Monitor had collected. I ran Process Monitor, configured the filter to include the HKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\LegacyDefaultPrinterMode path and executed gpupdate. I had to look under the hood at registry activity associated with the printer management to see if that would reveal the reason why Windows wasn’t honoring the GPO's setting. I re-ran gpupdate one final time and Windows reverted back to the legacy printer management. I re-ran gpupdate and after a brief moment the " Let Windows manage my default printer" checkbox got activated. I also noticed that the " Let Windows manage my default printer" checkbox briefly flashed when gpupdate ran in the background. To my consternation, the default printer changed to " Microsoft Print to PDF".
Set pdf default printer windows 10#
Then, I went to a Windows 10 machine, opened the printer management, verified that the setting ensuring that Windows will not manage the default printer was enabled, set the default printer and ran gpupdate /force. For that, I verified that the customer enabled the " Turn off Windows default printer management" (under User Configuration\Administrative Templates\Control Panel\Printers) policy. The first step in my analysis was to reproduce the issue to see if it revealed any clues.
0 kommentar(er)
