search for: ff561043

...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 Win7 users, install this on a pc. The set is found here after install : C:\Program Files (x86)\Microsoft Group Policy\Windows 10 and Windows Server 2016 ( Not all language...

...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 Win7 users, install this on a pc. The set is found here after install : C:\Program Files (x86)\Microsoft Group Policy\Windows 10 and Windows Server 2016 ( Not all language...

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