what about buying new hardware because your already perfectly working hardware is not compatible with newer OS ?
I wonder, why does a .NET Framework 4.8 also need the updates for .NET 3.5.1? Backward compatibility reasons? So far, the "Rollup for .NET Framework 3.5.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8" has always been downloaded to me via WU and the updates for 4.8 and 3.5.1 have been installed. Updates for .net 4.7 were not installed, only one older one (KB4019990...which file is included with every rollup!?) is installed since 2017 - but at that time maybe an older version was (also) installed. I will now continue to manually install the updates for 3.5.1 - but as I said, I would be interested in why the latter is required.
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
A question: now i tested the WSUS Proxy.. the datastore always has to be reset to search for updates ?, an old update from 2013 was found that I hidden, And when I register Add_wsus-only.cmd an error message appears immediately, I removed it again. Then Winupdate works again. If I search next month: Just let the Run_wsus.cmd and Winupdate search? On my other Win7 I installed the Bypass 12 and Net Bypass, then installed the missing SSU, now executed the add_wsus-and-reset_datastore.cmd, then the run_wsus.cmd (previously the Windows updates to never automatically, and lo and behold the netframeworks and the monthly security update were found and installed, then I closed the run_wsus.cmd, restart, everything ok. Now remove the netbypass due to Aboddi's warning. @abbodi and others: Must I always have the carry out add_wsus-and-reset_datastore.cmd before update, and what does add_wsus-only.cmd. On my other Win7 it was an Error by Searching Updates, when I carry out Add_Wsus-Only.cmd? I removed it again, then it went. I hope you can understand, i must use google Translator !
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?
Yes, reset is required for initial scan correct, going forward, you just need Run_wsus.cmd and search Windows Update
WSUS Proxy is detector, not installer ESU Supressor should be alway installed WU ESU Patcher do not interfere with WSUS Proxy, but it has no effect either Spoiler WU ESU Patcher is required with Run_wsus-Both.cmd
add_wsus-and-reset_datastore.cmd is only needed first time afterwards, you only need Run_wsus.cmd + Windows Update Add_wsus-only.cmd is for advanced users
Very good !!!! see my Post https://forums.mydigitallife.net/th...dates-eligibility.80606/page-352#post-1777502
Update History is only for updates installed from Windows Update, or using msu file you installed updates manually update history is not that important, Installed Updates is what matter https://forums.mydigitallife.net/posts/1777396/
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?