@abbodi1406 You're welcome. It's not easy for you to insist on sharing the compiled patch list with everyone, and there will inevitably be errors. Even saints can make mistakes sometimes. Sorry, English is not my native language, so I used a Bing translation to reply.
Embedded patches can update the core system files (which are common across ALL the Windows 6.1.7601.xxxxx (ie. Windows 7 SP1) versions). For Embedded patch versions, just using the monthly "System Only Quality Update" is a safe bet using BypassESU v12. I've yet to try going for installing the monthly Security Monthly Quality Rollup (Unless a very important monthly security issue arises, I'll save installing the Rollup for the "very last release" announced for July 2023.) That is not to say that July 2023 will be the very end of Windows 7 support, as therein remains Windows Embedded POSReady 7 ESU support until October 2024 (and they may be getting their support from the "Windows Embedded 7 Standard" titled security updates.) Same deal applies mostly to Windows 8.1 x86 versions (in this case it is NOT ESU support), with exception to using W8-1ESUI v0.1 installer scripts for installing Windows Embedded 8.1 "security only" updates to Windows 8.1 x86 or x64 versions (also momentarily supported until July 2023, yet there's still Windows Embedded 8.1 Industry Pro & Enterprise support until October 2024.) The second exception, only with Windows 8.1 x64 versions there is currently a BypassESU-Blue-v1r version that provides support to mitigate ESU installing Windows Server 2012 R2 x64 security updates (including to install same updates to Windows 8.1 x64 versions.) At this time, the answer is up to you to decide whether making use of Windows Embedded security updates is a better substitute than nothing at all for your Windows 7, Windows 8 or Windows 8.1 PC machine(s) versions.
Hello all, I am rather new to this but am in need of a Working Windows 7 Pro system as up to date as possible for testing a piece of software for a long outstanding bug which still exists on windows 11 to try and identify the root cause. To that end I have my trusty Windows 7 x64 ISO I can't tell you much about it other than the fact it is labeled GSP1RMCPRXFRER_EN_DVD, I have figured out how to use NTLite in order to do the basics but I am not sure that I am slipstreaming the right stuff I am just following as close as possible a guide on doing these things and in fact I am not even sure if my version of the DVD can have your fixes applied to it to get the latest updates. Can someone please advise me on the procedure as I am currently drowning in MSU's and a lot of conflicting information. EDITED: I forgot to mention I saw somewhere that no one can get hold of : windows6.1-kb4528069-x64_b00bef3c3a13b8bc65bfaea63426386dbb54c336.msu I have it if anyone needs it.
1) Attached is a list I compiled for my own fast setups of Windows 7 Ultimate x86 or x64 (they also mostly apply to Windows 7 Pro). Follow this listing in this order and you're pretty much there. https://forums.mydigitallife.net/at...9/?temp_hash=c38493d9696c5be8dd04f0826298706c 2) The MS version update of KB4528069 has a reputation to fail installation. As BypassESU was in its development stages, a pre-requisite version of KB4528069 called 'KB4528069-lite' was released that can circumvent the failings in installation of this MS update. It also is hard to find, but take it from here. https://forums.mydigitallife.net/at...5/?temp_hash=8fdeafc31ee68ed5727e1cfc5b482697 Note: An updated "Windows 7 Updates List.txt" file was uploaded here on 11-05-2023.
For me, neither WU-Patcher nor the WSUS Proxy found 5026413 this time around. Worked fine last month and had no problems finding the April LCU. Not sure if this is a local problem though.
Win7 Pro (x64) ESU Bypass v.12.u I manually downloaded and installed KB5026426 Security Only Win7 Embedded Standard (x64) and KB5026366 Cumulative Security update for IE11. Win7 Embedded Standard (x64). Many thanks once again to all at MDL
Did you do a clean install with the April LCU already integrated in the .wim? This may have something to do with it. My Feb thru April LCU installs were based on a fully patched Dec. .wim which did not include any embedded LCUs or Bypass code like the one I did my April clean install with. WU found all the LCUs during the Feb-Mar-Apr Patch Tuesdays. I usually build a new wim after the Dec, April, Aug WU updates and clean install from there. I didn't have this problem doing the same thing for Win 8.1. Maybe abbodi1406 has an idea why this happens to some of us.
Mine was manually updated until feb 2023 -- KB5022872 (Bypass v11/v12 added to the WIM) MS windows 7 Ultimate SP1 X64 -- Updated 2023-02 After that i added the Win7_WU_ESU_Patcher script by abbodi1406 to this online system, and (online) updated from there... No problems there...So not sure about that.
No, I used Kurwica v.4 way back and continued using the subsequent Bypass versions without any serious problem.
Hmm... don't even know about Kurwica but will either try Simplix Pack OR BypassESU version by version (I have v7, 9, 11 & 12).