Windows 10 KB5017308 inflicting troubles with Group Policy settings

 

The Windows 10 KB5017308 cumulative update launched this Patch Tuesday is reportedly inflicting Group Policy Object (GPO) issues, in accordance with admin reports.

According to reviews shared throughout a couple of social networks and on Microsoft's online community, GPO file operations will no longer work as they can no longer create or reproduce shortcuts efficiently after installing KB5017308. 

"Specifically, we reproduction a batch file into public\documents, then reproduction a shortcut to the modern user's computer to run it," one admin stated on Reddit. 

"Because the replace, the icons are no longer shifting over for the shortcut (i. E. They may be smooth icons now) and the batch file is absolutely empty when copied over." 

Another showed this issue on the Microsoft network website, saying that all shortcuts created by GPO are "created empty with 0 bytes and no info where shortcut "leads" to."

While Microsoft is to formally know the issue and offer a restore or a workaround, multiple home windows admins have suggested that un-checking the "run in user safety context" option at the affected GPOs will deal with the shortcut advent troubles.

Others have also advised a greater radical restore that calls for manually uninstalling and hiding the kb5017308 cumulative update.

"to do away with the lcu after setting in the blended ssu and lcu package, use the dism/put off-bundle deal command line want with the lcu bundle discover due the fact of the argument. You have to discover the bundled discover with the resource of manner of the use of this command: dism /on-line /get-packages," microsoft says.

"on foot home, windows trade standalone installer (wusa. Exe) with the /uninstall turn on the mixed package deal will now not art work due to the truth the combined package deal includes the ssu. You can no longer do away with the ssu from the machine after installation."

However, it is critical to factor out that, when you suppose that Microsoft bundles all protection fixes into a single replace, disposing of kb5017308 can additionally moreover unravel the malicious software program then once more will moreover get rid of all fixes for currently patched protection vulnerabilities. 

KB5017308 failing to install

Another apparently significant hassle encountered after deploying KB5017308 is affecting Windows 10 structures that will cling on reboot after set up with an 0x800F0845 delivered to the match log. 

"Ever for the reason that replace was once downloaded the computer hangs on the required reboot after the install. I have disabled updates till I can locate a fix. I've tried to download the replace and deploy manually but get the identical results," a consumer document reads.

Those affected say that the automated rollback will solely set off after rebooting the affected structures twice in a row.

While downloading the replacement from the Microsoft Update Catalog and putting in it manually generally fixes troubles in the place the updates can not be deployed, customers who tried it stated that, in this case, they encountered the identical reboot grasp bug.

The KB5017308 cumulative replace was once released on Tuesday to get to the bottom of bugs and tackle safety vulnerabilities on systems running Windows 10 20H2, 21H1, and 21H2.

This Windows 10 update is obligatory and will routinely be set up through Windows Update at some point in the servicing window.