Windows bcdedit /enum equivalent in Linux
Shows systemd-boot status where systemd-boot is used.
bcdedit /enum
bootctl status || grep menuentry /boot/grub/grub.cfg
sudo grubby --info=ALL
bootctl status || grep menuentry /boot/grub/grub.cfg
Overview
What this command does
On Windows, "bcdedit /enum" is used to show boot configuration. On Linux, the closest practical mapping shown here is "bootctl status". Shows systemd-boot status where systemd-boot is used. This reference is grouped under System & Storage → Boot.
Windows → Linux context
What changes when you use this on Linux?
Equivalent task, different tool
Windows bcdedit /enum maps to bootctl for this task. Treat this as a workflow mapping rather than a character-for-character syntax translation.
Distribution details matter
The Debian/Ubuntu, Fedora and Arch rows are not identical. Use the row for your distribution instead of changing only the package-manager name in an example.
Elevated privilege appears in this workflow
At least one example uses sudo. Confirm the target path, device, service or package before running the elevated form; do not add sudo simply to bypass an unexplained permission error.
For the broader concept behind this mapping, read Linux disks, storage and mounts.
Practical tasks
Common use cases
Show boot configuration
Shows systemd-boot status where systemd-boot is used.
bootctl status
Show boot configuration
bootctl --help
Show command help when supported
man bootctl
Open the manual page when installed
Ready to run
Copyable Linux commands
Review paths, device names, package names and permissions before running any command.
bootctl status
Walkthrough
Examples with explanations
# Windows equivalent: bcdedit /enum
bootctl statusReference
Common options and variations
| Command or option | Use |
|---|---|
bootctl status | Show boot configuration |
bootctl --help | Show command help when supported |
man bootctl | Open the manual page when installed |
Distro differences
Debian/Ubuntu vs Fedora vs Arch
The equivalent is distribution-specific for this task: Debian/Ubuntu uses "bootctl status || grep menuentry /boot/grub/grub.cfg"; Fedora uses "sudo grubby --info=ALL"; Arch uses "bootctl status || grep menuentry /boot/grub/grub.cfg".
| Distribution | Package manager / base | Equivalent command | Difference to notice |
|---|---|---|---|
| Debian/Ubuntu | systemd-boot or GRUB | bootctl status || grep menuentry /boot/grub/grub.cfg |
Equivalent workflow for this distribution. |
| Fedora | grubby / GRUB | sudo grubby --info=ALL |
Equivalent workflow for this distribution. |
| Arch | systemd-boot or GRUB | bootctl status || grep menuentry /boot/grub/grub.cfg |
Equivalent workflow for this distribution. |
Keep learning