The task in Win10 has always been an issue, but here is what it needs. The task is initially created for NETWORK SERVICE to run because 1709 broke the scheduler and it would only run multiple actions if a service account was used. When using a Win10 machine as a client, you will need to change the User to one that has access to the shared network folder. You will also need to save the password (whether logged on or not). I haven't had any double quote issues, it simply runs as it was created. Also, the task cannot have the -p option. It will fail if you try.