Solved

Agent for Windows recovery boot loop


  • Not a newbie anymore
  • 1 comment

I've been using Veeam Agent for Windows for a bit, and have successfully used backups to restore individual files. I wanted to upgrade my NVME system drive to a larger one, so I figured I would try using the restore.
I made sure my Windows 10 was up to date, updated Veeam to the latest version, created a new recovery ISO, and created a fresh backup. I then swapped in the new NVME and booted from a recovery USB. I stepped through the wizard, selected system volumes only (there is a data SSD I don’t need to restore); I did not use the Manual restore.
After it copied everything to the new drive I rebooted, and then was stuck in a boot loop which ultimately ended in a recovery environment. Looking through the manual, there is a note about driver injection, so I tried again and disabled driver injection, still stuck in a loop. I put the original NVME back in and started looking for answers - any insight appreciated.

icon

Best answer by ddot 27 June 2024, 00:09

View original

2 comments

Userlevel 7
Badge +21

Hi @ddot - from everything that I have been able to find there is no resolution that I can offer but it would be best to contact Support to open a case to have them look into this issue with you.  I hope this helps.

Thanks @sharixralex23  The system itself is fine, no errors.  I did a lot of searching, and tried some BIOS changes to get it to boot (no joy), tried different methods to fix it with bootrec (no joy), some other things I can’t recall right now. Based on my searching I think my partitions are in a different order than they should be, despite being a vanilla install. The various things I tried to fix the boot files did not work. I feel I’m stuck doing a clean install on the new drive, which I don’t want to deal with at the moment so I will just hold onto this new NVME until I decide what I want to do.

Thanks @Chris.Childerhose , I put in a support ticket, and after a few days it was closed without response because they had no one available to look at it :(

Comment