bare metal restore successful but os not booting

[mcz]

Hello!

I'm having an issue with my private notebook (free edition of veeam agent). I made several backups in the last month and therefore I'm having a chain of a full + multiple delta restore points. Now I'm having an issue with my cardreader and I suspect that the latest windows (1809) is causing the problem. I know that the cardreader was fine in october so I did a bare metal restore using a restore point of october. Everything works well, no error messages but when I finally restart the system, windows can't boot, tries the repair and finally shows the message

"Automatic Repair couldn't repair your PC
Press "Advanced options" to try other options to repair your PC, or "Shut down" to turn off your
Log file C:\WINDOWS\System32\Logfiles\Srt\SrtTrail.txt"

I was a little bit shocked and used another restore point - same result. Then I tried the latest restore point (which I made before I started the whole action) and this time it was successful. So a corrupt chain can not be the case because the latest restore point is also a part of the whole chain.

I suspect that there might be something wrong with the recovery image that I've built. I built the image from the latest windows (1809) and probably that's the reason why I cannot revert to a restore point with the version 1803. Is my assumption right or what else could be the case?

Thank you!

[Mike Resseler]

Michael,

What exactly has happened.. I am guessing here. Without specific logs it will be difficult to figure out what happened. But, if you created a recovery image for 1809, it took all the drivers specific for that build. It might be that some change between 1803 and 1809 causes the issue (a device driver that causes issues with the 1803 build). I think looking in that direction could be the solution

[mcz]

Ok, thank you Mike. That's exactly the direction that I'm looking at. Now the question is: Can I extract a recovery image from an existing backup chain? I mean can I fetch the image when windows was under 1803? And have you got an idea how to grab the logfile C:\WINDOWS\System32\Logfiles\Srt\SrtTrail.txt when windows doesn't boot?

Thank you!

[Mike Resseler]

Hey Michael,

When you boot, you should go to Advanced Options (depending on the manufacturer it is F8 or something) and choose Advanced options => Command prompt. Then you can connect to the HDD

I am guessing you will get an issue with error code = 0x32 in the disk metadata test. (Again, guessing)

[mcz]

Hi Mike,

now I've got the results:

errorcode 0x57
file c:\efi\microsoft\boot\resources\custom\bootres.dll is corrupted

Not sure if it's related to the recovery image or not. Another fact I would like you to know:

Luckily, I've created the recovery media and saved it as image on the disk which means that the backups contain these images. So I pulled an image from last summer (where I was using 1803) and tried to create the recovery media (using the tool "iso to usb"). But then I couldn't boot from this media. I tried again and again but somehow the boot process got interrupted (without errormessage) and finally it booted my windows. I then tried to use the latest image, again using the "iso to usb" tool, but even with the latest image the boot wasn't successful. I then used veeam's recovery media creator to create the recovery media (of course using the same usb device) and then I was able to do the bare metal restore.

Have you got an idea? Which tool should I use to write the image to a usb, any suggestion? And have you got an idea about the corrupted bootres.dll?

Thanks very much!

[Mike Resseler]

Bootres.dll is a tough one... Any change that the image has virtualization enabled in BIOS or UEFI?

[mcz]

Could be possible. What is your suggestion? Should it be disabled or enabled (virtualization)?

[Mike Resseler]

It might make a difference if you disable it. That could lead to getting you through the OS booting. I have had the same issue where I restored a windows image from once PC to another, and the hardware was indeed different but the issue was not the hardware but intel-VT being enabled on the newer one and it wasn't enabled on the older one. The other way around can cause also the issue.

[mcz]

good to know Mike, thank you. I can remember that I had to switch on intel-VT due to vmware workstation but every bios (or uefi) update disabled it. So there is a good chance that different restore points had other settings regarding intel-vt...

What about the recovery image creation? Any suggestion which application I can use to bring the image onto a device?

[Mike Resseler]

Normally our tool should be able to create that image. If there are issues, then it is best to talk to support I think.

[mcz]

Yeah but please consider the following case: System is down, doesn't boot and I'm just having the .img-file (which is the image but has only been saved on the local disk). How can I write the image to a external device for the boot process? I mean since the system doesn't run, I cannot run the veeam recovery image tool...

[Mike Resseler]

Ah, the only option you have then is to create such an image (to USB) from another computer... You can always add device drivers during restore.

[mcz]

Ok Mike, I did the following:

Opened UEFI and checked intel-VT, which was enabled. I disabled it and did another bare metal restore - boot process failed again. I then did a bare metal restore with the latest restore point (leaving intel-VT still disabled, allthough it was switched on before) and windows was booting. So that means my latest restore point doesn't care about the intel-VT, so does the restore point from october. It doesn't matter if I have it disabled or not, windows is booting with the latest restore point and aborting with the other restore points.

Have I got you wrong? Would I have to disabled it and then create the recovery media again or is the option not considered while building the image?

[tinnguyen]

Hi, (Case #07417329)

I'm facing an issue after creating Recovery Media and booting a new client. After rebooting or attempting a repair, Windows fails to boot. The following error message appears:

"Automatic Repair couldn't repair your PC. Press 'Advanced options' to try other options to repair your PC, or 'Shut down' to turn off your PC. Log file: C:\WINDOWS\System32\Logfiles\Srt\SrtTrail.txt."

I've reviewed several suggestions, but none seem to provide a solution. Do you have any ideas on how to fix this?

Thank you!