MIDI remote script of manually added controller will be not saved

I’ve added a simple pedal Nektar NX-P as a remote MIDI controller. Created the surface, mapped the CC, and the Focus QC7 functionality. All worked fine.

On the next start, the device disappeared. I tried to add the surface script, but no such thing was saved on the machine. So I’ve created a new one. Then, I exported the script as a “.midiremote” one. At the next start of Cubase, the device was also gone, but the exported script was saved. I’ve tried to import it, but it failed without an explanation of why.
So I added a new NX-P again, set it up, and so on. This time, I tried to edit the surface by clicking on the pen button showing up on the controller surface, where all remote controllers are shown. It opened like this:

I went back and double-clicked the controller to go to the edit page again. This worked fine:

It looks like Cubase tries to open the surface editor via script if I click the pen button, but it opens it in another way if double-clicking on the controller surface, where all can be seen.

Conclusion: Although the surface script is listed in the MIDI Remote Manager - Scripts, including the path where it is supposed to be saved, it does not exist. Therefore, the export process exports something broken, and if Cubase 15 (Version 15.0.10) Build 164 (Intel) tries to open the surface editor via a script, it fails, and, naturally, it cannot be opened on the next start.

Update: The script was actually saved on the fifth attempt to create a new controller. But that makes it even stranger. :thinking: