Warning: Don't deploy Win10 Creators/Feature Update as a "patch" (as suggested by ME)

After giving the world enough time to iron-out any bugs that might've existed with updating corporate workstations to 2017 Fall Creators Update v1709, we decided to go ahead and roll it out, following this guidance: https://www.manageengine.com/products/desktop-central/windows10-feature-packs.html

I created a policy that allowed users to delay ("skip") the Update for a max of 2 days, with the maximum of 10 retries. Five days later, our user-base is raw from the pop-ups that just won't stop, even if they'd allowed the "patch" to process.

In looking through the DCPATCHMGMT.LOG files, we keep seeing where the process is trying to run the *.iso (see link above) as an executable:

[INFO] getISwitch : iswitch for patchid : 104980 is /passive /quiet /norestart !!!
[INFO] execute : Executing Application Source : 104980-Win10_1709_enx64.iso /passive /quiet /norestart
[INFO] execute : Failed to Create the Process for the application
[ERROR] Error Code : 193 , Error Message : %1 is not a valid Win32 application.

We are now following a (hitherto unknown to me) different method, also suggested by ME:
https://www.manageengine.com/products/desktop-central/deploy-windows-10-how-to.html

Basically you:
1) Extract the *.iso to a share with Everyone (or whatever you use) permissions
2) Call setup.exe with the following command line:

\\<sharename>\<foldername>\setup.exe /auto upgrade
add the following switches as desired
/quiet
/DynamicUpdate [disable or enable - "enable" greatly extends the length of time]