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??
Yes, as long as ESU detection metadata does not change (you would know that if ESU updates no longer detected) but even if that occur, you can just reset DataStore and run WSUS Proxy initial scan again
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)
What clickable link is being talked about without running the proxy? The link from WU doesn't work for me without the proxy running.
hello abboddi1406, thank you for your fast answer. tried this first. but on my win7 32bit VM I get this error: WARNING: PopulateDataStore failed: 0x8007000e (ERROR_OUTOFMEMORY). Is RAM meant? Can't increase, it's already 4GB. Trying to increase Pagefile...
hello abboddi1406, no more ERROR_OUTOFMEMORY now. But still: 0x80248014 in MSE Upgrade. Started from scratch, meaning: datastore reset and script Run_wsus-Both.
So, in the notes on Page 1, it says:: "Important Notice about the .NET 4 ESU Bypass it has incompatibility issue and may cause MSI or other programs to stop working therefore, it's recommended to install it only when new .NET 4 updates are available, then remove it after installing the updates" Does this mean to remove it after the .NET 4 updates are installed BEFORE rebooting, or to do the reboot so as the complete the install and THEN remove it?? Thanks
Just remove it after the updates are installed or don't use it at all but use the separate .net esu updates installer.
The one says: "Check online for updates from Windows Update" under "Managed by your system administrator" did you ran WSUS Proxy initial scan first?
I appreciate your answer, but it is confusing. I have ALREADY "Installed" the update, but have not as yet rebooted. My question what constitutes "installed??" Does that word mean the "install" is complete after the reboot/restart, or before??
Yes, built new datastore and then Installed the Feb updates.. The 4.8 .Net (5022509) via .msi first and then the 2 offered updates KB5022872 & KB5022731 via WU. I just tried the link you mentioned and it did not give me an error. Neither does the other link now, but if I logoff and logon and launch WU, I get the screen below and then the error using the upper left search link. The only link that works each time so far is the one you mentioned.
Yes, that's exactly how the Alternative method woks: Check online for updates from Windows Update = WSUS Proxy not needed Check for updates = WSUS Proxy needed the second option is better, since updates are released once a month generally
Yep, the guy who replied to you earlier didn't actually read your question. I'll give you a better answer. From Feb 2022 through Jan 2023, I used the v11 bypass like this: - On Update Tuesday, boot up my PC - Run LiveOS-Setup.cmd and install the .NET 4 bypass - (Re)check for updates in Windows Update to ensure it finds everything, including the monthly .NET Framework rollup (if Microsoft released one for the month, which they sometimes skip) - Install all updates, including the .NET Framework rollup - Reboot PC - Run LiveOS-Setup.cmd and un-install the .NET 4 bypass. Leave PC running, no need to reboot a second time. - Continue to leave .NET 4 bypass uninstalled until the next Update Tuesday This procedure has worked for me without issue every single time. I have used the same procedure with the v12 bypass without issue as well. The effects of installing/uninstalling the .NET bypass seem to be immediate, which is backed up by the manner in which it works. Since Windows updates often require a reboot and may sit suspended in a queue until said reboot is performed, my intuition says to reboot first, then remove the .NET bypass. It has always worked for me. Edit: Fixed typo with two steps out of order