The old laptop runs our read-only FR10 check. The rebuilt one rejects an argument before connecting, using the same script. I found several SDK folders and a shortcut whose working directory nobody recorded. I'd rather identify the imported copy than reinstall everything and lose the clue.
Have the script report its interpreter path and imported module path from the normal shortcut on each laptop. Keep the exact argument error beside the failing configuration. Does the working copy have a recorded version or dependency list?
Ask the software maintainer to identify the intended supported version and compare the call against its documentation. Finding the different copy explains a useful difference, but it does not decide which version your handover should preserve.
The maintainer has the script and both imported paths. She is checking the original deployment notes before choosing the environment. The rebuilt laptop still fails; no claim that locating the folder fixed it.
Include the agreed launcher settings and dependency versions in the eventual rebuild instructions, then verify through that normal shortcut. The next person should not have to repeat the directory investigation.