Vista (plz read the warnings in post #2) and Server 2008 SP2 are still on v5. Seems to be that even the separate Dotnet Bypass does only work on 7/2008 R2.
After downloading the bypassESU v7 and installing KB4566517, do I have to remove .net esu bypass (option 6) by returning to LiveOS set up or can I keep this configuration? thanks
Thank you so much for your reply! I was hoping that maybe someone knew of way to get the .Net packages installed, as v5 was pre bypass, and you're right that the v7 bypass will only work on 7/2008 R2. Luckily, the other updates install like a charm, thanks to the heads up from @abbodi1406 in post #2 without any kind of bypass as long as they're downloaded manually Hopefully someone finds a trick or the .Net bypass become available for Vista/2008 at some point!
Iirc, the dotnet esu bypass can cause problems with installing other (office) stuff, but i am not 100% uptodate on that subject.
Carlos probably meant the standalone dotnet esu bypass: https://forums.mydigitallife.net/th...dates-eligibility.80606/page-157#post-1596682 https://forums.mydigitallife.net/th...dates-eligibility.80606/page-159#post-1596752
I will see if i can create .NET 4 hook for NT 6.0 although from briefly analyzing ESUEngine.dll, it check if the system is Server 2008 i'm not sure if it can be bypassed to allow installation on Vista in the meantime, you can create update administrative installation for .NET 4, if you know how it auto-bypass the ESU validation, then you can uninstall .NET / reinstall the update pack BTW, what's the latest .NET version that can be installed on Vista? 4.6 or 4.7?
Will definitely play around with this, thank you so much @Enthousiast! @abbodi1406, you're the best, thank you for the info! I believe it's 4.6, and if there's anything you can do, that would be amazing, but if not, I completely understand and appreciate you trying! All of you on this forum have been incredible resources, so thank you all!
ok thank you for the answer I will remove it and submit it to the next framework update. From what @ abbodi1406 says it seems better
This just helped me, I forgot this older laptop was still on a 32-bit version of windows and I had downloaded the 64. Using the correct version fixed my issue as well.
.NET 4.x ESU Bypass https://forums.mydigitallife.net/posts/1596946/ added bypass package for Vista/Server 2008
Just wanted to thank you guys for all the work you do to make updates possible. Just installed v7 to get the next .Net update and it worked great. I was wondering if v7 would also install June's .Net update if you hadn't followed the shortcut method mentioned last month?
Since ESU_FLAG/LOCK procedure has been removed, does July .NET updates still require .NET bypass? Can Bypass-v5 by itself install July .NET updates?
The override flags have been removed, they cannot be used to manually install the .NET packages, anymore. You now need to enable the DotNET option in BypassESU v7 temporarily while installing DotNET updates. Bypass v5/v6 together with the separate DotNET Bypass tool should also work.
I followed your instructions for creating the slim. I used dotNetFx.cmd and it created Code: netfx_Full.mzz 227621516 netfx_Full_x64.msi 2134016 netfx_Full_x86.msi 1355776 I then ran 7zSFX.cmd which created Code: ndp48-Slim-x86-x64-ENU.exe Your command is launching an individual msi. Running the Slim which includes 4565636 at SetupComplete won't work will it? Do I just need to add the reg entry? I'm confused
Either will work at SetupComplete.cmd (ndp48-Slim-x86-x64-ENU.exe /ai or start /w netfx_Full_x64.msi /qn /norestart) Setup_NDP48.cmd is mainly to install the updated .NET 4.8 pack on already installed OS with older .NET 4.8 installed because it need to uninstall the old pack (msiexec.exe /X) before installing the new one (start /wait netfx_Full_%arch%.msi) the two reg keys commands are cosmetic, not needed at all