Virtuelle Kopie

Normally, I do not want the virtual copy to bring over any of the edits in the original. So on the original, I select the first History State, then make the virtual copy.  (profile might still come over however?) You might have done that.

Each image version maintains its own edit history.

If you made 10 edits onto an imported photo (the master copy), and then you create a virtual copy - this virtual copy does reflect the result of all those 10 edits. But it does not show the history of how those were successively done. They were done to a different version. This is a new-born image version with no "memory" at all. Nothing has previously happened to it.

If you want a particular image editing state (cumulative set of editing) to be possible to return to from any image version, you can save that state as a named Snapshot. All the virtual versions (as well as the master version) for a particular imported file, share its Snapshots in common. And those are also included in external XMP metadata when that does get written out. Which only the master version can do.

So: whatever image version you have made this new virtual copy FROM, still does have that prior History. You can always revert to some earlier image state there, and generate a different virtual copy based on that state, if you want.

What do you mean with "the protocol"? The printer profile perhaps? If so, then that happens if you have 'soft proof' enabled at the bottom of the develop module main window. In all other situations the virtual copy will simply be named 'Copy 1'.