I used the same read-only status script after rebuilding our laptop and got an argument error immediately. The old machine still runs it. There are several SDK folders on both, so same script is beginning to sound like only half an explanation.
What would you compare before changing the call?
Compare what actually imports on each laptop, using the normal way you launch the script. Module path, interpreter and callable signature first. Folder names can tell a very confident story about a library you never loaded.
The rebuilt shortcut launches a different interpreter from the terminal. I had checked the terminal and assumed the shortcut matched. Have not captured the imported module from that shortcut yet.
Maya's right about the launch route. Get the comparison from the failing route before editing the arguments, otherwise you might make the script fit the accidental SDK and break the supported one.
Maya, our training technician owns it. He found the shortcut importing an older copied SDK from its working folder, while the old laptop uses the documented installation.
Yes. Technician aligned the launcher with the documented environment and ran the agreed read-only check from that shortcut. It returns the expected controller identity now. No argument changes to the script were needed.
Nice, an actual explanation as well as a working laptop. Put that launch-path check in the rebuild handover while the accidental copy is still fresh in everybody's memory.