@francesfarmer, I had a look at the screenshot in your link, but the quality was so blurry I couldn't read details. Hopefully one of the other better qualified members can help more.
Guys, if you just download from catalog.update.microsoft.com and install without ByPass v12 and ESU Patcher, will it install?
No. If that was true, then the bypass tool wouldn't exist, this thread wouldn't exist, and none of us would even be here talking about it. Read the OP.
April Patch Tuesday v12 & ESU bypass worked flawlessly for me on my Acer 64 bit Win7 Home Premium laptop. WU Gave me both options again (embedded 7 x64 & Server 2008 R2). I hide the 2008 R2 & update with the embedded 7 AFTER turning my security software off. Restart, And the hidden 2008 R2 disappears. No .NET updates this time or last. WU is continuously providing security updates between Patch Tuesday updates. THANKS to entire team for keeping our systems alive & well beyond the MS "kill" dates.
Yes, that will happen, but it is often due to pre-conditions set out in the .MSU installer and there are possible ways around that. For starters, the necessary ESU MAK Licensing Update packages should be installed (including the recent one). An alternative to BypassESU v12 is the Installer script W7ESUI v0.4 (which you can make use of in conjunction with 7-Zip, and if you have downloaded the .MSU package you do not need to be online so momentarily isolate your internet connection). Unpack the W7ESUI folder somewhere close to the C:\ drive or D:\ drive prefix (eg. C:\W7ESUI\ or D:\W7ESUI). Copy into this folder the .MSU file that you wish to install on your PC (process these file installations one at a time, because one of the .CAB files uses a common filename yet it is unclear whether that .CAB file is tailored solely for that update. Don't take the risk of unpacking multiple updates inside this folder in the hopes that this common named .CAB file is the same used in the other "extract"ed .MSU packages.) Use 7-Zip to "extract here" the 4 files inside that .MSU package (2 x .CAB, 1x .XML, 1x .TXT). Once done, delete the .MSU file from that folder. As a helpful monitoring of this process, open the Windows Task Manager (CTRL+ALT+DEL once, then select the very bottom option "Start Task Manager") => Press the "Show processes from all users" button. Now, "run as administrator" the W7ESUI.CMD script. If you followed the directions above about placing this folder near C:\ or D:\ drive, then you should be set to start. Press "0" to begin, else press "9" to exit. When the installation completes, you will hear a chime that your system is ready to restart. As you observe on the Task Manager, you will see the process "TrustedInstaller.exe" use up the CPU resources constantly. This may continue for 10-15 minutes until the "System Idle Process" task has CPU resources again at a constant 99%. You can safely restart your PC system now (all necessary pre-restart configurations have been completed). You may observe the restart process for your own leisure. The configurations should proceed into restarting. Once the pre-logon wallpaper appears the post-installation configurations may continue until achieving 100%. Even after the desktop reloads, you still best wait until the post-installation configurations complete another 10-15 minutes (you may reopen the Windows Task Manager to monitor this progress). It is important that you let Windows complete this process, as a misconfigured OS can occur when impatience is a factor (it will cost you time later to repair these instabilities). Once completed, remember to re-enable your internet connection.
Thanks for the response. If all goes well and POSReady7 updates can be applied to Win 7 that would make it's final EOL one year shy of Win 10 EOL POSReady 7 - Oct 8, 2024 Win 10 - Oct 14, 2025
This is not accurate. People seem fixated on POSReady 7, despite the fact that it is a reduced NT 6.1 OS and it and its updates may or may not have parity with full NT 6.1 OSes like 7 and 2008 R2. Afaik this remains to be seen. Also Bugcrash 10 will live far longer than that, sadly. The much more interesting and viable path is Premium Assurance. This offering from 2017 guarantees that Microsoft will be updating NT 6 until at least January 2026, for clients with on-premises Server 2008 and R2 boxes. We have already seen ESU license keys for Year 4, Year 5, and Year 6. This is the second half of ESU (Premium Assurance was quietly renamed to ESU in 2018). By way of Server 2008 R2 being a supported target for Years 4-6, Windows 7 is thus also a "supported" target for Years 4-6. We are already obtaining Year 4 through the catalog without issue, but Years 5 and 6 may be different. Will M$ continue to publish MSUs on the catalog for easily downloading and installation? Or will they personally drive someone with a CD book to every client in an effort to prevent those MSUs from leaking online? The answer might be somewhere in the middle. The correct thing to say is: if all goes well and we can obtain Years 5 and 6 of Premium Assurance, then that would make the real End of (M$) Support date for all SKUs of NT 6.1 (Windows 7, Server 2008 R2, WES7, POSReady 7, etc) be at least January 2026, which now surpasses retail Bugcrash 10's October 2025 date. (And on a sidenote, you cannot disregard the fact that Oct 2025 is retail only. Bugcrash 10 has hundreds of SKUs, some of which carry support agreements into at least 2029.)
I am pretty sure that using embedded 7 standard for our Win7x64 updates takes us to Oct 2024. At least that is what I just read in the notes I copied when I first downloaded the Proxy, v12 & the new Bypass ESU. They have been working real well 4 me following the instructions. Not sure why POSReady 7 is needed if embedded standard Win7 is doing the exact same thing up to Oct 2024. I used the Proxy method for the Feb 2023 updates including dotNET Framework. After which I installed v12 & BypassESU for March & April updates through the normal WU. The option I use gives me updates for embedded Win7 standard & 2008 R2. I hide the 2008 R2 & then update, restart & 2008 R2 disappears after updating with embedded Win7 std. I also continue to receive the security updates between Update Tuesdays. Smooth as a baby's behind. Much thanks to the team & the Good Lord.
You can try to zoom in, my screenshot is untouched so it's a 2048x1152 file ! because my monitor has this crazy resolution ! ohh... and the screenshot is in french !! I don't understand why WU offers quality update + .net6 and not security and nothing at all if I choose embedded 7! cropped image h t t p s ://ibb.co/PMVg4Ck after the updates : h t t p s ://ibb.co/d0NzMNP Funny thing : on another PC, I have a w 10 LTSC 2021 iot (to get updates until january 2032 with an interface as close as possible to W7, but I will use Windows 7 as long as I can because everything is better) and the update failed !!! so I'm up to date on W7 but not on W10 !!!
Sorry francisfarmer, I'm not much help with your problem. I hope one of the more expert guys who read your post will be able to answer the puzzle.
Take a look at this forum post #7292 and the replies below it (this is when using the standalone WU ESU Patcher for Windows 7): https://forums.mydigitallife.net/th...dates-eligibility.80606/page-365#post-1784093 Without cleaning out/resetting the DataStore.edb file, even when choosing for Embedded updates at first you will receive security updates for Windows Server 2008 R2 only. You will need to reopen the WU ESU Patcher and select updates for Windows Server 2008 R2 first, execute the choice and exit the program. Then, reopen it again and select updates for Windows 7 Embedded again. Without cleaning out/resetting the DataStore.edb, you will get this issue. Yet, when cleaning up/resetting the DataStore.edb file you may lose the details as to your Windows Update installation history (all the security updates and hotfix updates, etc.) I've not reached this stage, as I chose not to clean up/reset my DataStore.edb file - when this happens, maybe the System Update Readiness Tool [KB947821-v34] released in October 2014 can rebuild that update history listing before using Windows Update to search for new security updates. For this, I do not receive alerts to available Security Updates, yet I'm diligent enough to hunt them all down online on Microsoft Update Catalog. One last thing, it has always been common since the release of Security Monthly Quality Rollups that Windows Update will demand that THESE security updates are higher priority than the Security Only Quality Update versions for that month. You would need to manually search for these updates online on the Microsoft Update Catalog and download those update packages. On a month-by-month basis they are demarcated with a YYYY-MM prefix (eg. 2023-04 is April 2023 security updates). For Windows Embedded 7 Standard, enter the search details like this: 2023-04 7 .These will bring up those security updates that involve a "7" for Windows 7. Lastly, for Windows 10 if you are having issues with updating Windows, take a look at my post #7311 here for the common reasons and solutions 1 & 2: https://forums.mydigitallife.net/th...dates-eligibility.80606/page-366#post-1784697 As a solution 3, this is something commonly experienced with Windows 8.1 versions possibly within 4-6 months of continuous use. You'll have to use DISM to repair errors with some prior installed components using the commands as follows: (Open a Command Prompt window with "Run As Administrator" privileges, and you NEED TO BE ONLINE for this process) 1st attempt: dism /online /Cleanup-Image /StartComponentCleanup ** This process may take 1-12 hours pending on your computer's hardware specifications ** 2nd attempt: dism /online /Cleanup-Image /RestoreHealth ** This process may take 60-90 minutes at most ** After both attempts are completed, close the Command Prompt window. Now try again to update that Windows 10 computer with Windows Update. I don't use a Windows 10 computer, but I do still use a Windows 8.1 version currently supported with Embedded x86 security updates. Good luck.
Under BypassESU, I'd like to note that for both this April's update tuesday and also last March's, I was not offered .NET Core 6 updates through the WU client. This in contrast to Feb and earlier, where WU has always offered .NET Core 3, 5, and 6 updates for the last 5 years on my Se7en machines. I don't have any gripes about manually downloading and installing .NET Core (it's a good way to force me to stay current with news on the updates, i.e. watching Core 7 closely to see if they break NT 6 compatibility), but I am surprised that the WU client no longer offers updates for Core. I can't imagine that WU on real Server 2008 R2 boxes are not offered Core updates, so perhaps this is just a side effect of the ESU bypass tools? I am ofc using the "Win7_WU_ESU_Patcher" project. But I have chosen the Server 2008 R2 only option, since I don't want to deal with hiding duplicate updates and Server has a more prospective future than WES7. I'm curious if anyone else has the same experience as me. I should also note that my Microsoft Update enrollment is working and not the issue, since the WU client continues to offer the deluge of MSE definition updates.
Thanks very much for your help, I did that, we'll see next month ! all the update history is gone... I can't belive I missed this post from a few days ago !! For W10 : nevermind, it's just a test for the day it's impossbile to use w7 ! I will probably reinstall anyway
Has been for a while now. It is getting to be a pain reading all things not connected to this subject.
Attempting to read up on this with MS POSReady updates page sources, (you may be right) Windows Embedded POSReady 7 likely gets updated using the monthly Windows Embedded 7 Standard security updates - this applies even before ESU was proposed. There aren't really many POSReady 7 updates to find on Microsoft Update Catalog, same with Microsoft Downloads. When you may find a Windows Embedded 7 Standard security update on Microsoft Update Catalog in November 2023, it's just a question whether the pre-condition script settings for supported OS 7 versions on the .MSU update package will be altered to only support installing to Windows Embedded POSReady 7 after October 2023 until October 2024. Yet, using the available W7ESUI v0.4 or higher method (with the "extracted" content packages from that .MSU update package) may dodge those installation hassles. Else, when there is a new BypassESU with updated scripting to mitigate both the .MSU update package and the latest WU Servicing Stack Update package for permitting installing the update(s) (pray that it does not involve manually changing registry settings for ProductID, InstallationType, and ProductName). Best stay on track with the ESU bypass installing updates eligibility and W7 WU ESU Patcher (Windows Update) issues (+ suggested working alternates like WSUS Proxy, etc.)