Sorry, I will pay attention to it later. And by the way, that is wrong link, it is 110 in fact. The correct 109.0.5414.129 link can be find in here.
I have a question of understanding: Are the Windows Embedded Standard 7 updates compatible with Windows 7 Ultimate? Has this been tested? If I understand correctly, is the "WSUS Proxy for Windows 7" a way to continue receiving updates? Because I had read a few posts, does Microsoft Essential Security still work? I currently receive updates daily with it. I thanked you already, maybe someone can enlighten me. (p.s. thanks for the help and the forum over the years)
stop asking this question .. embedded update same as normal windows 7 update embedded are only price change !
Yes they are compatible and install fine. I have them installed on 2 W7 Ultimate machines and on 1 Pro. No issues.
I did not know that. Thank you for your answer. Do you know anything about MES? It seems that I am no longer running it? Could that be? That sounds good!
WSUS Proxy is to receive the updates online, instead of installing manually from the MU Catalog. And yes MSE still works.
I had also understood that, I was just not quite sure whether these updates are also compatible for Windows 7 Ultimate and Pro (and with MES).
Read: NB: MSE has absolutely nothing to do with the Windows monthly rollup updates. You are only receiving definition updates for MSE through Windows Update because you have enrolled in Microsoft Update. Microsoft Update uses the Windows Update client to provide updates for other Microsoft products, such as MSE, Visual Studio, etc. Do not confuse the two. This is a strange thing to ask. You already know that you are receiving definition updates daily through it, so there is no question that the definitions are out of date. If you open MSE, you will see a bright green check mark and many other positive indications that indicate that MSE is working without issue. These are the same indicators that MSE is working without issue which have been present and unchanged in the application for the last 10+ years. And if this is still not good enough for you, you can very easily download a fake test "virus" from the large number of security organizations that provide these test files for free, and watch as MSE dutifully identifies it as a virus and locks it away in the quarantine. Questions and answers are one of the pillars of forums, but laziness is not. Please put some effort into finding the answer yourself, especially before asking superfluous questions with answers that can easily be found in just a few minutes. This thread is about Windows 7 ESU and it so frequently gets bogged down by off-topic things like this... making it harder for the rest of us to actually stay up-to-date on the ESU-related matters.
This answer was really unnecessary. I am referring to a statement here in the forum where MSE no longer works (possibly due to the updates). There is no reason to directly denigrate my question. Post: https://forums.mydigitallife.net/th...dates-eligibility.80606/page-353#post-1777714
For the first time since I started to use the Bypass in February 2020 for installing Windows 7 ESU updates I had trouble installing this month’s .NET 4.8 update(KB5022509). Every time I tried I got error 1603 (0x643) when using either the dotNetFx4_ESU_Installer_u or using BypassESU-v12_u. This happened on 4 of my systems. After some debugging I discovered that the 0patch agent was to blame. I had installed 0patch in July 2022 in case I had to use their patches starting February 2023. I never had any problem with 0patch before. After uninstalling 0patch KB5022509 installed fine. I used the dotNetFx4_ESU_Installer_u and have not tried BypassESU-v12_u. I would assume the issue of not being able to install the .NET 4.8 update using the Bypass is also solved, because it threw the same error. Note: 0patch has to be uninstalled entirely. Stopping the service, ending the 0patchservice process or simply disabling the 0patch agent does not solve the problem, only uninstalling 0patch does.