@rpo is talking about the open source replacement for wub.exe that isn't included in any version of the script yet but planned to hopefully be in the next version 2.6.1. Since one of the end goals is for the script to be 100% open source, an open source alternative for wub.exe is in development to eventually be used in the script. Sledgehammer 2.6.0 is working fine.
1903 is only giving people a false sense of hope on controlling updates. I expect no less from Microsoft, and I doubt they'll ever give full control back.
MS-DEFCON can take a long time before answering and ping to ntp.org often fails. As the script is going to download ms updates, testing the connection to Microsoft.com is defensible. PS: the Test-NetConnection cmdlet, starting with Windows 8.1, offers TCP testing (only ping is available with Test-Connection).
I'll change it to microsoft.com then. I'm not impressed with cmd script's handling of testing an internet connection. If I ping an ip address, returned error codes are unreliable. If I ping a url, I get a reliable error code, but the ping can fail when it shouldn't have. So I'll check out powerscript's TCP testing. Thanks for the info.
My feedback: I've replaced 2.5.5 with 2.6.0 on two machines, and ping to pool.ntp.org failed on both today. So I think changing to microsoft.com will be a good move.
Ha-ha, I really should read changelogs more carefully. I spent quite a while wondering how MS had infiltrated my hard drive with Windows10Upgrade and rempl folders in spite of best efforts to prevent them. I took ownership and deleted them only to have them keep coming back. I forgot that they're dummies with good purpose.
Which option should I use if I want to re-enable Windows Update after using portable version and/or using Windows Store?
I'm not sure what you mean by "re-enable Windows Update after using portable version and/or using Windows Store". Windows Update is enabled when you use the store with the script. It has to be or the Store wouldn't work. I'm guessing you're not talking about pressing [E] in the script's Configurator to [E]nable Update Service temporarily to use Windows Store. If you mean permanently, you can uninstall the script. If you mean without running the script, you can enable it with wub.exe in the script's bin folder.
I'm working on a fix. I knew the unexpected folders would be a problem and would freak some people out when I did it. But I decided it's for the greater good.
Please note that while using directories and locking them, one can also use files of the exact same name. All MS filesystems in history, back to DOS and beyond, do not allow a file and a directory of the same name in one and the same place. As an old DOS user, I use files to block the directories. These files can be conveniently set to System+Hidden, making them Super-hidden and vanish, unless you are a power user and have showing of system files enabled. Setting the directories to Super-hidden would also work with your directories and make them vanish on over 99% of typical Windows installations.