First of all: Great improvement over the last years and thanks for your hard work.
I am running my cron job nowadays every week, Wednesday early morning, and I am curious since 26th of march how your new version will solve the Win-10 choosing part.
Now I got 4 warnings for following command:
Command line: /files/wsusoffline/sh-new/download-updates.bash w100,w100-x64,o2k13-x64 deu,enu -includesp -includecpp -includedotnet
2020-04-01 02:01:29 - Warning: Windows 7 / Server 2008 R2 is no longer supported.
2020-04-01 02:01:31 - Warning: Option -includesp is not recognized.
2020-04-01 02:03:50 - Warning: The settings file w100-versions.ini was not found. Please install the utility "dialog" and use the script update-generator.bash to select your Windows 10 versions.
2020-04-01 02:08:09 - Warning: The settings file w100-versions.ini was not found. Please install the utility "dialog" and use the script update-generator.bash to select your Windows 10 versions.
1. the Win7 warning is nice, but in my case not necessary anymore (stopped the download in February)
2. nice reminder to change my cron script
3 and 4. this was not so easy
![Zwinkern ;-)](./images/smilies/icon_e_wink.gif)
first I was looking for a w100-version.ini...........not available...aha...I have to run the upgrade-generator.....no problem (i thought)....run-it, to choose the necessary parts and....say NO to run the script, because it was done a few hours before......
not a good choice: the new ini files are not written, the tmp directories are empty..........after running it again, everything is working and no warning anymore in the short run, because nothing is really done, due to the 24 hours rerun limit.
Now I have real questions:
1. why is the 1507 and 1607 win10 version chosen as standard? I thought they are out of service
2. what will happen, when the 2003 version will appear and i run the update only as command (see above)?
will you add them automatically to the ini? (I would prefer it this way)
Best regards
Mani