locked
windows 10 1607 printer installation from windows 2012 r2 RRS feed

  • Question

  • after doing a few windows 10 anniversary upgrades  the printers already installed on PC's have gone haywire.. the default settings have changed from the default settings to print double sided, tray 4 instead of 2

    after removing the printers and reinstalling from  (windows 2012 r2) server the default settings of the printer are not brought across, windows 10 1607 appears to change the settings that have been setup on the server and wants to print double sided

    how do we sort this out?

    Tuesday, August 16, 2016 10:02 AM

Answers

All replies

  • Hi ,

    Does this issue only affect Windows 10 version 1607 machine?

    We have been reported that this issue that Windows 10 version 1607 may change printer default settings. If this issue only occur on Windows 10 version 1607 machine, please refer to this similar case to have a try. And,  try the built-in "Feedback" tool to submit the issue on your side. I hope it could be fixed in the near future

    Default Printer Frustration
    https://social.technet.microsoft.com/Forums/windows/en-US/1b6bc17e-acfc-4f13-8e77-68797adcc8b2/default-printer-frustration?forum=win10itprogeneral

    Best regards


    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by nik3com Wednesday, August 17, 2016 7:24 AM
    Wednesday, August 17, 2016 7:21 AM
  • ok thanks, yes only windows 10 version 1607 machines 

    i will look at the other thread thanks for the heads up

    nick


    nicholas hay

    Wednesday, August 17, 2016 7:24 AM
  • I have exactly the same problem on all clients running 1607. The printer settings always gets resetted. Have you already a solution for this problem?

    Wednesday, August 17, 2016 11:53 AM
  • yeah go back to 1511 there is no fix at this time

    nicholas hay

    Wednesday, August 17, 2016 11:57 AM
  • We're having the same issue. It's not the same issue as the one in the link Rik Li posted. This needs to be fixed MS.

    Thursday, September 15, 2016 4:57 PM