Your Deployment is unlogic:
Your first Step is a file copy to "C:\Windows10" but your second step starts the Install from the "Repository" and not the local c:/windows10/ folder, this makes the firs step unnecessary. The second step also includes the files from entire directory, this way you copy all files two times, a waste of time.
The thirs step "Reboot" is unnecessary too, because the upgrade includes all necessary reboots as long as you don't use the /NoReboot parameter for the setup.
The Win 10 Upgrade doesn't need a extra file copy to the local drive, the upgrade process allready includes this an can be launched from the share directly.
All you need is one single cmd Step:
\path_to_win_10_setup\setup.exe /auto upgrade /migratedrivers all /ShowOOBE none /Compat IgnoreWarning /Telemetry Disable /DynamicUpdate disable
I'm not sure about your /quiet parameter, he exist but i never used him for a upgrade.
Keep in mind, you can not upgrade x86 Version with a x64 Version and vice versa.
If you use a image including both versions, you have to start the right setup.exe from the x86 or x64 folder (\path_to_win_10_setup\x86\setup.exe or \path_to_win_10_setup\x64\setup.exe) and not the one from the root folder. Create a step for each O/S architecture and set the exclusions to the O/S architecture under the condition tab to be sure you start the right deployment.
For more details, take a look here:
PDQ Win 10 Upgrade