Deploying Win32 Apps that use scripts to install - first install takes forever

klenTAHNthanks for those pointers.  #1 certainly sounds like it might play into the issue - I'm surprised it doesn't seem to be more common of a problem if that's the case.  Would love to know if there's a way to confirm that in the logs and/or speed it up.  I do use the syntax in your #2 examples too.

Rudy_Ooms_MVPyes, it only happens the first time, and only when a script (CMD or powershell) is called for the install - all other scripts run without the long wait no matter how long after the first install or reboot. I can certainly access the appworkload log - could not find the company portal log (or it's logged under a different log file name/location and I'm not aware).

Our default Delivery Optimization policy sets our end-user PCs to "HTTP only, no peering (0)" mode for updates and to restrict download bandwidth (foreground and background) usage during business hours.  I am also playing with a few endpoints that use the DO settings recommended here.  So far, I haven't noticed a difference in that first endpoint script execution time under either policy.