ejrydhfs · March 23, 2025 04:00
diff --git a/gistfile1.txt b/gistfile1.txt
 It was so hard to install Linux on a brand new dell Inspiron 3535. It came with windows 11 with bitlocker
 enabled but I didn't remember that it was enabled at the time. Tried to install Linux mint and the
 installer registers the Mok secure boot keys before trying to perform the installation. 

 I should have
 disabled secure boot whatever it seems like it can't really be disabled on this machine, even when you
 disable it it's still active in some way somehow. Anyways install fails because of bitlocker but after
 the MOK keys are registered. Shoot. This triggers a BUG in the UEFI so when I turn off the computer, 
 unplug the drive from which I was installing mint, and turn it back on boom my computer turns on but
 doesn't boot like anything at all not windows not mint.

 The UEFI said no bootable device found and 
 first suspect is the SSD but if I go into the UEFI boot menu I can still boot normally. Spent a whole
 day troubleshooting it and it seemed like I was the first person on the Internet to fix it since I 
 saw a thread on spiceworks saying it was a no fix. So it turns out,

 I needed to boot the second latest
 version of mint, with secure boot "disabled" to finish enrolling the Mok keys. Then I could reflash my
 mint install drive and install the latest version of mint. Great now windows and mint boot. Then I 
 decide to get rid of mint and now windows becomes unbootable again.

 I follow this guide with a drive
 with a windows install image  
 https://www.dell.com/support/kbdoc/en-us/000124331/how-to-repair-the-efi-bootloader-on-a-gpt-hdd-for-windows-7-8-8-1-and-10-on-your-dell-pc#instructions but
 I get an access denied error.

 So I followed a guide that said to run  bootrec /rebuildbcd from CMD but get a system cannot find the file specified error and 
 also I had to find the BCD file by looking manually at the files in the EFI partition. So I ran bcdboot C:\windows and checked from the command line that 
 the EFI partition contained the new BCD and then I was able to boot again.
	It was so hard to install Linux on a brand new dell Inspiron 3535. It came with windows 11 with bitlocker
	enabled but I didn't remember that it was enabled at the time. Tried to install Linux mint and the
	installer registers the Mok secure boot keys before trying to perform the installation.

	I should have
	disabled secure boot whatever it seems like it can't really be disabled on this machine, even when you
	disable it it's still active in some way somehow. Anyways install fails because of bitlocker but after
	the MOK keys are registered. Shoot. This triggers a BUG in the UEFI so when I turn off the computer,
	unplug the drive from which I was installing mint, and turn it back on boom my computer turns on but
	doesn't boot like anything at all not windows not mint.

	The UEFI said no bootable device found and
	first suspect is the SSD but if I go into the UEFI boot menu I can still boot normally. Spent a whole
	day troubleshooting it and it seemed like I was the first person on the Internet to fix it since I
	saw a thread on spiceworks saying it was a no fix. So it turns out,

	I needed to boot the second latest
	version of mint, with secure boot "disabled" to finish enrolling the Mok keys. Then I could reflash my
	mint install drive and install the latest version of mint. Great now windows and mint boot. Then I
	decide to get rid of mint and now windows becomes unbootable again.

	I follow this guide with a drive
	with a windows install image
	https://www.dell.com/support/kbdoc/en-us/000124331/how-to-repair-the-efi-bootloader-on-a-gpt-hdd-for-windows-7-8-8-1-and-10-on-your-dell-pc#instructions but
	I get an access denied error.

	So I followed a guide that said to run bootrec /rebuildbcd from CMD but get a system cannot find the file specified error and
	also I had to find the BCD file by looking manually at the files in the EFI partition. So I ran bcdboot C:\windows and checked from the command line that
	the EFI partition contained the new BCD and then I was able to boot again.