Firstly , many thanks to all the Devs , beta testers etc. I got an old laptop (Win 7 Enterprise x32) out the cupboard to test this. No updates of any type had been done for almost 12 months. Firstly, I updated it via WU , and got all the official updates installed that it would allow me to download and install. I then installed ESU bypass v5.0 + The patcher to get all future updates via WU (Option 1) I rebooted , expecting WU to prompt me to install all of the Feb 2020 updates. BUT it only made kb4537829 available for me to install (after forcing a recheck - the others from Feb 2020 did not show up. I was able to install them manually though (Apart from .KB4528069 which of course, was taken care of by the v5.0 ESU bypass).. and everything installed correctly after a reboot.. I am not complaining or anything , just interested to know why WU did not make them available , when it did kb4537829?. Surely if the patcher was not working , then WU would have not offered me kb4537829. Or am I totally misunderstanding this? Thank in advance...
Did you install the ESU Licensing Preparation update (kb4538483), needed for WU to offer the updates, after the bypass was installed? Afaik, the 2020-02 SSU (kb4537829) is not an ESU checking update, it's offered when all other Important and optional updates are installed by WU. EDIT: the feb 2020 ssu is not offered when the bypass + wu patcher didn't run, i got it offered when i ran the bypass + wu patcher but didn't install the ESU license prep. update (kb4538483), and only after wu was satisfied (except the lp's) and a reboot. Probably because it is not an actual ESU update, it got offered without kb4538483. When installed kb4538483 after this, the 2020-02 rollup is offered.
@Enthousiast No, I did not , I MANUALLY added it afterwards.. I guess that must be it. My fault that I should have read the tutorial more closely. I guess the fact that it did offer me kb4537829 , means that its the type of update that is offered to everyone? , regardless of if you have the WU Patch or bypass installed. Thanks for your time. I have a few more machines to do for my neighbours , and this will really help me...
Got it to install successfully on my desktop, however on my laptop I am getting the following errors when trying to run the automated installer and selecting option 1: Error: 3 The system cannot find the path specified. The DISM log file can be found at C:\windows\logs\dism\dism.log Failed installing KB4528069 package. restart the system and try again. Press any key to exit I've tried rebooting but same result. I had installed all available windows updates previously so the prerequisite packages are present.
If this is helpful, the Error entries and activity immediately prior from the DSIM.log are here: 2020-02-25 21:26:11, Info DISM DISM Package Manager: PID=2900 Attempting install from source location [%configsetroot%\Windows6.1-KB4528069-x64.cab]. Full path [C:\Windows\ConfigSetRoot\Windows6.1-KB4528069-x64.cab]. - CPackageManagerUnattendHandler::Internal_InstallPackageFromSource 2020-02-25 21:26:11, Error DISM DISM Package Manager: PID=2900 Incorrect parameter C:\Windows\ConfigSetRoot\Windows6.1-KB4528069-x64.cab - path not found - CDISMPackageManager::Internal_CreatePackageByPath(hr:0x80070003) EDIT: I manually created the above folder and put the cab in it and everything installed successfully.
Are these two cabs inside the bin folder? Code: 0e28e79b0caa45d5d2c03a0cd034625b46546725 *Windows6.1-KB4528069-x64.cab 858c83f333f6ca0d57d0d506960c68335ff63337 *Windows6.1-KB4528069-x86.cab
Yes they are there. Sorry for false alarm, see my post above yours. For whatever reason a subdirectory it was trying to find in c:\windows was missing so I manually created it.
I have Windows 7 family Premium x64 KB4528069 installed with BypassESU V4 on 01/27/20 ok BypassESU V4 uninstalled on 02/14/20 and KB4537820 installed manually ok (i am waiting for KB4537829) BypassESU V5 AIO installed today , option 3 Install WU ESU Patcher ok KB4538483 manually installed ok check WU offered updates KB4524752 ?! (for W7 PRO) haha ok I hide the update after offer ESU updates via WU KB4537829 WOOW ! yes it works thank you again for your work, you are great , let's go to Mars.. sorry i'm french, my english is bad.
Glad that all worked out eventually I am learning to code, i can only find these lines about the failing update in the Live installer script: Code: echo. ^<assemblyIdentity name="Package_for_KB4528069" version="6.1.1.1" language="neutral" processorArchitecture="%xPA%" publicKeyToken="31bf3856ad364e35" /^> echo. ^<source location="%%configsetroot%%\Windows6.1-KB4528069-%xOS%.cab" /^> Somewhere @abbodi1406 set that folder as sourcefolder, i can't find it atm, hoping he will clear this up
Yeah on this system the 'configsetroot' source location was pointing to c:\windows\configsetroot\ instead of the bin folder for the update package that was part of the download.
Well, I followed the directions in the first post concerning installing v5 of the bypass: installed the licensing prep pkg, then ran the LiveOS version of the installer (selecting the Windows Update patcher option, since I already had the test update, a.k.a. ESU Suppressor, installed; of course, the WU patcher option was the only option that showed up for me, since I already had the suppressor installed). Afterwards, I ran Windows Update & only one update showed up; the EOL notification update for Windows 7 Professional. I figured I didn't need that since I had already gotten the EOL notify thing for Windows 7 Home Premium (the version of Windows 7 that's on the computer I use), so I hid the EOL notify for Win7 Pro update. Then, ran WU again, and nothing showed up the second time. So, I suppose I'll find out if the install of v5 of the bypass was truly successful by if March's SSU & the March monthly rollup show up in WU on the second Tuesday of next month.
@rylan @Enthousiast Normally, %configsetroot% variable should be exist or set globally on Win 7 unless Win 7 was installed with autounattend.xml that used that option (and even then, it should have been cleaned after installation) so anyway, it's side-effect
Hi to all, I just got 83 updates yesterday after installing v4 the week before. I'm hoping that's a good thing...?
Bypass v4 doesn't affect WU. So you shouldn't have any ESU updates from Windows Update unless you use the newer v5. These 84 updates are probably the security updates (or rollups) that you missed throughout the previous months back when Windows 7 was still supported from Microsoft.
Hi, I've already installed KB4528069 and successfully used ESU Bypass v4. I had all pre-requisites installed and I followed the tutorial for ESU Bypass v5 by Enthousiast. I rebooted, checked WU, and nothing was offered. I stopped wuauservice and deleted "C:\Windows\SoftwareDistribution", and I was offered 6 new updates! Thank you very much to all the devs and people who are helping for this amazing tool! I've been following this thread since its creation and I' ve been trying to read every trouble-shooting comment, but it's hard to read through every comment, so I'm sorry if this was already asked: in order to get new future updates, is net necessary to stop wuauservice and delete the SoftwareDistribution folder every time you want to check WU?
No, it was not even needed this time, a simple reboot was the first option to do, if then still no ESU updates appeared on WU, reset WU was the next option, and that is only needed one time.