Did it stop working? will do the new .NET 4 Bypass concept can work for Server 2008 too but Vista require the old one (Dll Injection), because we need to hook GetProductInfo & VerifyVersionInfoW from kernel32.dll
A million thanks to abbodi1406 and friends, not just for v.10 of this great tool but also for the clear detailed instructions on how to use it. I've been using it since the beginning and haven't had any problems using it. Thanks again guys, very much appreciated!!
if you didn't expand my post, just have a look at my 1st post https://forums.mydigitallife.net/th...dates-eligibility.80606/page-248#post-1635302 thx
WU ESU patcher does not seem to work on WES7? Even if I install the necessary updates, I still can't get the ESU updates.
Hello abbodi bypass v10 works fine for ,Net ESU updates and Office installation, but it breaks all other MSI files! (WIM integration).
abbodi1406, hi. I checked v10 on the "naked " original windows 7 - everything works. ... When enabled .Net 4 ESU Bypass does not allow you to install Kaspersky anti-virus. If Kaspersky was installed before .Net 4 ESU Bypass its operation is not disrupted (databases and software modules are updated without problems).
Hmm, this is so weird... I came here to find out if any problems were being reported in relation to MSI installers and the latest V10 script. Not because I have any particular reason to think it's the script causing this, but because I was running out of options to figure out what could be causing the issue. In my case, I performed a sysprep and capture of an updated Win7 Pro x64 image using the script & ESU updates. Now, some msi installers work fine. But both the old Classic Shell as well as the latest Open-Shell installers (they have msi's inside the exe wrapper) are refusing to install and are giving me error code 1946 and not being able to register dll's. I thought perhaps somehow my sysprep image got messed up and was about the make it again. I just thought I'd check this thread in case someone else is having these issues, to then see this post by aquilotto. EDIT: I just ran V10 and uninstalled both ESU bypass and .NET bypass, and after reboot I was able to install Open-Shell! I then installed ESU bypass again, rebooted, and I could still install the msi. I then enabled .NET bypass and rebooted, after which I could NOT install the .msi. (Just checked: no reboot required, disabling .NET bypass makes it so I can use the msi installer successfully right away.) Like I said above, it's not doing this with all .msi's, but these are tried and true installers I've used many times so there is something going on in relation to the .NET bypass. I did not have this issue previously with Win7 Enterprise images I made via sysprep, using V9 of the bypass. (Since this is a sysprep scenario I of course used the LiveOS-Setup.cmd option, FYI.) I'm guessing one could just enable the bypasses in time of updating, and then disable .NET bypass in the mean times, as a temp workaround.
That's exactly what you had to do with v9 when you had these MSI installer issues... sounds like the same problem with slightly different issues
So this is a known, then. Well, I made several images using V9 and had not encountered this issue, using the same Open-Shell installers. 7-Zip .msi's and Firefox .msi's installed fine though, strangely. When you said, "That's exactly what you had to do" do you mean one had to disable the bypass to use certain .msi installers and then turn the bypass back on afterwards? EDIT: That's what I'll do. I will just disable the entire script before sysprep finalize & capture and just use the script when checking for updates. I don't ever have WU on automatic anyway, it's only manual checks. It was just not having encountered issues with V9 that I didn't think it would be an issue to leave the bypasses enabled at all times.
@abbodi1406 WUFUC, Nitro Pro 8, Araxis Merge 2014 and XML Notepad can't be installed; Firefox 78.6.0esr.msi works fine. After uninstalling .NET bypass (option 6) all works fine.
# Bypass ESU for Server 2008 (and Vista) - Updated ESU Suppressor (to align with the same one as Windows 7) - Implemented and updated .NET 4 ESU Bypass - Removed Prerequisite updates requirement (they're still recommended to install first) - Dropped Wim-Integration.cmd script (does not seem very useful for Vista)
I install the version 10 and all seems ok, but since few months, Windows Update doesn't find the updates anymore... From what is that coming ? I installed the Bypass since the version 5 or 6, and all was working fine (WinUpdate etc.. )
Please show the "update history" and "installed updates" windows and what does the bypass show when you run ESU Bypass v10 "LiveOS-Setup.cmd"? Did you check the Troubleshooter Q&A?
Maybe a bit off-topic but if not here then where? MS still allows Win7 users to "upgrade" to Win10 for free. On the other hand it looks like they still employ dozens or hundreds of people whose sole job purpose it is to make it more difficult for Win7 users to use the ESU's for free. Is it about the money (income from ESU payers) or is it just another attempt to force everybody to use Win10? Any thoughts or knowledge on that? PS: That actually reminds me of the days when game developers used way too much human and budget ressources to implement copy protections which only lasted about 1 day to 1 week, instead of using the ressources to release a perfectly working product without bugs...
Officially only businesses will be eligible for ESU licenses, there are some areas in the world where the licenses will be sold to anyone. Win 10 makes money from the profiling when using the store apps but probably most money is made in the cloud (online services). Officially HWID's generated after the 1 year free offer are not considered 100% legit (who cares, msft doesn't).