Administrators have Group Policy Object issues after Win10 update • Registry

The latest cumulative update for Windows 10 is causing trouble for IT administrators who are having issues with Group Policy Object (GPO) capabilities.

Specifically, officials complain about it after installing Update KB5017308 For OS builds 19042.2006, 19043.2006, and 19044.2006 introduced in the Tuesday 13 September Patch release roll, GPO is no longer able to create or maintain shortcuts that end users use.

Many users have found that the only way to correct the problem is to uninstall KB5017308, which allows normal GPOs but also eliminates the upgraded security capabilities that the update introduced. However, an independent consultant suggested users who are experiencing problems to “pause” the update until a solution is found.

One user posted “The GPO file copy doesn’t seem to be working properly (the shortcuts lose their icon and the batch file is empty)” redditadding that they “can no longer publish software from Lansweeper.”

Another post on Reddit responded to the problem.

“Specifically, we copy a batch file to public documents, and then copy a shortcut to the current user’s desktop to run it,” they wrote. “Since the update, the icons for the shortcut have not been moved (i.e. they are now empty icons) and the batch file is actually empty when copied. It also seems to prevent us from publishing from Lansweeper, once uninstalled it is fixed.”

on me Microsoft support siteone user posted that they had “almost identical problem. Everything was fine when I uninstalled but a little worried about security updates. Today the update installed again, and the exact same thing happened…again!!! .. .. second!!!”

They said they are “now waiting to download and reinstall it again which will probably cost me another 2 hours to update and uninstall. WE NEED TO FIX THIS NOW!!!”

Microsoft noted that the update was made to address security issues in the operating system.

While many users cited manually uninstalling the update as an answer, some administrators at Microsoft support sites suggested that users could fix the broken desktop shortcuts issue by unchecking the Run in user security context setting.

One user wrote that it assumed that “running in security context” was required for the %userprofile% variable to work, but found that it was not.

For its part, in its description of KB5017308, Microsoft explained how users can remove the latest cumulative update (LCU) and servicing stack update (SSU) after they are installed.

The company said administrators can “use the DISM /Remove-Package command line option with the LCU package name as an argument. You can find the package name with this command: DISM /online /get-bundles. Run Windows Update Standalone (wusa .exe) with /uninstall Switching on the merged package will not work because the merged package contains an SSU. You cannot remove SSU from the system after installation. “

record I asked Microsoft for comment on this matter. We will update the story with any response. ®