Group policy bug blocking Windows Update is finally fixed

Radu Tyrsina
by Radu Tyrsina
CEO & Founder
1 Comments
Download PDF

It was recently reported the existence of a group policy bug that blocked Windows Update if a user delayed installing the updates, but fortunately, the bug is finally fixed.

After the launch of Windows 10 Fall Creators Update, Microsoft added a new feature that allows users to delay installing the Windows Feature updates for up to 12 months. This feature is primarily useful in case of Windows Administrators or for users who simply want to delay installation.

Issues with the new feature recently reported

Lots of users have reported some problems regarding this new feature on the Microsoft TechNet forum. According to users’ reports, Windows 10 Creators update seemed to block the security updates if a user delayed installing the updates in the Local Group Policy.

If you didn’t know this by now, then it’s time you found out that you are able to delay the updates by heading to Local Computer Policy – Computer Configuration – Administrative Templates – Windows Components – Windows Update – Windows Update for Business – Select when Preview Builds, and Feature Updates are received. You’ll have the opportunity to set days ranging from 0 to 365.

Group Policy incorrectly blocked the security updates

Taskbar jump list not working

Users reported that Group Policy was blocking security updates if you changed the days to anything besides 0. The issue could only be fixed by changing the days back to 0, so the cumulative updates downloaded on the spot. Other users also claimed that deferring the updates from setting had the same effect.

This was a pretty severe problem because security updates include fixes for all kinds of potential threats and have to be installed on a regular basis. It’s all over now, thanks to Microsoft who became aware of the issue and resolved it immediately.

RELATED STORIES TO CHECK OUT:

  • This is not a group policy bug m8…its a bug in the windows update engine. Please correct the article? =)
    Group policy can’t “block the updates”. Group policy can only deliver a registry value. The windows update engine is responsible for reading that value and doing something with it – in this case, the WUE incorrectly stopped updating when reading values other than 0.