For me also, it eventually worked. But since I dislike deactivating Antivirus, after full uninstall / reboot / full install ByPass v7 / Reboot, I tried once more with antivirus active => same error 641 But with Avast deactivated, it woked ! So I'm not sure it was really useful to fully uninstall Bypass then fully reinstall it. I think more that the key point is to deactivate Avast. But what is important is that at the end, it worked ! Thanks to everybody for advices.... and see you next month !
I also use Avast, it's probably because of this. Then uninstalling and reinstalling the bypass is not required. ....see you next month !
You shouldn't have to go into safe mode to delete the software distribution folder. Just make sure Windows Update is stopped and preferably disabled. Also stop trusted installer from a command prompt: net stop /y trustedinstaller
Try Code: /MSIOPTIONS "ESU_FLAG=2D40812E-974C-4EA2-8DCC-63C992D505B9 ESU_LOCK=2D40812E-974C-4EA2-8DCC-63C992D505B9"
It took awhile, but I finally got all six computers updated. For the first time since the Bypass fun began, I had to more or less go through a different procedure on every machine, although they're essentially all set up the same (four are Lenovo, two are HP). I won't bore you with the details because I'm sure no one else is in my situation. However, I can say to anyone who's having issues, even though it requires a bit of reading and (for me at least - I'm 73 years old) a lot of concentration, in my experience, if you go through this giant thread, at one point or another, you'll find the solution you're looking for. As several people have suggested, it would be nice if one of the moderators (are there moderators for this thread?) would go though and get rid of posts - like this one - that really don't contain any hands-on-solution-type information. I won't hold my breath. Anyway, I'll end this by again thanking everyone who's made it possible for us "little people" to be able to continue using Windows 7. Great job folks!
The MSIOPTIONS keys do not work anymore for me. What DID finally work was installing the ESU DotNET Bypass from ESU Bypass v7. Then, it installed without issues. The keys are either ignored or have been changed.
KB4565539(SecOnly), KB4565479(IE), KB4565612(.NET3.5), and KB4565524(RollUp) : Success KB4565636(.NET4.8) : Failed It looks like ESUEngine.dll 4.8.4181 ignore "ESU_FLAG" and "ESU_LOCK" arguments.
Try uninstalling ESU Bypass and ESU Dotnet 4 Bypass (if installed) and then install both again. Then, try again. That was the only thing that finally worked.
I installed ESU DotNET Bypass and I still had problems with NET framework 4.8 update. Windows installer was crashing, but after disabling Avast shields everything went fine. I believe the culprit is a new Ransomware shield.
The "ESU_FLAG/ESU_LOCK" procedure had been removed completely from this month updates originally, it was intended to identify WES/POS/FES embedded systems, but the came up with different way to check/validate those
I believe i got the dotnet updates figured out (with a little help from @abbodi1406 of course ) Win 7 ESU Bypass Updates Overview July 14. 2020: https://forums.mydigitallife.net/th...dates-eligibility.80606/page-184#post-1607440
Well, thankfully, I'm one of the lucky ones, as after I got the monthly rollup & .NET update first, then the SSU second, they all installed without problem. So, here's looking forward to a problem-less August ESU.