Bypass Windows 7 Extended Security Updates Eligibility

No problems so far

 

I always have done that for years, is more reliable. @abbodi1406 Do you know if M$ will soon invent a blocking method, or will give some years more for Win7?
Thank you for your great work.

 

If I am correct, here is what I know:
.Net frameworks updated independently, i.e. if you update 3.5.1 it doesn't mean that 4.7.1 for example would get updated too, they are independent entities
More over you don't have to have every .net framework installed on your machine
You only install whatever .net framework needed by you to run a certain program
There are tools available online that tells you which .net frameworks are installed in your system
But there is one last point , windows 7 comes with .net frameworks : 1.0, 1.1, 2.0, 3.0 and 3.5 preloaded out of box, that is when you finish installing windows 7 you don't have to install these .net frameworks

So your mentioned rollup for .net framework tries to update "whatever" .net framework it finds on your PC, if it finds only one of them it will update it, if it finds 2 it will update both .. & so on

 

On 15.02., I used BypassESU-v8-AIO to manually update KB5022872 without any problems. And for .NET Framework KB5022731, I followed the dotNetFx4_ESU_Installer_u instructions, loaded the ndpKB5022509.exe file and installed. But it doesn't show up in the update history , only in installed updates! Now I don't know if it installed correctly. I looked at the 2022-12 .NET Framework update KB5021091, in the update history it shows as KB5021091, but in the installed updates it shows as KB5020879.

 

What does this line in the wsus proxy readme mean?

============
if you are using external tool, make sure to select "Windows Server Update Services" for Update service
============

I feel like I followed the instructions -

Win7 Home premium 64 - updated via v11 thru last month
- V12 is installed and running including .net bypass (should this be running along w/proxy?)

Ran WU first and installed the malicious ...

Ran db reset

Ran wsus proxy and unblock php

Ran WU (no important updates)

Obviously I'm doing something wrong, but not sure what


Thanks

 

I have an existential dilemma... Is it necessary to uninstall ByPass ESU v.12 or is it compatible to install the new automatic installer for Windows Embedded Standard 7 without deleting ByPass ESU?

 

Does WSUS Proxy work when using a real WSUS server to distribute updates to W7 clients? If not, can it be added in a future release?

 

You can run Windows 10 22H2 with few tweaks on most if not all old hardware.
With some effort you could run Windows 11 too, but this is not necessary because Windows 10 22H2 has finally become stable and sort of final after so many years.
Or run one of the supported LTSB versions 1507/1607 if you need a more like Windows 7 experience.

 

WSUS Proxy works, great. One question, not entirely sure on the procedure "## Alternative method after initial scan... Going forward, you can keep using the clickable link without running WSUS Proxy. " Does this mean we can now use the clickable link every time, without running anything else from WSUS beforehand?

 

On Feb 17th, added to the Catalog is this::

2023-02 Update for .NET Framework 4.8 for Windows Embedded Standard 7 for x64 (KB5023823) 9.7 MB

But on Feb 14, there is this::

2023-02 Security and Quality Rollup for .NET Framework 4.8 for Windows Embedded Standard 7 for x64 (KB5022509) 42.2 MB

Should I install both of these or just the smaller update (KB5023823) 9.7 MB.

Very confusing.

Also in regards to .NET Framework 4.8 again, should I install the Security and Quality Rollup, or the Security only??

 

Both. 5023823 is an out-of-band update which came out after 5022509

 

WSUS Proxy works great.
But it seems no longer be possible to update security patterns in MSE. Or is this only me?
Code: 0x80248014 (WU_E_DS_UNKNOWNSERVICE)