I have an Acer Nitro 17-41 with a Ryzen 7 7840HS, Radeon 780M, RTX 4060, and two SSDs. Windows 11 is installed on a 4TB WD_BLACK SN850X, while a 1TB Samsung SSD is used as secondary storage. The system is configured for UEFI boot with AHCI, and the BIOS detects both drives normally.
The laptop booted normally until I installed a pending Windows update. Since then, every startup goes through "Preparing Automatic Repair" and "Diagnosing your PC" before returning to the recovery menu. Startup Repair, shutdowns, BIOS checks, uninstalling the quality update, System Restore, SFC, CHKDSK, and the bootrec commands have not fixed it. The feature-update rollback fails with an error, and bootrec /scanos and /rebuildbcd find no Windows installations even though the files are visible from the recovery environment.
Safe Mode produces an INACCESSIBLE_BOOT_DEVICE blue screen, while debugging mode reports a loader rollback error. I have not changed BIOS settings or overclocked anything. I want to repair the installation without resetting Windows because this is my only computer and I need to preserve my files and installed programs. What should I try next?
3 Answers
The boot configuration may have been damaged during the update or rollback. You can back it up and rebuild it, but first verify that the EFI partition and Windows partition have the letters you expect. If `C:BootBCD` does not exist, the BCD may be stored on the EFI partition instead, which is why the basic bootrec commands are not finding anything. Using diskpart to identify the small FAT32 EFI volume, assigning it a temporary letter, and rebuilding the boot files with `bcdboot C:Windows /s S: /f UEFI` is generally more appropriate for a UEFI system than relying only on bootrec. Substitute the correct Windows and EFI letters.
Since the files are still visible, prioritize backing them up before making additional changes. From recovery, you can connect an external drive and use the file browser from Notepad’s Open dialog, or copy important folders with robocopy. After the data is safe, an in-place repair using Windows installation media may preserve files and applications, but it usually requires booting into Windows first. If that is impossible, reinstalling or resetting may be the fallback, so make sure you have a backup and confirm whether drive encryption is enabled before proceeding.
Before attempting more boot repairs, confirm the drive letters from the recovery environment. They can change there, so the Windows installation may not actually be mounted as C:. You can use diskpart, then list the volumes, exit, and check each candidate drive for a Windows folder. Once you know the correct letters, run an offline system-file check such as `sfc /scannow /offbootdir=C: /offwindir=C:Windows`, replacing C: with the actual Windows volume. The recovery environment itself is usually mounted as X:, so it should not be used as the Windows path.
Windows appears to be mounted as C: and the recovery environment is X:. I had only run the regular SFC command, so I’ll try the offline form with those paths.
The command that tried to access C:BootBCD reported that the file was not found, so it may be on the EFI partition. I’ll identify that partition before trying to rebuild the boot files.