Group Policy settings are being affected by the Windows 10 update KB5017308.

Group Policy Object (GPO) problems are purportedly being caused by the Windows 10 KB5017308 cumulative update, according to administrator reports.

Social media reports and posts on Microsoft’s online community claim that after installing KB5017308, GPO file operations will cease to function since shortcuts can no longer be correctly created or copied.

 

One administrator explained on Reddit that they “exactly copy a batch file into public documents, then add a shortcut to the current user’s desktop to launch it.”

 

Since the upgrade, the shortcut’s icons are not moving over (they are now blank), and copying the batch file over actually leaves it empty.

On the Microsoft Community page, a second user corroborated this problem by stating that all shortcuts generated by GPO are “created empty with 0 bytes and no info where shortcut “leads” to.”

Multiple Windows administrators have claimed that the issue can be resolved by unchecking the “Run in user security context” option on the problematic GPOs, despite the fact that Microsoft has yet to formally acknowledge the problem and offer a remedy or workaround.

 

A more radical solution that necessitates manually deleting and hiding the KB5017308 cumulative update has also been proposed by others.

“Use the DISM/Delete-Package command line option with the LCU package name as the argument to remove the LCU after installing the merged SSU and LCU package. DISM /online /get-packages is the command to use to find the package name “says Microsoft.

“The combined package contains the SSU, therefore using the Windows Update Standalone Installer (wusa.exe) with the /uninstall switch will not work. After installation, the SSU cannot be taken out of the system.”

However, it’s crucial to note that uninstalling KB5017308 will also delete all fixes for previously addressed security vulnerabilities because Microsoft combines all security changes into a single update.

KB5017308 also has installation issues
Windows 10 PCs that hang on reboot after installation with an event log entry of 0x800F0845 are another issue that appears to be widespread after applying KB5017308.

 

“Since downloading that update, the machine has become unresponsive during the obligatory reboot that follows installation. Updates have been blocked while I look for a solution. I’ve attempted to manually download and install the update, but I still get the same outcomes “Reads a user report.

Those who are impacted claim that restarting the affected systems twice in a row is the only way to get the automated rollback to occur.

Users who tried it reported that they faced the identical reboot hang bug in this instance, despite the fact that obtaining the update from the Microsoft Update Catalog and manually installing it typically resolves difficulties where the updates can’t be delivered.

For computers running Windows 10 20H2, 21H1, and 21H2, the KB5017308 cumulative update was released on Tuesday to fix bugs and address security concerns.

During the servicing session, Windows Update will automatically install this necessary Windows 10 update.