via Windows Update: KB4556399 (.NET)=FAIL KB890830 (Malicious Software Removal Tool) = Succcess. KB455836 (Monthly Quality Rollup) = Succcess. ------------------------------------------------------------------------- Outside Windows Update: KB52921 (.NET)=FAIL KB4503575 (.NET)= Succcess. KB4538483 (Security Update) = Succcess. KB4555449 (Security Update) = Succcess.
KB4556399 is not available as a full downloadable patch. Therefore KB4556399 might be really a new MS "blunder"... In addition, KB 4556399, shown as 60 Mb in Windows Update screenshot, instead after the "failed" installation becomes 36 Mb. It is very strange.
Has anyone tried to install the KB4556403 (.NET Security Only)? This provides our WSUS and also the MS Update Catalog.
I saw a report from earlier saying it doesn't work. Same problem. Different program, same mechanism. Non-OS components aren't patched by the OP's ESU bypass.
I can confirm the .NET update installed succesfully on one of my machines without any .NET 4.x version installed. (Normal Windows 7, not Embedded version). On another machine with .NET 4.6.1 installed, it failed. However on a third machine without any .NET 4.x, it failed too, so maybe having any .NET 4.x installed is not the deciding factor.
Simply, I can't reach the page where it is possible the download of KB4556399. Microsoft Update Catalog gives me Error. Anyway, it doesn't matter. Many thanks
I've installed this month's updates, including a very small one going by the name of KB4557900 (which is just a timezone change for Morocco). I didn't bother with the .NET Framework update because I've had hassle with these kind of updates in the past (even though the last one I installed was from January). However, I'm really thinking about upgrading my bypass to v6 because I'm getting really impatient of updates being searched through for half an hour, then again for another update, and the cycle repeats. I'll think about it though for the time being. Just wanted to vent.
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.