@Dgk - the statement was they didn't know other than it was a re-issue (different size) of the old ESU WU enabling System
It works!! As easy as opening a cmd window, navigating to the folder containing the patch, and pasting the corresponding command above. Tested it on both x86 and x64 with the v4 bypass lol. I only have the SSU up till April and no May ESU prep package and all the other updates (including kb4552965 for .net 3.5) installed fine; I'm assuming you'll need the May SSU and that ESU whatever package for the next round though. Thank you so much for figuring this out and saving others precious time. Exactly, thank you. The ESU key is not available to consumers, and let's just say there are very good reasons not to switch to Windows 10 beyond application compatibility. I found the uncharacteristic push to get users onto Win 10 highly suspicious even by those standards, and that's saying something. I do like the added exploit mitigations in 10, but at what cost?
Thanks guys ! I manually installed KB4556836, KB4555449 and KB4552921 on Windows 7 Ultimate x64 (ESU Bypass v4). Again,thank you !
Credits to @vinzf and @pesho_georgiev for finding and implementing an excellent solution to this 202005 dotNET update issue... thank you very much! See EXPLANATION and EASIEST SOLUTION to the issue.
Just confirming the above method works with KB4552953 as well (.net 4.8 security-only) on both x64 and x86. Just run the following from a command prompt in the same folder as the patch: ndp48-kb4552953-x64_251d9ac6b7e872dabe6d772f5925876ac5232db3.exe /msioptions "ESU_LOCK=2D40812E-974C-4EA2-8DCC-63C992D505B9" Replace the filename with the x86 version if necessary. Thanks again to vinzf for solution. Is there a way to get these to show up as installed updates in WU?
Great find @vinzf Once ndp48_4552921 has been installed, the KB556399 update was finally installed through WU. Good job my friend.
Thanks. One more question - this command doesn't change anything permanently, right? So it shouldn't cause any problems with future bypasses or Microsoft's restrictions.
Nope, the /msioptions part just specifies a parameter for that one .exe file. It doesn't change any system settings or anything.
I don't have 4.8 so i need 4.7 with "vinzf" method. Plus (as usual) windows6.1-kb4552940-x64 (around 23,6 MB). Restart, KB556399 installed no longer pending in WU.