Windows 10 Update
So happy you cannot currently be with the updates from Microsoft. Not only that the latest Patchday has once again produced a number of bugs, it has also released the first updates that bring the Epson dot matrix printer back to work, but now again addressed the same problem. There are also other issues with the release of bugfix updates. After an update was withdrawn in the last week, there is more confusion about the upcoming updates for Windows 10.
Also Read: Windows Defender Receives A Poor Rating On The AV Test Again
For example, Microsoft is expected to release more cumulative updates shortly, because you can already see the corresponding entries in the Knowledge Base, but no updates for the users. In the update history, there is already a created entry with the number KB4051963 for the case Creators Update – the link to the entry currently shows a 404 error page.
Also Read: Windows 10 Gets A New Game Bar
The situation is different for an older version of Windows 10: So far, only an article about KB4051033 for OS Build 14393.1914 is fully available. The build is out of line with the Windows 10 Anniversary Update, also known as Windows 10 Version 1607. Users who are still working on this release from last year should have already received the update or can now install it. The list of bugs fixed is long.
Also Read: Microsoft Publishes Update For Windows 10 By Mistake
This update includes quality improvements. This update does not introduce any new operating system features. The most important changes include:
- Fixed an issue where screen tearing and/or encrypted content would appear in applications when a computer is connected to three or more USB 3.0 displays. This happens when you change the content on one or more of the connected display devices.
- Fixed an issue where a service would fail to start if two or more services use the same built-in account (for example, NetworkService or LocalService). When this problem occurs, the failed service reports the error: “The service did not start because of a login failure” or “A specified logon session does not exist. It might have already ended.”
- Fixed an issue where scheduled tasks with saved credentials could not be executed when Credential Guard (in Windows Defender) is enabled. The task fails and reports Event ID 104 with the following message: “Task Scheduler failed to log on \ Test.” Error occurred in LogonUserExEx. “User Response: Make sure the task credentials are specified correctly: 214794373726. 2147943726: ERROR_LOGON_FAILURE (The username or password is incorrect). “
- Fixed an issue where BitLocker decryption or encryption of a drive could corrupt files protected by the Encrypting File System (EFS).
- Fixed an issue where opening Microsoft Office files from a file server with Windows Information Protection enabled failed with the error message “Sorry we could not open document xxx”.
- Resolved an issue where a Storage Spaces Direct (S2D) drive that fails or is removed from a node is incorrectly reported as healthy by admin tools. These tools include Get-Physical Disk, Server Manager, and Failover Cluster Manager.
- Resolved an issue where a repair job could be interrupted indefinitely after adding a node to an S2D cluster again.
- Fixed an issue where incomplete repair of storage spaces could lead to incorrect metadata, resulting in future repairs not working anymore.
- The Network flyout has resolved an issue where closing the login dialog unexpectedly (eg, clicking outside the window) prevents additional login dialogs from appearing when the user tries to connect to the same network.
- A token leak has been fixed in the services.exe file that occurs after the application of MS16-111 / KB3175027. This results in a kernel session object leak that degrades system performance over time. This particularly applies to Terminal Server implementations, where typically more user logins occur.
- Fixed an AppProxy issue that could prevent mobile devices from connecting to a network.
- Fixed an issue where the Remote Desktop Clipboard Redirector policy would not take effect if the connection to an existing session is restored and the policy has changed between the original connection and the reconnection to the session.
- Fixed an issue where, in a non-English locale, the OEM OOBE process could not complete when building a failover cluster. This process fails with the error message “Unable to find an integration component with the given name”.
- Improved performance in querying the file system formats of Direct Access storage media.
- Fixed a clustering health policy issue when dealing with unresponsive clustered drives.By default, drives are shut down for unresponsive conditions. The frequency of unresponsive reset remediation is too aggressive.
- Resolved issue in network flyout where closing the login dialog unexpectedly (eg clicking outside the window) prevents further login dialogs from appearing when the user tries to connect to the same network.
- Improved performance when launching applications that use Virtual Disk Service to manage volumes.
- Resolved an issue that affected some Epson SIDM (Dot Matrix) and TM (POS) printers that could not print on x86 and x64-based systems. This problem affects KB4048953.