yes, nothing i can do i would have to implement powershell commands to adjust cmd window buffer you can change Defaults command prompt buffer before running the script, make Height 3000 or more or start admin cmd, then change the current window size Code: mode con lines=3000 then run the script in the same window
Regarding Windows7 update lists, i will continue add new extended security updates, they will be added in sub-catalog "Security\ESU" however, i still not decided how to handle the updates which will be superseded by ESU updates most of them will likely be the old ones that are already superseded by ConvenienceRollupKB3125574 should i keep superseded updates in their place? or move them to "Additional\WithoutESU" ? or should i move updates in main categories (security, general, hotfix)only, and keep the old ones under "Extra\WithoutKB3125574? any suggestions are appreciated p.s. February rollup KB4537820 supersede 3 old hotfixes 2763342, 2796725, 3014783
yes, same one will continue Spoiler Code: ================================================================= 2020/02/18: Notice: From now on, all new updates are Extended Security Updates. All will be added under "Security\ESU" category, unless specified otherwise. Added: 4537820 4537829 4538483
Hi abbodi, I'd say the snapshot approach would be wiser (atm): "Security\ESU" > OK, containing 4537820 (Feb20RU), 4537829 (Feb20SSU), 4538483 (?) "Additional\WithoutESU" > OK, containing (fixed list) 4534310 (Jan20RU), 4536952 (Jan20SSU), 4539602 (WPNoStretch fix) "Additional\WithoutESU\WithoutKB3125574", containing (as of Feb20) 2763342, 2796725, 3014783 (as you found), and moved from "Extra\WithoutKB3125574" to this folder as future ESUs supersede them. Guess a WHD-W7UI update should be required as well...
Yeah, i will update the script soon i'm actually thinking to keep superseded Extra\WithoutKB3125574 inplace, for the time being at least if i decided to move them, then to "Extra\WithoutKB3125574\WithoutESU"
Don't be upset, but after some thinking, i decided to move superseded updates (in main categories) to "Security\WithoutESU" this way, both "ESU" and "WithoutESU" will be aside and easily distinguished, and will make easy for me to handle WithoutKB3125574 updates will be kept in their place for now, the change log will mark them as superseded for info + https://forums.mydigitallife.net/threads/abbodi1406s-batch-scripts-repo.74197/page-52#post-1579713
Never upset by you, friend. Bit late now, but in fact, after reading your reply, I was going to suggest that the most consistent rearrangement with your work so far would be simply using "Extra\WithoutESU" and "Extra\WithoutKB3125574\WithoutESU". Seems that not using the latter has not caused troubles to the WithoutKB3125574 CMD update (like having to hard code the superseded ones to skip if using ESUs), but anyway, mi two cents.
In most cases that means that some settings are not set correctly. Can you post a screenshot or the content of the cmd window?