Unable to unregister or re-register feature datasets as versioned

Description

There is an option to 'move edits to base' for data that is registered as versioned. If a feature class that is registered as versioned without the option to move edits to base is added to a dataset that is registered as versioned with the option to move edits to base, the dataset can still be unregistered, but mixed version types are created.
However, if a feature class that is not registered as versioned is then added to the dataset, attempting to unregister or re-register the dataset as versioned fails.

Cause

Enterprise geodatabases do not support feature datasets containing mixed version types. The reason the dataset fails to be unregistered or re-registered is due to versioning incompatibility. There are two known defects related to this behavior, logged as the following bugs: BUG-000082521 and BUG-000092111. When working with versioned data, ensure the aforementioned bugs are taken into account.

Solution or Workaround

1. Compress the geodatabase to state 0. For more information on geodatabase compression, refer to ArcGIS Desktop Help: Geodatabase compression.

Note:
Step 1 is important to prevent edits from being lost because the feature classes will be unregistered as versioned in Step 3.

2. Select all feature classes that are of a different version type, and remove the feature classes from the feature dataset by dragging and dropping the feature classes outside of the feature dataset.
3. Unregister all the feature classes removed from the feature dataset in Step 2 as versioned. For more information, refer to ArcGIS Desktop Help: Unregistering data as versioned.
4. Drag and drop the feature classes back into the feature dataset.
5. Re-register the entire feature dataset as versioned. For more information, refer to ArcGIS Desktop Help: Registering data as versioned.