Share via

FVE_SECURE_BOOT_CHANGED

yağmur 0 Reputation points
2026-06-01T08:35:50.12+00:00

I have an MSI Katana laptop running Windows 11.

The problem started immediately after I shut down the laptop using “Update and Shut Down”. On the next boot BitLocker recovery was requested with error FVE_SECURE_BOOT_CHANGED.

After not using the laptop for a few days, it started asking for a BitLocker Recovery Key at boot. The error code shown was FVE_SECURE_BOOT_CHANGED.

I retrieved the recovery key from my Microsoft account and entered it successfully. After that, the system proceeds past the BitLocker screen, shows the MSI logo, and enters Automatic Repair.

However, Windows cannot start. Startup Repair fails, System Restore fails, and uninstalling updates does not work.

In BIOS:

  • Secure Boot is enabled and active.
  • TPM / Security Device Support is enabled.
  • Date and time are correct.
  • The SSD is detected correctly (SanDisk PC SN5000S 1TB).

In Windows Recovery Environment:

  • diskpart -> list disk returns “There are no fixed disks to show.”
  • diskpart -> list volume shows no volumes.
  • wmic diskdrive get model,size returns “No instance(s) available.”

The SSD is visible in BIOS but not visible in Windows Recovery Environment.

I would like to recover access to Windows and preserve my data if possible.

Windows for home | Windows 11 | Windows update
0 comments No comments

3 answers

Sort by: Most helpful
  1. Lucus-V 7,815 Reputation points Microsoft External Staff Moderator
    2026-06-04T18:48:19.0766667+00:00

    Hi yağmur,

    You may try using Windows Recovery Environment from a bootable Windows USB.

    Please refer to Download Windows 11, download and run Media Creation Tool to create a bootable USB. It's recommended to use a USB with 8GB storage or above.

    Then following these steps:

    1. Start your computer using the bootable USB drive.
    2. When the Windows installation page appears, click "Repair Your Computer" to launch the Windows Recovery Environment.
    3. In the Windows Recovery Environment, select Troubleshoot > Advanced Options > Startup Repair.

    From that bootable USB you also could perform a clean install if you already backed up all necessary data. Please note that a clean install will wipe out your data in C drive.

    If you have further information, please feel free to let me know.

    Was this answer helpful?

    0 comments No comments

  2. Gaming Divy 20 Reputation points
    2026-06-01T09:08:38.9733333+00:00

    it could be because you don't have a storage driver for WinRE, also what's your update build or update code?

    Was this answer helpful?

    0 comments No comments

  3. AI answer

    2026-06-01T08:36:09.83+00:00

    The BitLocker error code E_FVE_SECUREBOOT_CHANGED indicates that the Secure Boot configuration measured in TPM PCR 7 has changed unexpectedly. In this state, BitLocker requires a recovery method to unlock the device.

    From the provided information:

    • Secure Boot is enabled and active in firmware.
    • TPM is enabled.
    • BitLocker recovery key entry succeeds, but Windows then fails to start and Automatic Repair cannot fix the issue.
    • In Windows Recovery Environment, no disks or volumes are detected, even though the SSD appears in firmware.

    According to the BitLocker preboot recovery documentation, for E_FVE_SECUREBOOT_CHANGED:

    • Cause: The Secure Boot configuration unexpectedly changed; the boot configuration measured in PCR 7 changed.
    • Resolution: A recovery method is required to unlock the device.

    In this scenario, the recovery key has already been used successfully, so BitLocker is no longer blocking access. The remaining problem is that Windows and Windows Recovery Environment are not detecting any fixed disks, which prevents Startup Repair or other recovery tools from accessing the system volume. The provided context does not include additional supported steps for repairing or recovering data when the disk is visible in firmware but not visible to Windows or WinRE.

    The only supported actions in the context for this error and related startup issues are:

    • Use a BitLocker recovery method (already done) to unlock the device.
    • Use Startup Repair from Windows Recovery Environment to attempt to fix startup issues such as corrupted BCD or system files. This requires that the disk be visible and that the BitLocker key be available.
    • If Startup Repair cannot fix the problem, it provides a report, but no further supported remediation steps are given in the context.

    Because the disk is not detected by Windows Recovery Environment and the context does not provide additional supported procedures for this condition, no further data-preserving recovery steps can be described based on the available information.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.