If we look at the changelogs, all of these updates include a single change. Previous updates introduced an Event Viewer bug in Windows 10. Microsoft fixed this issue in the recent releases. At the time of writing this article, there are no reports of installation issues. We will keep you updated once more details are available.
KB4509477, KB4509478, KB4509479 major features and improvements
Event Viewer bug fix
Microsoft rolled out KB4509477, KB4509478, KB4509479 to resolve a bug affecting Event Viewer. Previously, some devices were unable to connect to some Storage Area Network (SAN) devices that used iSCSI. This issue triggers the following bug “Target failed to respond in time for a login request”. Thankfully, the bug has been fixed for all users now. If you are experiencing the same issue, you need to update your system as soon as possible.
Known issues
Although the updates fixed the Event Viewer bug in Windows 10. However, recent releases bring their own issues. Microsoft warns that you may experience issues while performing some specific operations on folders or files. Microsoft says that the operations may fail with the error STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5). This issue is caused after the installation of KB4509477, KB4509478, KB4509479. Secondly, Microsoft acknowledged that users who installed kb4509478 may see a black screen at startup. Microsoft is currently working on fixinf these issues. We expect to receive a patch on July Patch Tuesday.
Download KB4509479, KB4509478, KB4509477
These updates should be available automatically on your system. You can install latest updates from Settings > Update & Security > Windows Update and select Check for updates. If the update is not available via Windows Update, you can visit the Microsoft Update Catalogue to download the update manually on your system.
Download KB4509479 Download KB4509478 Download KB4509477
RELATED ARTICLES YOU NEED TO CHECK OUT:
5 best Windows 10 event log viewers How to clear the Event Log in Windows 10, 8, 8.1, 7
Name *
Email *
Commenting as . Not you?
Save information for future comments
Comment
Δ