NotificationsNEWRECENTYou've reached the end of all notifications from the past 30 days.You've reached the end of all notifications from the past 30 days.Mark as readMark as unread<span>{username}</span> replied to <span class="notification-center__item__description__link">{title}</span><span>{username}</span> mentioned you in <span class="notification-center__item__description__link">{title}</span>
What’s everyone doing in regards to the issue with KB5034441? Not feasible in a large environment to change the recovery partition size, and Microsoft is reportedly working on a fix, but no timeline. We have 599 impacted assets with only 70 updated. Majority of those are attempting to patch and users getting Automox restart prompts daily.
I’m going to ignore for now, but was curious what others were doing to deal with this.
This could be run as a Worklet with the latest ‘Safe OS Dynamic Update’ as a payload. As always, make sure to test something like this vigorously.
The other potential approach is to ignore these packages either on the Software page or within a policy itself. There are sporadic reports in the reddit thread about Windows Update not providing this KB to endpoints. Deferring until a February cumulative update might not be the worst idea, but thats a risk each company needs to decide for themselves.
This could be run as a Worklet with the latest ‘Safe OS Dynamic Update’ as a payload. As always, make sure to test something like this vigorously.
The other potential approach is to ignore these packages either on the Software page or within a policy itself. There are sporadic reports in the reddit thread about Windows Update not providing this KB to endpoints. Deferring until a February cumulative update might not be the worst idea, but thats a risk each company needs to decide for themselves.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.