JLink issue with stm32cubeprogrammer and JTAG locking

[A_Bit_More]

Hello!

I've was following this tutorial on Jtag locking for stm32h573RI using j-link. 
link to tutorial: How to enable RDP-like product state flash protect... - STMicroelectronics Community

I made it to the updating the product state to 17 and was in the process of reconnecting under hot plug mode, however I didn't have success reconnecting. 
I get these 4 errors: 

To Note: 
I was able to flash initially with no issues. 

I've been trying to update the jlink version on the stm32cubeprogrammer and have had no luck

I have updated my jlink version locally to 9.18v

Thank you for the any suggestions :D

[Kouthair]

Hello @A_Bit_More,

I have tried reproducing this behavior on my side, but I wasn't able to get those popups when reconnecting using Hot plug mode after setting the product state to 17.
Is it possible to provide more information (firmware version, J-Link used etc..) 
It is also important to note:

-Provisioning is not yet supported by J-link.

-The tutorial is made using ST-LINK.

[A_Bit_More]

Great to know, that J-link isn't supported for this example.

Replies to your questions: 
Firmware version for stm32cubeprogrammer V2.22
fw on the dev kit, it was just an example code toggling the led lights.
I tried both jlink and st-link for different boards.

More info: 
I was using a custom board and a dev kit.
The custom board only has swd connections, which is why I was using jlink.
This is where I was getting my errors above, it just won't connect anymore.

As for the dev kit, I was using the st-link to follow the example.
On the step to regress, my ST provisioning integrity status:0xf5f5f5f5
and I'm stuck on this step from the example. 
From what I was able to figure out my dev kit is locked and there is no way to get it out of this state, correct?
@Kouthair