Resolved issues in Windows 10, version 1507

See a list of known issues that have been resolved for Windows 10, version 1507 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.


Resolved issues

SummaryOriginating updateStatusDate resolved
Receiving a prompt for administrative credentials every time you attempt to print
This issue affects devices in environments in which the print server and print client are in different times zones.
OS Build 10240.19060
KB5005569
2021-09-14
Resolved
KB5006675
2021-10-12
10:00 PT
Administrator credentials required every time apps attempt to print
Certain printers in some environments using Point and Print might prompt for credentials every time when printing.
OS Build 10240.19022
KB5005040
2021-08-10
Resolved External
2021-09-16
18:23 PT
Printing and scanning might fail when these devices use smart-card authentication
Non-compliant printers, scanners, and multifunction devices might fail to print when using smart-card authentication.
OS Build 10240.19003
KB5004249
2021-07-13
Resolved
2021-08-03
10:36 PT
Apps might have issues accessing event logs on remote devices
Event logs might not be accessible from remote devices unless both devices have updates released June 8, 2021 or later.
OS Build 10240.18967
KB5003687
2021-06-08
Resolved
KB5003687
2021-06-08
10:00 PT
Security updates released May 11, 2021 might not offer in managed environments
Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager and managed devices are affected.
OS Build 10240.18932
KB5003172
2021-05-11
Resolved
2021-05-11
19:01 PT

Issue details

October 2021

Receiving a prompt for administrative credentials every time you attempt to print

StatusOriginating updateHistory
Resolved KB5006675OS Build 10240.19060
KB5005569
2021-09-14
Resolved: 2021-10-12, 10:00 PT
Opened: 2021-10-15, 17:21 PT
After installing KB5005569 or later updates, you might receive a prompt for administrative credentials every time you attempt to print in environments in which the print server and print client are in different times zones.

Note The affected environments described in this issue are not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises 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
Resolution: This issue was resolved in KB5006675. If after installing KB5006675 you still receive the prompt every time you print, see Q1 in the "Frequently ask questions" section of KB5005652—Manage new Point and Print default driver installation behavior (CVE-2021-34481).

September 2021

Administrator credentials required every time apps attempt to print

StatusOriginating updateHistory
Resolved ExternalOS Build 10240.19022
KB5005040
2021-08-10
Last updated: 2021-09-16, 18:23 PT
Opened: 2021-09-16, 18:11 PT
After installing KB5005040 or a later update, certain printers in some environments using Point and Print might receive a prompt saying, "Do you trust this printer" and requiring administrator credentials to install every time an app attempts to print to a print server or a print client connects to a print server. This is caused by a print driver on the print client and the print server using the same filename, but the server has a newer version of the file. When the print client connects to the print server, it finds a newer driver file and is prompted to update the drivers on the print client, but the file in the package it is offered for installation does not include the later file version.

Workaround: Verify that you are using the latest drivers for all your printing devices and where possible, use the same version of the print driver on the print client and print server.

Affected platforms:
  • Client: 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
Resolution: This issue is resolved externally by adjusting the print drivers in your environment. If updating drivers in your environment does not resolve the issue, please contact support for your printer manufacturer (OEM). For more information, see the Q1/A1 in the "Frequently asked questions" section of KB5005652.

July 2021

Printing and scanning might fail when these devices use smart-card authentication

StatusOriginating updateHistory
ResolvedOS Build 10240.19003
KB5004249
2021-07-13
Resolved: 2021-08-03, 10:36 PT
Opened: 2021-07-23, 14:36 PT
After installing updates released July 13, 2021 on domain controllers (DCs) in your environment, printers, scanners, and multifunction devices which are not compliant with section 3.2.1 of RFC 4556 spec, might fail to print when using smart-card (PIV) authentication.

Affected platforms:
  • Client: 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, 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
Next steps: A temporary mitigation is now available. For more information, please see KB5005408 - Smart-card authentication might cause print and scan failures.

June 2021

Apps might have issues accessing event logs on remote devices

StatusOriginating updateHistory
Resolved KB5003687OS Build 10240.18967
KB5003687
2021-06-08
Resolved: 2021-06-08, 10:00 PT
Opened: 2021-06-07, 16:10 PT
After installing KB5003687 or later updates, apps accessing event logs on remote devices might be unable to connect. This issue might occur if the local or remote has not yet installed updates released June 8, 2021 or later. Affected apps are using certain legacy Event Logging APIs. You might receive an error when attempting to connect, for example:
  • error 5: access is denied
  • error 1764: The requested operation is not supported.
  • System.InvalidOperationException,Microsoft.PowerShell.Commands.GetEventLogCommand
  • Windows has not provided an error code.
Note Event Viewer and other apps using current non-legacy APIs to access event logs should not be affected.

Affected platforms:
  • Client: 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 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
  • Server: 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
Resolution: This is expected due to security hardening changes relating to Event Tracing for Windows (ETW) for CVE-2021-31958. This issue is resolved if the local and remote devices both have KB5003687 installed.

May 2021

Security updates released May 11, 2021 might not offer in managed environments

StatusOriginating updateHistory
ResolvedOS Build 10240.18932
KB5003172
2021-05-11
Resolved: 2021-05-11, 19:01 PT
Opened: 2021-05-11, 14:58 PT
When checking for updates within Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager and managed devices that connect to these servers, KB5003172 might not be available or offered. Note: This might also affect Security Only and Internet Explorer Cumulative Rollups, on platforms that receive these types of updates.

Affected platforms:
  • Client: Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Resolution: This issue is now resolved on the service-side and updates should be available. Note: If you initiate a synchronization cycle and are still not being offered the updates, please check again soon. There might be slight delay as it propagates to all servers in all regions.