Resolution
----------

By default, the **GRUB\_ENABLE\_BLSC** is set to **true** in the **/etc/default/grub** file. When this variable is set to **true**, GRUB2 uses **blscfg** files and entries from the **/boot/loader** file instead of **menuentry** entries in the **grub.cfg** file.

To resolve the **ClientError: BLSC-style GRUB found** error on import or export, set the **GRUB\_ENABLE\_BLSC** parameter to **false** in the **/etc/default/grub** file. Then, rebuild the grub configuration file.

1.    Open the **/etc/default/grub** file with a text editor, such as vi.

2.    Make sure that the **GRUB\_ENABLE\_BLSC** parameter is set to **false**.

3.    Run the following command to rebuild the grub config file:

```plaintext
$ grub2-mkconfig -o /boot/grub2/grub.cfg
```

Thanks. I had this issue today and the solution provided here worked!

When I use the ImportImage task to import a Red Hat Enterprise Linux 8 (RHEL 8) virtual machine (VM) image in AWs Import/Export, I receive an error. Or, I receive an error when I use the ExportImage task to export a RHEL 8 Amazon Machine Image (AMI) in Import/Export.

Resolve "BLSC-style GRUB errors" when using Import/Export

How do I resolve the “ClientError: BLSC-style GRUB found, but unable to detect default kernel” error when I use Import/Export? 

Compute

Why do I get an error "The snapshot is currently in use by AMI" when I try to delete an EBS snapshot, even though there is no AMI on the account?

How can I set the default printer on Amazon Windows WorkSpaces and prevent the settings from reverting?

How do I resolve the “ClientError: BLSC-style GRUB found, but unable to detect default kernel” error when I use Import/Export?

Resolution

Relevant content