The rebuilt laptop doesn't like our identity script

Our FR5 identity-recording script works on the old laptop. On the rebuilt one it rejects a keyword before any controller connection. Same script file, different Python setup. There are three SDK folders on the old machine. No note says which one is active. I would like to identify the working import and interpreter before changing the call. Has anyone untangled this without destroying the only working setup?