Unable to restore the Windows Server 2019 using Windows rescue image.

Question

Hello Community,

We are reproducing a test scenario in our cloud environment to demonstrate how to troubleshoot a Windows instance using a rescue image.
In our environment, we do not have the option to boot with an ISO or detach the root disk. Our templates are configured with raw and qcow2 image formats.

To simulate a real-time issue and put the instance into an error state, we deleted the winload.exe file from the system32 directory, causing the instance to fail to boot. We then created a rescue image for troubleshooting purposes.

When booting the instance with the rescue image, the disks inside the instance are labeled as C and D drives, with C is the rescue image disk and D is the original root disk of the instance (the original bootable drive for the instance).

We need guidance on how to effectively troubleshoot the instance in this situation. Any insights or step-by-step instructions would be greatly appreciated.

Cloud Environment:- Redhat Openstack Platform 17.1
OS:- Windows server 2019

Regards
Raghava Yerubandi

Answer 1

Hello

Thank you for posting in Microsoft Community forum.

Troubleshooting a Windows instance in a cloud environment like Redhat Openstack Platform 17.1 can be complex, especially when dealing with boot issues. Since you've already identified that the winload.exe file is missing from the system32 directory and you have a rescue image ready, here are the steps you can follow to troubleshoot the instance:

Boot the instance with the rescue image: You've mentioned that upon booting with the rescue image, the disks inside the instance are labeled as C and D drives, with C being the rescue image disk and D being the original root disk of the instance.

Access the file system of the original root disk: Once the instance is booted with the rescue image, you should be able to access the file system of the original root disk (D drive). You can use disk management tools within the rescue environment to verify that the drive is accessible and intact.

Replace the missing winload.exe file: The winload.exe file is essential for Windows booting process. You can copy this file from the rescue image or another working Windows Server 2019 instance to the D drive's system32 directory.

Check boot configuration: Use the bcdedit command to check the boot configuration data (BCD). Ensure that the paths and settings are correct for the Windows boot loader. The BCD store should be located on the D drive, and you might need to use the /store switch to specify the BCD file's location if it's not in the default directory.

Rebuild BCD if necessary: If the BCD is corrupt or misconfigured, you may need to rebuild it. You can use the bootrec /rebuildbcd command to scan for Windows installations and let you select the ones you want to add to the BCD.

Fix master boot record (MBR) and boot sector: If there are issues with the MBR or boot sector, you can use the bootrec tool with the /fixmbr and /fixboot options.

Check disk for errors: Run a chkdsk on the D drive to check for and fix any file system errors that might prevent booting.

Restart the instance: After making the necessary repairs, restart the instance without the rescue image to see if the issue is resolved.

Best Regards,

Wesley Li

Answer 2

Hello Wesley Li,

Thank you for your response. I followed your instructions on my rescue instance, and my instance booted normally and working fine after I unrescued it.

Regards

Raghava Y

Answer 3

I'm so glad that I could provide some help here, it will be great to mark any useful answer so other can easily find it.