VirtualBox uninstall problem

[FrenchPress]

@Rory

The problem for me isn't UEFI Secure Boot.....it's that VirtualBox had an update and now I'm getting a message to permit the use of third party drivers that you see in the screen shot.

I am afraid you got a cause and effect wrong.
The cause of the problem is secure boot which manifests itself as a problem in VirtualBox update.

Even we could help you to solve the current VirtualBox issue, you will hit another roadblock eventually when such update comes to your system next time.

[Rory]

@Aravisian

And in reading that page, you can easily see that the Synopsis I gave above is accurate.

I haven't read it as it doesn't solve my immediate problem.

[Kedric]

Try this? sudo apt-get --fix-broken install

[FrenchPress]

@Kedric

Try this? sudo apt-get --fix-broken install

OP can try.
But I do not think it would help.
I first thought the problem was incomplete installation but then I found out that the system got secure boot enabled.

[Rory]

@FrenchPress

Even we could help you to solve the current VirtualBox issue, you will hit another roadblock eventually when such update comes to your system next time.

I find it hard to make any sense of that though because I have been updating my Zorin 16 Pro system everyday since 17th August and everything has been fine.....with UEFI Secure Boot enabled.....up to now and this VirtualBox update.

So if I remove the VirtualBox update my immediate problem is resolved....no?

[Aravisian]

@Rory

So if I remove the VirtualBox update my immediate problem is resolved....no?

No.
You need to configure your packages. Something has corrupted or broken.

[Kedric]

So um I can no longer like for the day lmao. i also made maximum number of edits

[Kedric]

can't edit anything, ouh nevermind I can edit, I just made maximum edits for one particular post I think?

[FrenchPress]

@Kedric

can't edit anything

You should learn how to consolidate your postings into one. It is not a Twitter and longer meaningful postings are more appreciated than short meaningless ones.

[Rory]

@Aravisian

Please allow us to help you resolve the issue instead of insisting you don't want the fix.

Happy to receive anyone's help and appreciate it too. Not happy to turn off UEFI Secure Boot on a dual boot system with Win 10.

Neither Win 10 nor UEFI Secure Boot have cause the issue, it's the update to VirtualBox from what I can tell and I just need to remove it.

I can promise you I'm not trying to annoy anyone, it would be counterproductive especially as I intend to be a committed Zorin user and will likely be asking for further guidance in the coming months. You especially Aravisian helped me a couple of weeks ago with the Dell problem.

[Kedric]

Thats what I do, I keep editing the post to add information. @Aravisian told me about it.

[Rory]

@Kedric

Try this? sudo apt-get --fix-broken install

Kedric, I'll try that but is it OK for me to kill off the Terminal which still has the process running from before? It's waiting for me to say OK to this:

[FrenchPress]

@Kedric

Thats what I do, I keep editing the post to add information. @Aravisian told me about it.

Lucky you.
Now you got 2 mentors on this forum

[Kedric]

Should be ok, you're not installing or deleting anything.

[Aravisian]

@Rory

Happy to receive anyone's help and appreciate it too. Not happy to turn off UEFI Secure Boot on a dual boot system with Win 10.

I understand your point of view. However, the trouble is that you also refuse to configure it. Do you see the issue here? You won't turn it off, but refuse to configure it, creating your own quandary.

@Rory

Neither Win 10 nor UEFI Secure Boot have cause the issue, it's the update to VirtualBox from what I can tell and I just need to remove it.

This is what we are trying to explain: The virtualbox issue is a symptom not a cause.

[Rory]

@tomscharbach

I want to be very careful, because (1) UEFI/SecureBoot is complicated, and (2) I am speculating and might well be in over my head.

I've read (with respect to other Linux builds over the years) that it is possible for a user to create/enroll a "personal" MOK and load Linux builds that otherwise require that Secure Boot be disabled with Secure Boot enabled. I've never tried this, it is far over my head, might well brick your computer, and I personally wouldn't touch it with a ten-foot pole. For me, and with all due respect, almost certainly for you, this falls under the "Don't try this at home!" category.

Reading it, I think that the message is offering to generate a private MOK and enroll that MOK in the computer's firmware. Why anyone would do this to uninstall software is beyond my ken.

I took a few minutes and read through is entire thread. I suspect that (a) the VirtualBox installation is corrupted or (b) Virtual Box has made a major change in configuration in more recent builds that tangle it up somehow with Secure Boot. Those are the only thing that makes sense to me, and I have no idea how to proceed at this point.

I'm going to do some research while I watch the University of Wisconsin football team pound Penn State into the ground and see if I can come up with something.

Mate, thank you, I'm definitely on the same page about being careful, hence my reason for posting and asking for help. The enrolling an MOK worried me because I don't know the implications and it's also a third party driver and all a bit above my head.

Anyway, I appreciate your post and good luck Wisconsin

[Aravisian]

In which case, you can just close the window as Tom suggested. This will bring us back to the original problem.
First, you need to be able to successfully run dpkg --configure .

[Rory]

@Kedric

Should be ok, you're not installing or deleting anything.

Well I ran sudo dpkg --configure -a and that message is where it is now sat. OK, I'll kill the terminal and try that command you gave.

[Rory]

@tomscharbach

Say "No" and kill the process. The last thing you want to do is to create a private MOK at this point. Then try Kedric's suggestion. If Virtual Box is corrupted, Kedric's suggest might resolve that issue.

Did that, killed the terminal, tried the command Kedric gave sudo apt-get --fix-broken install and am now back at this again:

It's a bit of a loop and there is no way to say 'Not OK' and I certainly don't want to create a private MOK, especially for something which I'm actually trying to uninstall.