I Have solved it. The issue was to dual boot with linux i replaced windows boot manager with grub The Part that was failing to update was some boot component then I remembered I was using grub I removed grub and now it is working Perfectly Thanks!
Someone threw an old PC with "Windows 7 Embedded Standard (SP1)" at me, which recieved its last updates in 2014. It is sometimes still connected to the internet, according to the owner. He now "heard about" possible updates until 2023 and asked me about it. I never needed this great ESU bypass, but now I wonder... The "Win7 Embedded" system cant be freshly re-installed, as it has different, licensed, old software running on it. The installers/companies are either no longer existing or ask a lot of money for re-installation. There are backups and acronis clones exisiting. So, ready for experimenting. But where exactly would I start here using the ESU bypass, on a 2014 device ? Would it be enough letting it search for "old updates" first, then going for the ones from the TXT file ? And then finally run the ESU bypass itself ? Us beeing aware that this system and the installed software might get beyond instable, recieving more and more updates towards 2023, we agreed on giving it a try. Maybe someone here could hand me an advice, on how to start carefully with this desaster ?
You will need to get this Windows 7 Embedded SP1 PC up-to-date first with the official updates packages until 2020-01 (January 2020). Take a look at the forum link below, response # 11007: https://forums.mydigitallife.net/threads/windows-7-hotfix-repository.19461/page-551#post-1786496 The TXT file is a list of all the necessary security updates and update hotfixes packages necessary KBs (you will need to download and install these KB packages for Windows 7 Embedded Standard, yet check first to identify your Windows 7 OS whether you are running an x86 [32-bit] or x64 [64-bit] OS version of Windows 7 Embedded SP1). Install the updates in the order listed, and you won't run into too many issues. Just allow the installed packages some time to integrate their configurations before restarting (in other words, do NOT rush the process with installing too many packages at once, or restarting the computer too quickly after being prompted to restart). The objective here is first to ready your PC into a safer and stable OS state so you can use Windows Update to "Check For Updates" safely. Afterwards it will be getting your PC ready for ESU (Extended Security Updates). There is no faster way to complete this without corrupting your OS. But give the attachments a browse and you make up your mind to proceed.
@Ready_Slavik Thank you so much for the explanation and this detailed (long) knowledgebase list ! =D Its a x64 Windows 7 Embedded Standard SP1 (KB976932) and I will now start to slowly grab every single KB, one by one. Last KB on this system beeing (KB3011780) (Nov. 2014), I think I should not (yet) jump to *** AT THIS POINT, YOU MAY BE SAFE ENOUGH TO USE WINDOWS UPDATE TO CHECK FOR UPDATES IF YOU WISH *** But pick every 2015 KBs 1st ? (CPU, IE, etc.) and also that 2019 KB4490628 WU Servicing Stack Update, BEFORE going any further down in that list ?
1) That Security Update (KB3011780) will be necessary to install on your PC before going online on the internet to 'Check For Updates'. According to Microsoft Catalog, the next security update that supersedes/upgrades that patched component is during ESU in 2021-[02,03 - February or March 2021 Security Monthly Quality Rollup]. 2) You need to get your PC updated to at least March 2019. From this point onward, any security and update packages for Windows 7 SP1 will be SHA-2 Code Signing Supported (You will need KB4474419 installed to install security updates and update hotfixes packages from this point forwards). It will be at this point with all the prior listed Security Updates and Updates installed that you will have mitigated your PC against most of those Hardware CPU and Side Channel Memory Exploits from 2018 (known as Meltdown, Spectre, Foreshadow, etc) enough to safely use Windows Update to 'Check For Updates'. 3) Installing the WU Security Stack Update package (KB4490628) before the others is fine. This update will supersede all the previous WU Service Stack updates, and you need THIS one in order to install the KB4474419 package. Just don't install the KB4474419 package too early, else you may create a configuration mess with your OS DataStore database file (Afterwards It will require "sfc /scannow" and a few other remedies to stabilize it, but you will have a new long list of past components security updates that were misconfigured/corrupted to reinstall).
Thanks again, I feel much more encouraged to try now. Regarding the WU Patcher, would you recommend the one bundled in ByPassESU v12 or the stand-alone W7-WU-ESU-Patcher?
I am trying to integrate KB5022338, the final official rollup for Windows 7 Professional ESU. I ran the ESU Suppressor from BypassESU, then installed all the recommended updates first which all succeeded, then I attempted to install this rollup, which always seems to fail at the very end. I was wondering if I am doing something wrong here? For context, the WIM I'm using was released by Microsoft in 2018 and therefore has pretty much all the updates till that point. On top of that, I installed the SHA-1 update, the 2019-03 and 2022-09 servicing stacks, and the ESU prep update (KB4575903). Am I missing an update? I pasted the DISM output that I get. Let me know if you need any other info, I appreciate any help! --DISM output-- Processing 1 of 1 - Adding package C:\Users\[REDACTED]\Downloads\BypassESU-v12_u\windows6.1-kb5022338-x64_75d100c03bcaee4b62d08004cc382337ed09d327.msu [==========================100.0%========================= ] C:\Users\[REDACTED]\Downloads\BypassESU-v12_u\windows6.1-kb5022338-x64_75d100c03bcaee4b62d08004cc382337ed09d327.msu: An error occurred applying the Unattend.xml file from the .msu package. For more information, review the log file. Error: 0x80070005 Error: 5 Access is denied. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log