As we reported earlier about the renewed printing problems under Windows 10 and Windows 11 – now Microsoft has already addressed the issue and has confirmed the problem as a “Known Issue” in the Windows 11 status information.
According to the report, the individual printer problems have now been confirmed by Microsoft after starting Windows 11. A new addition is a bug that can occur if the print server and the print client are in different time zones. The problem is likely to affect a large number of users in the corporate environment.
Printing for the admin only?
There are other printer problems, including with HTTP connections, with individual print specifications, and in connection with the Internet Printing Protocol (IPP). The error is now re-listed in the documentation for known problems in Windows 11. Recently, it was added to the release health status that every print job is prompted to log in, which may mean that users can no longer print. The bug report was opened on October 15th. It says:
- You will be prompted for administrative credentials each time you try to print
- Status – Confirmed
- In environments where the print server and print client are in different time zones, you may be prompted for administrative credentials each time you try to print.
- Note: The affected environments described in this issue are typically not used by devices that are intended for personal use. The printing environments affected by this problem are more likely to be found in companies and organizations.
- Affected platforms:
- Client: Windows 11, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1 ; Windows 7 SP1
- Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Microsoft is currently working on a solution. The team expects a solution to be available by the end of October. Then there will probably already be a bug fix update as part of the optional updates.
Manager at Research Snipers, RS-NEWS, Digital marketing enthusiast and industry professional in Digital technologies, Technology News, Mobile phones, software, gadgets with vast experience in the tech industry, I have a keen interest in technology, News breaking.