Try this simple sequence in windows 11:
1. Close all active windows
2. Open CS and run profile.
3. Magnify the profile windows (so that is 100% at the top)
4. Connect virtual probe and run a quick built-in sequence.
5. Minimize the profile window
6. A pop-up will appears waiting for an ack. Ignore it, and maximize the minimized profile window.
6b. Click on the magnified window
7. Now you have lost CS control. You cannot minimize again and various windows key sequences are useless!

It is not so unrealistic, if, during CS work you run other windows on your PC (obliviously not suggested if you are doing a long characterisation, but there are other cases where you can accept then risk of a lost of real time).

How fixing: Open resource manager (ctrl-alt-del). Find the CS profile sub task, and minimize it by clicking the right mouse/keypad button

Cannot replicate, so going to need more specific detailed instructions.

Steve

Sorry ..... I have use the wrong thread. I wanted to post it in tips and trick. as I don't think it is a CS bug
Can you move it other there (or delete, in case I rewrite with more details)

If it can be replicated - it is possibly a bug.

Steve

OK.
I assume the profile window, when magnified, takes the all screen (at least that my case)
I have added step 6b, I had forgotten.

Still can't replicate...

Steve

I have a videorec to clarify
https://1drv.ms/v/s!Agrddzvyi1trgZIl0mdJUa3D7q-qwg?e=7O9hfC

Ok - you are deliberately 'shrinking' the profile window before the profiling finishes, and then recalling it back before clicking the po-up window.
Yeah - not really a ColourSpace bug.

Steve

Indeed it happens to me when doing LUT requiring time.

This has been complained about before (where you can find workarounds) to no avail:
https://www.lightillusion.com/forums/bugs-wibnis-21/problem-with-characterisation-modal-dialog-box-answered-1023.html

Yes, if you abuse standard Windows hierarchy you can causes such issues, based on the way ColourSpace uses floating windows.

Don't do that, is the simple answer.
As ebr9999 says, not a ColourSpace bug.

Steve