I did actually. Just completely forgot about it Anyway, I've downloaded the v6 bypass for now and will consider installing it when I feel like it.
I had to patch my BypassESU to v6 (then reboot) to get the updates to show in WU. Of course KB4556399 will still fail. As mentioned above its happening to a lot of people with ESU keys, so it will probably get fixed soon.
What caught my attention the most from the start is that the .NET Framework update is very small compared to all previous Microsoft uploads. As a general rule, other NET Framework updates were around 140MB, while the last one (giving error 643) is only 36.6MB. If this update is also giving installation issues to those who have official ESU licenses, it is possibly a Microsoft bug. I edit, because I was wrong. The method explained by @vinzf in post https://forums.mydigitallife.net/th...dates-eligibility.80606/page-150#post-1596124 on page 150 works perfectly. After successful execution, the pending update of the .NET Framework disappears from WU, which means that it is installed correctly.
I uninstalled the old .net 4.8 Lite AIO (KB4503548, KB4503575, KB4532941) that I made base on abbodie1406 & installed a new one (KB4503548, KB4503575, KB4552921). After rebooting & check WU, KB4556399 still showing/needed so I installed it w/out problem. I had the option to install or hide KB4556399 since KB4552921 was installed.
You're wrong. Microsoft mentioned on some of the update description pages that you may need to re-lock your ESU license (for those that have one) in order to maintain your access rights for the May ESU updates.
Ok girls, here is the solution: I've captured the custom action dll from NDP48-KB4552921.msp and analyzed it in IDA. The custom action dll exports a function ValidateESULicense which initially queries a msi property "ESU_LOCK" and compares it to several values that determine the further path of action. Long story short, if that value is "2D40812E-974C-4EA2-8DCC-63C992D505B9" the code path logs "ESU Validation is OFF", yay! So we can override that property via msiexec: msiexec /p PACKAGENAME.msp /log c:\tmp\log.txt ESU_LOCK=2D40812E-974C-4EA2-8DCC-63C992D505B9 Luckily also the ndp48-kb4552921 installer exe accepts msioptions for the embedded package it ships. So the final solution to get KB4556399 installed is: for x86: ndp48-kb4552921-x86_608b67e4011b9e103ca18deadbfc013d1c328508.exe /msioptions "ESU_LOCK=2D40812E-974C-4EA2-8DCC-63C992D505B9" for x64: ndp48-kb4552921-x64_6912af0422fc16a14f4f398fda98117f1e2f01b8.exe /msioptions "ESU_LOCK=2D40812E-974C-4EA2-8DCC-63C992D505B9" reboot as requested and go to windows updates which still believes that KB4556399 is not installed but quickly marks it as installed once you tell it to update.
What are you talking about? Microsoft does not sell the key to the private/final users like us, but only to the companies.
Excellent! Confirmed working for .NET Framework 4.7.2 as well - KB4552919. Same ESU_LOCK value. Note: The log file which is optional will be created only if the folder already exists.
@vinzf Thank you very much: the method you have explained works perfectly and the .NET Framework update is no longer pending in WU
@vinzf Thank you very much: the method you have explained works perfectly and the .NET Framework update is no longer pending in WU +1