You should Run_wsus.cmd + Windows Update first, before "Check online for updates from Windows Update" your log look very normal and as expected
Thanks for the suggestion @abbodi1406, that's what I did in my first attempt. I did the exercise again with Run_wsus-Both.cmd in administrator mode, then Windows Update first, then "Check online for updates from Windows Update" : no luck :-(. Thanks anyhow for the tip, cheers, Bill
How do I know if KB5023820 (the out of band update NetFrame 4.7.2 / 2023-02-17) is an optional update ?? If so, I won't download and install it. Who can advise me ?
For everyone lost in the details , here is what I did in a nutshell : I was using @abbodi1406 script v9 till 2023-01 as you had the choice to either use v9 or v11 All my windows 7 installations were updated up to 2023-01 from 2023-02 going forward, there shall be no more updates showing in windows update Now you have to install v12 script to be able to install new .net framework updates you have 3 ways to obtain updates now, windows update catalog, or simplix tool by @Enthousiast , or uses WSUS proxy If you use windows update catalog, there is no new Windows 7 updates, instead there will be updates for windows 7 embedded which are 100% compatible with Windows 7 Simplix tool is already using latest Abbodi script & search for everything in the right direction for you, it literally let you "Sit back & relax" while it does everything for you automatically if you use WSUS proxy, things goes as follows : first read readme, it will tell you to install "Microsoft Visual C++ v14 Redistributable (x64)" & links to that are included & some other updates that are prerequisites .. then you set windows update to never check for updates .. then run "Add_wsus-and-Reset_DataStore" which will reset windows update database .. after it finishes .. you run "Run_wsus" & give it network access Now you check for updates from the link on the left in windows update screen (the one under "Control panel home" link) initial scan will be slow & you will see activity in the black screen of "Run_wsus" Sometimes first scan doesn't work so repeat it one more time if things go on in the right direction you should get windows embedded updates showing which will be 2, one rollup for windows & one for .net framework if updates older than 2023-02 show just hide them, you shouldn't install updates using WSUS proxy before 2023-02 after you install February updates you have 2 options afterwards .. either you run "Run_wsus" every time you open windows update & click the link on the left hand-side .. or don't run "Run_wsus" & use the link below "managed by you system administrator" Hope this is helpful for every one & Huge thanks for @abbodi1406 , @Enthousiast , @whatever127 & @mspaintmsi
Oh boy, of course... that explains why it always installed the updates for version 3.5.1. I forgot - silly me. Thanks for reminding.
@eric cabrol : in the OP (Opening Post), under "WSUS Proxy for Windows 7 to detect ESU updates after 2023-01"
I'm not getting what is going on with you .. I'm guessing you are a little bit confused .. but "run_wsus" is one of the batch files found inside WSUS proxy folder & if you are asking where is WSUS proxy ? .. then as @Bill_Boquet mentioned its link is "in the OP (Opening Post), under "WSUS Proxy for Windows 7 to detect ESU updates after 2023-01""
Has anyone successfully been able to upgrade to 10 on a windows 7 machine that has been getting the bypass updates?
It's only a small annoyance, but why does a New updates are available alert appear in the taskbar after using BypassESU-v12 and after manually installing these February 2023 updates? They're all old updates, and I've already hidden about 60 of them. About half of them are associated with NET Framework.
I read the topic, and still do not understand completely, we orients to October 2023 (eos for emvedded standard 7), or can we expect to install updates until 2024 (POSReady 7)?