ConfigMgr Feature update issue

[Stephane Lalancette]

With this month new versions of FU:
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-16908

It's the second time that we need to download all of the feature updates that we currently use to fix issue that this does. 

Would it be possible to  improve how this is done and/or provide some guidance and more importantly improve the communication. Was only aware because I saw this post on Twitter with this post:
https://twitter.com/jandreacola/status/1316089842388938752

This is a bad admin experience and it seems that it will happen more often.

I get why they need to be updated, but I think the how can be improved.

Any insight on this?

Thks

[#2]

@Stephane Lalancette  - Hi Stephane - Thank you for your question.  You will see a formal answer to this posted on our blogs shortly.

This year we have had two security updates (CVE's) which have required that we update Windows SetUp files.  As we update these files, the consequence is the need to have new media/feature update.  This, in turn, will end up timing-out any feature update that would be pre-cached to the endpoint - and the need to bring down the new media.

Please stay tuned in the next day or so for a blog on this.

AND - yes - we understand the feedback and are looking at how we can improve this experience between our MEM, Fundamentals and Windows Servicing&Delivery teams.

[#3]

@Karen_Simpson Thanks for the update Karen.  Looking forward to the blog post and communication plans moving forward.  I think the biggest issue is the "deleted deployments" if they were active.  Also having to redistribute content in MECM (esd file) when only a relatively minor set of files (WindowsUpdateBox.exe) changed.