New laptop rejects an argument before the FR10 gets involved

There are three folders called SDK. Newest wasn't the working one. How do I compare them sensibly?

Get the loaded file path and interpreter path from each laptop, then look up the arguments that copy expects for your call.

Try Robin's shortcut check first, the editor can pick its own Python and make this even more confusing.

Yes, normal shortcut works there. New machine's shortcut launches a different interpreter from the editor.

Write both launch arrangements down before fixing anything. It saves a lot of confusion when someone later says they tested the same script and got another answer.

Which SDK file does each of those launch methods actually load? Could still be the same copy despite using different Python installs.

Our trainer once tested the editor run and handed us a broken desktop button. Please include the button in the final check; that's the thing evening shift will use.

Both new launch methods load the new SDK. The working laptop loads a copy beside its application.

That gives you something concrete to preserve. Does the application folder include release notes or a manifest explaining which copy was supplied?

Don't just delete the argument to shut the error up, find what that call expects in each copy first.

Found a release note. Working copy documents the argument; new copy's matching method has a different signature.

Will you restore the known setup or update the application? I need that distinction in our own handover when a laptop gets replaced.

Is the copied old folder approved for that controller, or merely the one that works?

Support confirmed the old release matches our approved setup. We're restoring that environment for now.

Write down that exact version so the next rebuild uses it too, and give the newer SDK its own upgrade job instead of sneaking it in.

Include where the verified package came from. A folder called 'working final' is surprisingly unhelpful to the person rebuilding your next laptop.

And try the workshop login, not just the administrator account used to install it. Our shortcut problem only showed up for the ordinary operator.

Workshop login and desktop shortcut both pass the read-only check. Package source and version are now recorded. Thank you.