In Windows 10 KB5017308, Group Policy settings are broken.
Reports from administrators suggest that the Windows 10 cumulative update KB5017308, released on Patch Tuesday, is wreaking havoc on their ability to manage Group Policy Objects (GPOs).
After upgrading KB5017308, users have reported that they cannot successfully create or copy shortcuts in Group Policy Objects (GPOs). This information has been shared on social networks and the Microsoft online community.
One system administrator explained on Reddit that "specifically, we put a batch file into publicdocuments, then add a shortcut to the current user's desktop to launch it."
Since the upgrade, "the batch file is actually empty when copied over," and "the icons are not transferring over for the shortcut" (i.e., the icons are blank).
Another user on the Microsoft Community site corroborated this problem, noting that shortcuts made via GPO are "generated empty with 0 bytes and no info where shortcut "leads" to."
Multiple Windows administrators have stated that the shortcut generation issues can be fixed by unchecking the "Run in user security context" option on the impacted GPOs.Microsoft has yet to acknowledge or fix the problem.
Installing the KB5017308 update for Windows 10 (BleepingComputer)
A more extreme method involves manually deleting and hiding KB5017308.
"If you've installed the SSU and LCU package together and want to uninstall the LCU, you can do so by running DISM with the /Remove-Package command and passing the name of the LCU package as its argument. Using the command DISM /online /get-packages, you can determine the name of the package "according to Microsoft.
"Since the SSU is included in the merged package, launching wusa.exe with the /uninstall switch will fail. After installation, the SSU is permanent."
It's worth noting that because Microsoft packages all security fixes into a single update, uninstalling KB5017308 may repair the issue but would also undo the work Microsoft has done to address newly patched security holes.
Additionally, the installation of KB5017308 fails.
Also, after releasing KB5017308, many users have reported that their Windows 10 machines froze after reboot, adding an error code of 0x800F0845 to the event log.
"Since that update was installed, the machine has been stuck at the reboot prompt. Until I can find a solution, I have temporarily suspended updates. Downloading and installing the update manually yields the same effects for me "According to the User Report.
Those impacted claim that performing two consecutive reboots of the affected systems is required for the automatic rollback to take effect.
Users who tried to manually install the update by downloading it from the Microsoft Update Catalog reported running into the same reboot hang error experienced by those who used the automatic deployment method.
On Tuesday, Microsoft released KB5017308, a cumulative update for Windows 10 20H2, 21H1, and 21H2 that fixes issues and patches security holes.
During the maintenance window, Windows Update will forcefully install a required update to Windows 10.
Comments
Post a Comment