Well, the reason that I'm asking is that, from January up until now, I've been taking care of the ESUs the same way others here have: by manually downloading & installing them. So, what I'm asking the members of this forum is if it's worth it for those like me in Group A (the monthly rollup group) to switch from the way we've been taking care of the ESUs (manual download & install) to the new way via v5 of the bypass (getting the ESUs through Windows Update).
I'm guessing they don't fully install because Vista doesn't have certain Server components, like Hyper-V. At least from what I've observed, most critical OS components do get updated (from a brief analysis of the updated dll and exe files in various system folders).
I don't know if this is just coincidence but since running BypassESU v5 my laptop fan has stopped working. Has anyone else had the same issue? Probably not related but seems strange it happened just after running v5. Anyway I'll keep an eye on things.
Thank you guys,the V5 bypass is working perfectly on my Windows 2008 R2. At least i don't have to upgrade immediately and stay updated. Thanks again !
@craftech - I've started a thread in the W7 forum https://forums.mydigitallife.net/th...ventid-1542-and-others-broken-profiles.81210/ and requested moderators to move a list of "off-topic" stuff from here to there, let's give it some time to see if they move stuff so we can continue there without further cluttering up this thread!
@Bill_Boquet Nope, doesn't work. Still shows "Unsupported Hardware". Whenever I install both things (wufuc and Bypassv5) it just doesn't work. Wufuc modifies wuaueng and v5 creates additional dll. I don't know why can't both dlls be used at the same time as they use different names. It seems that Windows likes the v5 dll instead of the original (modified by wufuc). So if v5 isn't patched to support wufuc, I guess I'll just stick with manual install of updates. Edit: Oh Jesus, how stupid am I?! All I had to do was to reboot the system! I can now confirm that WU ESU Patcher from v5 is working with wufuc.
The BypassESU v5 uses the wuaueng.dll to create the wuaueng3.dll, so if the wuaueng.dll is already patched by wufuc, the wuaueng3.dll is also patched by wufuc. The system uses only one dll (the wuaueng3.dll if BypassESU v5 is installed).
Of course. I'm using W7 Ultime x64 with wufuc and the operative system and Windows Update work both properly since I've installed WU ESU Patcher from v.5.
great job, seems to be working. @abbodi1406 Concerning the LiveOS-Setup.cmd script, the variable _bat is set on line 30 and is then used on line 109. line 109 : 1>null 2>null %xSU% /c cmd.exe /c ""!_bat!" -su" &exit /b shouldn't it be this instead: 1>null 2>null %xSU% /c cmd.exe /c ""%_bat%" -su" &exit /b it would seem that with the <! > the variable is undefined whereas with < % > it is well defined.
Will the WU patch leave the current WU settings as they are, such as letting me choose what to download and what to update?
well, shall I report a bit odd stuff of using bypass v5 on fully updated win7 ult x64 including yet all ESUs of Feb2020 installed or I missed something smart? the bypass install CMD window didn't offer me 1st 2 options but the 3rd one only = [3] Install WU ESU Patcher {source file: wuaueng.dll} appreciate
oops. that was a point of my initial question when neither bypass v4 nor KB4528069-Lite installed but the genuine KB4528069! and also it was odd when after install that KB4528069 I was able to install all feb2020 esu patches w/o any glitch!
No, not just server-specific packages some components in the updates require client-type packages, but with higher version than the packages in Vista specifically: Code: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.0.6001.18000 this package version exist only in server 2008, vista has the RTM version 6.0.6000.16386 likewise Code: Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-us~6.0.6001.18000 this package version don't exist in vista (or server 2008) this accidentally caused issue in KB4474419-v3, and they had to fix in KB4474419-v4 -- @alorsnon !_bat! is delayed expansion variable, it's used to avoid issues if the file path contain special or unicode characters
ok. thanks 4 ur kind prompt. well, and what shall I do to make bypass v5 to be installed w/all options? remove KB4528069?