From what I understand, v9 is still good to go for the time being. I will test the latest and greatest v10 this coming weekend.
Thanks very much again. Checked the winsxs folder. It is huge: 15,6 GB, 89.000 files in 22.000 folders !!! Takes explorer several minuetes to display it all !! A lot of amd64... folders, msil... folders, wow64... folders, x86... folders. Also the temp folder, with 2 subfolders: pending deletes and peding renames. All of these empty !! All this seems very stange to me, why the enormous number of files in winsxs ? Could this be the cause of my boot-delays ? When expolrer spends several minuetes going through this, could not this also affect the boot ? Looking forward to hearing form you.
@abbodi1406 Is it necessary to update the BypassESU for Server 2008? It's been a while since v5 was released.
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.