We often have given the advice to disable secure boot when users reported problems with their system.
Recently, however, some users have reported that this has damaged their desktops, and, in some cases, even a reinstallation of Zorin was required because re-enabling secure boot didn't help to go back to the previous state.
What’s causing this? Is it due to Nvidia drivers? Should this advice no longer be given if Zorin was installed with Secure Boot enabled? Has something changed so that, whereas it used to be possible to disable Secure Boot after installation, it’s no longer possible?
My question was what can help to disable secure boot afterward.
Do you think it can help to remove the installed (secure boot signed) nvidia drivers when booted with secure boot and then boot without secure boot and install the nvidia drivers again? Or can the MOKs be deleted?
I'm wondering what can help those users to avoid a fresh install of Zorin if they want to disable secure boot because of problems or because they want to install a later unsigned kernel.
I'm a newbie to Linux as @Nourpon will know with modern hardware I believe this is the way going forward. With my new Lenovo 2 in 1 disabling secure boot caused me 2 problems
1 With my dual boot system I couldn't log into windows.
2 Booting Zorin with it disabled wrecked the installation removing desktop config and removing programs I'd installed.
As Zorin 18.1 supports secure boot why disable it if no problems.
Of course with dual boot you have to activate secure boot.
But sometimes when there is no dual boot it make some driver problems for some hardware, and also if you want to install unsigned kernel, you can't have secure boot activated
with modern hardware I believe this is the way going forward. With my new Lenovo 2 in 1 disabling secure boot caused me 2 problems