search for: driverisol

Hello, when deploying drivers via Point-and-Print recent Windows (tested with Windows 10 1607) asks the user to confirm the driver installation. An appropriate Policy [1] is set up so that no user interaction should be required for the driver installation. There are similar reports [2,3] that identify updates KB3163912, KB3172985 and KB3170455 causing these issues. However, Windows 10 1607

...y image, updating to 6.2.1 ) 2 tests, clean pc, without drivers and test with one as imaged. The HP park tools have admx templates to managing the driver settings, use that. If possible use package-aware drivers. Search in the .INF for lines like :  PackageAware=TRUE       Some info: - DriverIsolation : https://msdn.microsoft.com/en-us/library/windows/hardware/ff560836(v=vs.85).aspx - Packaged Driver : https://msdn.microsoft.com/en-us/library/windows/hardware/ff561043(v=vs.85).aspx ‘ - ( new polices for win10 1607 found here: https://www.microsoft.com/en-us/download/details.aspx?id=53430...

...y image, updating to 6.2.1 ) 2 tests, clean pc, without drivers and test with one as imaged. The HP park tools have admx templates to managing the driver settings, use that. If possible use package-aware drivers. Search in the .INF for lines like :  PackageAware=TRUE       Some info: - DriverIsolation : https://msdn.microsoft.com/en-us/library/windows/hardware/ff560836(v=vs.85).aspx - Packaged Driver : https://msdn.microsoft.com/en-us/library/windows/hardware/ff561043(v=vs.85).aspx ‘ - ( new polices for win10 1607 found here: https://www.microsoft.com/en-us/download/details.aspx?id=53430...

Hi all. I have read carefully all your posts and I am glad to see that some of you workaround this new MS surprise... To solve the problem, I understand that : * if you use the "AD way of deploying printers", the workaround is to use the "Computer ConfigurationPoliciesAdministrative TemplatesPrintersOverride Print Driver Compatibility Execution Setting Reported By Print