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.)
Have been a member & active user/follower since Feb 2020. Has worked mostly because of the time & skill of those making it possible for the "poor" Win7 users to stay updated after M$ kidnapped & sold for ransom the Patch Tuesday extended" updates. As a bonus removing tracking spyware elements of certain updates. All the thanks to them. I kept my copy of the proxy but don't anticipate needing it again. Good luck to all those POSReady 7 machines. I hear there are not that many left. ;>) As explained Win7, Win7 embedded & Win8 all use the same Core OS (6.1 I think). Targeted updates for 6.1 apply to all equally. A member of the team can provide answers for POSReady 7.
Respectfully, they are definitely not all the same Core OS - OS 6.1 is definitely Windows 7, OS 6.2 is Windows 8, OS 6.3 is Windows 8.1. It's a reverse engineering scripting matter (all the .INFs, .INIs and .CATs) for .DLL, .SYS etc. compatibility between them, but I say for now we've covered the distinct focus for Windows 7 security updating down the track so we can move onward (my post before was maybe too discrete hinting indirectly of caution about 'off topic' content.) Answers specifically for POSReady 7 mitigation are posted on another forum, and for now perhaps enough answers towards the eligibility means of updating it have been clarified a little more accurately. So we're all good.
No problem. Let me refer you to Comment #7104 by FuzzleSnuz Feb 23, 2023. Page 356 in this forum; 4 comments from top of page. Might be a good read for you & reading will not violate the off topic rule. A very necessary good rule I might add. Good luck.
WMC works well even on the latest Win 11 / Server 11, I don't think there are problems on any older Windows. This is a W7 thread, so YES WMC is a core application, but even if it wasn't I can't see the need of a harsh reply. Some people use the computers because the applications they use, not just to say "Hey ma! I'm fully updated"
I'm running Windows 7 Ultimate x86 (which possesses the WMC/MCE) with April 2023's SECURITY ONLY updates installed, and no issues thus far. Since February 2023 the security updates have mostly been about "improvements". I've mentioned beforehand that with Windows Embedded 7 Standard x86 updates I've yet to install a Security Monthly Quality Rollup, so I'm waiting for a month where there's visibly a load of important-to-critical listed patch-ups of multiple OS components.
Not meant to be harsh. Simply pointing out the lack of details needed to properly help them. If the wording seemed harsh I apologize. I now humbly bow out of this particular conversation & voice my appreciation for all the help available here for everyone. Thank you.
No luck for me this month! Bypass: BypassESU-v12_u.7z Rollup: windows6.1-kb5025279-x86_2a2e4d2cf10d42586099f5ad68543412e24f20e3.msu (Yes x86!) At first it seems to install, but then after the reboot it says "Failure configuring Windows updates. Reverting changes.". It was working fine last month (KB5023769). Any suggestions?
Updates can fail for other reasons than ESU, check logs in C:\Windows\Logs\CBS "Root Certificate Updates" has nothing to do with it
Anyone else has an nVidia GPU driver problem after using the latest bypass? Every time I try to install the 474.30-desktop-win8-win7-64bit-international-whql.exe update, the GPU breaks, shows as not installed, the system turns to using the mobo graphics. Have to revert to 474.11-desktop-win8-win7-64bit-international-whql.exe, then the GPU works fine as before.
win7-64bit Yes. Installed with glitches 474.30: - Missing Aero effect - Missing nVidia control panel. - In the Device Manager of the Video Adapter - it says that the driver does not have the required signature. It seems to me that bypassing the ESU has nothing to do with it, the cant is on the side of nVidia. I rolled back to 747.11 - everything is fine.