Enthousiast, did you get a chance to test? Does the install order matter between Wufuc and Bypass-v5?
All I am using now is the windows security essentials antivirus on W7. Disabled it same thing happens. Is Security essentials causing it?
As you can see, I am not Enthusiast, but I advise you to install wufuc first and then, after rebooting, continue installing Bypass-v5.0. All of us who have previously installed wufuc have been able to install Bypass-v5.0 afterwards without any problems. On the contrary, the operating system could prevent previous WU updates that do not even need to have Bypassv5.0 installed yet. Get all (necessary) critical updates first and when you have them, install Bypass
Thanks for your input, I understand installing Wufuc then Bypass-v5 works. But I want to know if there are any issues installing Bypass v5 first, then Wufuc second. Call it a curiosity Which is why I asked Enthousiast because he said he would test that scenario.
In my case it was a proprietary snapshot solution that I use to test stuff. You can do anything you want and when done just revert to snapshot - so this was a first, the snapshot mechanism actually prevented the v5 script from running until I disabled it.
Just been offered this, is it safe to instal. Sure i'd done all the feb updates already and was only offered security updates earlier... 2020-02 Servicing Stack Update for Windows 7 for x64-based Systems (KB4537829)
When you are on v5 or Lite or v4 (and used v4 as instructed), it's safe to install and needed to be able to install the next (march) updates.
I have a local WSUS server (Server 2008 R2) and clients (Win7 enterprise). All machines have the prerequisites of Bypass V5 installed. Bypass V5 is installed on all machines (WSUS server and clients) in mode 1 (Full Installation). SoftwareDistribution directory has been deleted and wuauserv run again. The WSUS server actually found the Feb ESU Updates (4537813, 4537829, 4537767 and 4537820) needed for itself and they can be approved. However, for the Win7 enterprise client none of the Feb ESU Updates are detected to be needed. But checking the Updates view on the WSUS server they appear to be known also for Win7 x86 and Win7 x64. So the catalogue on the WSUS server seems to be up to date. WindowsUpdate.log on the client doesn't reveal any errors. Simple question: Should this setup (Win7 enterprise being updated by local WSUS on 2008R2 with V5 Bypass installed) work at all? Or does it only work with M$ WU or manual install?
@unimbecil Did you approved and installed KB4538483 for Win7? the ESU Detectoids are the same between WU and WSUS, so it should work for both
Updates approved in WSUS does not mean they will appear on the client. You can see that with W10 clients, after eos, they will not find any new update even the updates are approved on the WSUS. Did you see the updates on the clients, if you search for them online? (Rename Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate to WindowsUpdate1 restart wuauserv service check for updates, rename WindowsUpdate1 back to WindowsUpdate restart wuauserv service)
> Did you approved and installed KB4538483 for Win7? Yep. Approved and installed (just checked again in the update history page) on both: WSUS and client...
> For WSUS on 2008R2 KB4484071 is needed. Had been installed on the WSUS box and on the clients in June 2019 > Did you see the updates on the clients, if you search for them online? Just tried. No, it finds only: - a very old Update for IE11 (2014) - Win Malicious Software removal tool Feb 2018 - Win Malicious Software removal tool Feb 2020 and a bunch of optional crap like language packs and drivers. But none of the ESUs of Feb 2020. Maybe I should de- and reinstall Bypass V5 again?
Added offline integration instructions to the official tutorial: https://forums.mydigitallife.net/posts/1578167/