Process

unknown

bcdedit.exe

bcdedit.exe is the Boot Configuration Data editor, the tool that views and changes how Windows boots. Administrators use it for boot troubleshooting and multi-boot setups. Ransomware uses it to switch off the recovery options that would let a victim restore the system.

File identity

File details

Not observed.

Signing information

Not observed.

File version0

Not observed.

File size0

Not observed.

Execution context

File paths0

Not observed.

User context0

Not observed.

Integrity level0

Not observed.

Instances0

Not observed.

Session0

Not observed.

Token privileges0

Not observed.

Ancestry

Parents0

Not observed.

Children0

Not observed.

Grandparents0

Not observed.

Grandchildren0

Not observed.

Behavior

Loaded modules0

Not observed.

Named pipes0

Not observed.

Process handles0

Not observed.

Command-line patterns0

Not observed.

Indicators

Hashes

Not observed.

Analysis

About this process

bcdedit.exe reads and modifies the Boot Configuration Data store, the database that tells the Windows boot loader what to start and how. It can add or change boot entries, set safe-boot and recovery options, and toggle features like driver-signature enforcement. It requires administrative rights and lives at C:\Windows\System32\bcdedit.exe.

Legitimately, bcdedit is run by administrators during boot repair, OS installs, or driver debugging, which is infrequent on most machines. The setting it changes is what gives an instance meaning.

Security notes

bcdedit.exe is a fixture of ransomware (T1490). Before or during encryption, operators run bcdedit /set {default} recoveryenabled no and bcdedit /set {default} bootstatuspolicy ignoreallfailures to stop Windows from booting into the recovery environment that could repair or roll back the machine. These commands almost never appear in normal use, and seeing them, especially next to shadow-copy deletion with vssadmin or wbadmin, is close to a confirmed recovery-inhibition step.

Because bcdedit is a legitimate administrative tool, the specific setting and the parent are what matter. A boot-repair session by an administrator looks nothing like a recoveryenabled no issued by a script host in the middle of mass file changes.

Anomaly signals5
  • Image path other than C:\Windows\System32\bcdedit.exehigh
  • /set {default} recoveryenabled no (disabling automatic recovery)high
  • /set {default} bootstatuspolicy ignoreallfailureshigh
  • Parent is cmd.exe, powershell.exe, an Office application, or an unfamiliar processhigh
  • Run alongside vssadmin, wbadmin, or wmic shadowcopy deletehigh

Telemetry

OS prevalence0

Not observed.

Observation timeline

Not observed.

References

Subsearch

Hasbeen seen inof bcdedit.exe?