I'm not well-versed in automating things on Windows. I know the concepts around Task Scheduler, PowerShell, batch files, and the like, but if I try to use these tools, I know I'll end up in some forum ...

If the powershell.exe process running the script is using next to 0% CPU, you're likely blocked on a command-line program waiting for input from the user. Also, you can run it in powershell_isa.exe ...

The GUI is fine if you're only moving a few files, but for larger and more complex migrations, this built-in Windows utility is the way to go. There are many ways to get a file from Point A to Point B ...