Available since Tuesday, September 13, 2022, the KB5017308 update for Windows 10 seems to pose some problems for administrators, as it disrupts the proper functioning of group policies (GPO). Let’s do a check in.
As a reminder, update KB5017308 applies to Windows 10 versions 20H2, 21H1 and 21H2.
If we refer to the various reports on the Microsoft forum and on Reddit, we see that the KB5017308 update for Windows 10 disrupts the proper functioning of certain GPOs. For example, on Redditwe can read the testimonial of an administrator which evokes GPO which copies a Batch script to the “Public\Documents” directory of the machines and which creates a shortcut on the Desktop in order to allow the execution of this Batch script. Following the installation of the update, it turns out that the shortcut icon is not displayed so the icon is white, and the Batch script is empty, while the source file is correct .
Another administrator also mentions a problem with all the shortcuts created by GPO: the elements are created, but they are empty. Indeed, this can be confusing for end users.
At this time, Microsoft has not officially communicated about this bug, so there is no official fix or workaround. However, data subjects claim that unchecking the “Run in user’s security context” on the GPOs concerned allows you to troubleshoot shortcut creation issues. It’s still a shame to have to uncheck this option.
Other users have made the decision to directly uninstall KB5017308 update for Windows 10, which solves the problem! This proves that it is the update that is the cause of this new bug.
KB5017308: Update causing error 0x800F0845
Some people seem to have Trouble installing this update KB5017308, as well as that of the previous month, namely KB5016616. Windows 10 hangs during reboot to complete installation. In the end, an alert is generated in the Windows Event Viewer, with a similar error for these two KB: “Windows failed to install the following update with error 0x800F0845: 2022-08 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5016616).“. Sometimes it’s the mistake 0x800f0845 which is also encountered.
Have you encountered any issues on your end? Feel free to leave a comment to give feedback to the community!
Logiciel – OS,Microsoft,Windows 10,