Does Packaging Plugins Not Follow Suit Unlike Compiling A Game?

Upgraded to Visual Studio 2019 (16.4.3) today from 2019 16.4.1.
I could not package a plugin, even a simple template plugin not modified. The failure code was C1853 in the Log, and the error text stated: precompiled header file is from a previous version of the compiler, or the precompiled header is C++ and you are using it from C (or vice versa).

Couple of things: How does this fit in to 4.24’s new AutoSDK? Are plugins supposed to follow suit as when you compile and build anything else?

I found the answer, for me, to be found here: https://forums.unrealengine.com/development-discussion/c-gameplay-programming/1567923-solved-fatal-error-c1853-on-plugin-packaging-only

After the VS upgrade, and failing to package even a template plugin, The only Windows 10 SDK checked was 10.17763.0). Using the solution provided in the forum, I unchecked that version, and checked the latest version (10.0.18362), and all worked as it should. But why?

I was able to compile and package plugins just before updating Visual Studio, so what causes this exactly? It obviously has to do with upgrading Visual Studio and enforcing the use of the latest Windows 10 SDK available for VS, but I would like to know why.

-Erol