I just want to say a big thank you to the author of these tools. Yesterday I've read a lot of pages and then I've applied the tools. Everything was perfect Thanks as well to all the people who wrote advices and info. A guy from Italy
abbodi1406 Hi, I do not understand what the problem is. I installed ByPassESU-v12 and then Patcher with point "1" on your recommendation, but updates for 2023 and still not find it through the Windows Update Center.
abbodi1406 Yes, both updates are installed in the system and after applying the patch I naturally rebooted the computer. This is what I have installed: 2023-01 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB5022338) Installation date: 11.01.2023 6:52
This means the patch is not applied or working correctly try to remove it, then apply it again or try option [2] for Server
Is LiveOS-Setup.cmd (v12) supposed to work in a VM (Win7 + Updates from 01)? I ran it as admin, but it just flashed the cmd prompt, so I changed it to /k to try and get some info. I don't see any output. I was expecting a window wirh Choose a menu option: Code: X:\$W7\$0_KUC\ESU_All\BypassESU-v12\bin>whoami /USER | find /i "S-1-5-18" 1>nul && (goto :Begin ) || ( if defined _elv goto :E_TI net start TrustedInstaller 1>nul 2>nul superUser32.exe /c cmd.exe /k ""!_bat!" -su" 1>nul 2>nul & exit /b ) . . . '"X:\$W7\$0_KUC\ESU_All\BypassESU-v12\LiveOS-Setup.cmd"' is not recognized as an internal or external command, operable program or batch file. X:\$W7\$0_KUC\ESU_All\BypassESU-v12\bin>
If you open up a COMMAND PROMPT window as an Administrator then execute the CMD file, it should be fine.
@adric your path contains a dollar sign, that is not even a possibility in Windows because it is a special character for MFT metadata files. Extract the files to a simple folder like C:\BypassESU like the readme says and try again
running superUser32.exe only adding /v option gives: Not sure if that's an additional problem not related to LiveOS-Setup.cmd not running
an internal tool from where I used to work that I've used for ages on DOS/Windows. 32-bit only. No problems running with it on a native W7 64-bit system.
Many, many thanks abbodi1406. Just manually installed Security Only KB5023759 Win7 Embedded Standard (x64) using ESU Bypass v.12 and no problems. Question:- last month there were .NET4.8 updates;- ndp48 KB5022509 (x64) (.NET Rollup Win7 Embedded) ndp48 KB5023823 (x64) (OOB update) They installed fine....but I just noticed that in Control Panel all 16 of my .NET4.8 updates show the installed date as the same i.e.22nd Feb 2023. It may be coincidence , but I made a full image of my system that day 22nd Feb using Macrium Reflect. Any ideas? Thanks again. Edit:- I remember trying to install one or two of the other ndp4 updates...maybe that was my bad??
Moin @ All! My March 2023 ESUpdate experience for Windows 7 Pro SP1 x64 systems: "Licensing method": KB4528069 & "new" BypassESU-v12 "Installing method": Manual download and installation via Microsoft®Update-Catalog KB5023759 (Security Only Quality Update for Windows Embedded 7 Standard / Windows Server 2008 R2 SP1) -> succesfully installed @ abbodi1406: Thx for your support! Great job! Addendum: The following additional updates were offered by the Microsoft servers via the Windows Update Search and were also successfully installed: KB5024670 (.NET 6.0.15 Security Update for x64 Client) & Security Intelligence-Update for Microsoft Security Essentials.
The thread needed some cleaning. === @Jay K To reiterate, we have a dedicated discussion thread for 0patch, so kindly stick with it. Comparing apples with oranges makes no sense.