nMP crashing after sneek update from 13.2 to 13.4

[StrawberryX]

Hello,

Suddenly my Mac Pro was rebooting and trying to instal 13.4.
That crashes ... It says on boot up OSX can't be installed.
I don't want 13.4 and was very happy with a fully working ( apps etc ... 13.2 ).
I don't know how the installer was downloaded It was just in sleep mode and suddenly rebooting.

When I boot during startup and choose what boot drive.
I have the options OSX Installer, My boot drive, My secondary boot drive.

If I choose my boot drive all is still well, except there I can't see the installer as a boot device.

Having a crashing installer during every boot is no fun.

Is there a way to remove the installer as a boot device?

Otherwise I will always have to choose a start up disk or start with a crashing installer.

I stayed on 13.2 exactly for something like this.
All my apps work.

But lately I got some more forced upgrades It seems.
First every Mac program upgraded from Itself.

And now suddenly I got the installer ... for 13.4.

Any tips?
I just want to stay on 13.2.

Sorry for the misspelled title etc ...
--- Post Merged, Today at 1:56 AM ---
OK I checked in disk utility.

The difference between my external boot drive, that just has high sierra but none of my apps.
And my main drive.

Is that in the container of the main drive, there is a red part called VM.

I'm in the middle of a big premiere/after FX project with the deadline in 10 days,
I don't know how the update creeped on my computer.
I have been selecting tomorrow for months now regarding to the system update.
Just last week, It was like updates started downloading by themselves.

All that stuff like this is very unwelcome now ...
I finally had a stable high sierra rig ...

Can I get rid of the VM in my container?

I have to reboot sometimes instead of sleep.
And would not like every reboot to be "OSX can't be installed on your computer"
Or select the bootdrive instead of the VM during start up, not easy because It boots so fast,
sometimes I just don't have the time.
--- Post Merged, 47 minutes ago ---
An option could be getting the latest version of CCC.

Clone the drive not the container ...
Erase the drive.
Put the clone back on the drive or something ...

But I don't really have the time now because of the deadline for maintanence ...

 

[StrawberryX]

Seems to be fixed for now after installing all my apps on the TB2 samsung NVME drive with HS.
Only difference, that one has trim enabler on it.
And turned off al the Apple Store Update stuff, which were all turned off on the samsung drive.
But some were turned on on the Apple drive ...

No more trying to install version 13.4 when rebooting.

It still has the VM partition but the color is changed.

 

[developer13245]

Welcome to the new Apple quality level. They trick (force) you to upgrade, and get screwed by all the new bugs.
Now it's your job to test and report bugs (that they ignore). So see, it's all you fault.

 

[bsbeamer]

I cannot recommend Carbon Copy Cloner enough. Have not run into this exact issue, but the garbage with automatic installers on both Apple and Adobe's part has put me in a bind more than a few times. Having a stable clone to return to quickly has paid for itself when it comes to dealing with client work.

In addition to my regular backups and Time Machine, I try to keep several versions of the system drive that are updated at different times and different states for these exact reasons. The main backup SSD is updated every 7-10 days, unless a recent OS or Adobe update has been installed. I keep an external USB spinning drive that gets updated around every 30 days. Also keep a SATA spinning HDD with multiple partitions that only gets updated before major OS updates (10.11 > 10.12, 10.12 > 10.13).