MY CPT records convert to Post on their own

Just now: screenshot how to my CPT looks after self-conversion

Really hard to say at the moment.

Was this happening before or after the 1.10.0 update? Trying to first nail down if something from the 1.10.0 release could be contributing here.

Are you able to recreate on a non-public website? If yes, then it’d be possible to reduce down to just CPTUI and perhaps one of the default WordPress themes to see if it still occurs. If yes, then something is definitely up. If not, then you could re-activate other plugins in use until the issue comes back. Once it does, we know the probable source of conflict.

I worked on Tuesday, and no any troubles with this CPT. I got free day yesterday. I had troubles with Search Results template (looking answers at Elementor Pro and on the forums) and  I started today from Elementor & Search Results decisions. 
Then I updated some plugins (and CPT UI also).
Then I click on the ‘Solve problem’ link near Elementor (on the plugins page), because I thought it will affect on Elementor & its support only (I never use this functionality ‘Solve problem’ before). I clicked back (browser) and switch off 'Solve problem' mode. 
CPT UI show me 'need update' again, I click on it but get warning that I have fresh version.  

After it I started attempts to roll back my site from backups, but nothing.

My biggest questions/concerns, at least from the point of view of potential needed support for CPTUI, is if your post type content and/or taxonomy term content is all still safe in the database, and how the settings are for CPTUI.

Are those parts all intact from what you can see?

The only thing seeming to somehow change is that the post type column changes to ‘post’?

Also still curious if you’re able to try what I outlined in my last paragraph in my first reply.

I’m looking throw MySQL database and can’t find any transformed records. I’m afraid that my first description was not fully correct. Old CPT record removed :(( the new one (that I tryed to add today) – yes, transformed to native POST, and without any special data (because special data should be applyed only to this CPT (at ACF Pro setup). So it looks like a lost.

I’m going to move this site to production and will try to apply your last paragraph (I will need to move the site manually in current situation; empty WordPress…parent theme…my child theme and so on)

@tw2113 am I right that your CPT UI hasn’t own table(-s) at the database?

Correct, we don’t create any custom tables. We store our settings in the wp_options table, and that’s about all we save. The rest is processed at run time and any content created with the content types we register are handled by standard WordPress locations like posts/postmeta tables and all the associated term tables.