I’m have question about the usb recovery drive. For some reason the recovery will not boot into the bare metal utility, it stops and shows a command window. I’m running latest windows 11 so any thoughts as to why this would be?
Yes I think something is not being done right here as this should work. If done wrong you get the command prompt if the system cannot boot from it.
Definitely is running UEFI on a year old desktop system. Just for the heck of it I remade 2 USB’s with 1 from ISO and the the other from the Veeam app and both showed no errors during the process but fail at boot.
I will try to ask Veeam support but as do not have a company email and am using the free windows agent I’m not sure i will get any support from them.
Thanks for all your help as its is much appreciated.
Yes I think something is not being done right here as this should work. If done wrong you get the command prompt if the system cannot boot from it.
Definitely is running UEFI on a year old desktop system. Just for the heck of it I remade 2 USB’s with 1 from ISO and the the other from the Veeam app and both showed no errors during the process but fail at boot.
I will try to ask Veeam support but as do not have a company email and am using the free windows agent I’m not sure i will get any support from them.
Thanks for all your help as its is much appreciated.
No problem let us know what happens to help others.
Or you have an alternative for backups should the Veeam Agent not work. 😉
This is actually a foolish design and alternatives need to be identified and implemented. Recovery should not be reliant on building a working image on a specific version of an OS. I SHOULD be able to install whatever i want including preview builds and use the tool I pay good money for, to recover should I need to.
Other vendors offer linux based recovery media, this is probably a good addition to the product and I hope it's one that comes along with V12.
I totally agree. Would be great if they based the working image on Linux as this would certainly help resolve the issue we are facing.
I agree, the recovery media could be more flexible. But this does not solve the problem that a backup software can’t support a new OS version completely at the next day after it appears.
In the issue in this thread you cannot be sure if your backup is really reliable, because this OS version is not completely tested.
It takes some time to test and adapt the backup software to the new OS version. At the most times this takes several weeks only with Veeam….
Or you have an alternative for backups should the Veeam Agent not work. 😉
This is actually a foolish design and alternatives need to be identified and implemented. Recovery should not be reliant on building a working image on a specific version of an OS. I SHOULD be able to install whatever i want including preview builds and use the tool I pay good money for, to recover should I need to.
Other vendors offer linux based recovery media, this is probably a good addition to the product and I hope it's one that comes along with V12.
This is not a foolish design and most all vendors follow this path. Just because a new version is out does not require the vendor to support it day one and no vendor I know does this! It will take weeks sometimes months to test so you should not be able to install what you want and expect Veeam to support it right away they need to test it like all vendors.
@SchrepfV have you tried to create recovery USB from another PC and the use that to boot into recovery from yours? If there’s no RAID or particular driver, it should works.
This was my suggestion next - I think the ability of the source PC to make a boot media may be the question at this point.
So I can say that I’ve made recovery images across many systems, never had an issue. I’ve shared them left right up and down and they work well, including across versions. The epitome of “it works” but “may not be supported” - so try a different PC, install the free agent, make a recovery image and try again. Will say, I’ve been fiddling with the agent since 2014, never seen this situation.
Yes I think something is not being done right here as this should work. If done wrong you get the command prompt if the system cannot boot from it.
Definitely is running UEFI on a year old desktop system. Just for the heck of it I remade 2 USB’s with 1 from ISO and the the other from the Veeam app and both showed no errors during the process but fail at boot.
I will try to ask Veeam support but as do not have a company email and am using the free windows agent I’m not sure i will get any support from them.
Thanks for all your help as its is much appreciated.
No problem let us know what happens to help others.
Hi Chris,
Here is the latest update.
Just received reply from Veeam, look like their schedule will not allow support on this issue.
Looks like I’ll need to find a solution on this without Veeam’s support.
Yes I think something is not being done right here as this should work. If done wrong you get the command prompt if the system cannot boot from it.
Definitely is running UEFI on a year old desktop system. Just for the heck of it I remade 2 USB’s with 1 from ISO and the the other from the Veeam app and both showed no errors during the process but fail at boot.
I will try to ask Veeam support but as do not have a company email and am using the free windows agent I’m not sure i will get any support from them.
Thanks for all your help as its is much appreciated.
No problem let us know what happens to help others.
Hi Chris,
Here is the latest update.
Just received reply from Veeam, look like their schedule will not allow support on this issue.
Looks like I’ll need to find a solution on this without Veeam’s support.
Best,
Volker
You need to open another ticket and reference this one as they should not auto-close them. Even post the issue on the Forum referencing the old and new ticket numbers to get action.
It would help, if you can describe all steps taken (probably with screenshots). Or take a video from the boot process until the cmd window shows up and upload it to youtube so we can see whats happening exactly.
You can post the Video to this community.
If we still don’t have an answer, you can try our R&D Forum. Just open a new case first and provide the case number in your forum topic. :)
Hey, i’ve got the same Problem. Windows 11, Veeam Recovery media Boots into command prompt (X:\Windows\System32)
newest Version of Agent and Recovery Media.
tried UEFI and Legacy Boot also with Rufus on different machines
@SchrepfV - there is another user with same issue. For both of you which Windows 11 version are you running? The initial release or an Insider build by chance? If you run WINVER you will get a screenshot of the Windows version screen.
I’m running 22621.160, I’m not in the insider build.
Hey, i’ve got the same Problem. Windows 11, Veeam Recovery media Boots into command prompt (X:\Windows\System32)
newest Version of Agent and Recovery Media.
tried UEFI and Legacy Boot also with Rufus on different machines
@SchrepfV - there is another user with same issue. For both of you which Windows 11 version are you running? The initial release or an Insider build by chance? If you run WINVER you will get a screenshot of the Windows version screen.
I’m running 22621.160, I’m not in the insider build.
No but that is the next release of Windows and not the original 22000.xxx release. So there could be some compatibility issues with the Veeam Agent is my guess.
Agree, but it does appear that there is an issue and more people will be updated and have the same problem. Hope that Veeam take a look to see if they can resolve this quickly. Note that there apparently was a similar problem back in 2019 on a windows 10 update so would think that Veeam has history with such an issue and thus might be a simple fix based on history.
Hey, i’ve got the same Problem. Windows 11, Veeam Recovery media Boots into command prompt (X:\Windows\System32)
newest Version of Agent and Recovery Media.
tried UEFI and Legacy Boot also with Rufus on different machines
@SchrepfV - there is another user with same issue. For both of you which Windows 11 version are you running? The initial release or an Insider build by chance? If you run WINVER you will get a screenshot of the Windows version screen.
I’m running 22621.160, I’m not in the insider build.
No but that is the next release of Windows and not the original 22000.xxx release. So there could be some compatibility issues with the Veeam Agent is my guess.
Agree, but it does appear that there is an issue and more people will be updated and have the same problem. Hope that Veeam take a look to see if they can resolve this quickly. Note that there apparently was a similar problem back in 2019 on a windows 10 update so would think that Veeam has history with such an issue and thus might be a simple fix based on history.
Thanks
Yeah here is hoping as I remember the one in Win10 too.
Hey, i’ve got the same Problem. Windows 11, Veeam Recovery media Boots into command prompt (X:\Windows\System32)
newest Version of Agent and Recovery Media.
tried UEFI and Legacy Boot also with Rufus on different machines
@SchrepfV - there is another user with same issue. For both of you which Windows 11 version are you running? The initial release or an Insider build by chance? If you run WINVER you will get a screenshot of the Windows version screen.
I’m running 22621.160, I’m not in the insider build.
No but that is the next release of Windows and not the original 22000.xxx release. So there could be some compatibility issues with the Veeam Agent is my guess.
Agree, but it does appear that there is an issue and more people will be updated and have the same problem. Hope that Veeam take a look to see if they can resolve this quickly. Note that there apparently was a similar problem back in 2019 on a windows 10 update so would think that Veeam has history with such an issue and thus might be a simple fix based on history.
Thanks
Yeah here is hoping as I remember the one in Win10 too.
Guess it’s wait and see and hope we don’t need a to use “bare metal restore” before the fix… 🤞
Same Issue on HP Elitedesk 705 G5. All latest Build OS Windows 11 22H2 and Veeam Environment
Worked fine on Windows 10 latest Build / with coexisting Linux on 2nd NVME.
Failure:
Boots to the cmd screen.
Fix:
Booting from a stick created with “Create Recovery Media) on different PC (HP Workstation) running Windows 10 starts the Recovery Environment. Luckily HP Drivers are compatible and i can access the Backup in the LAN.
PS: removing the Recovery Partition from Disk and Replacing the Recovery Environment from Current ISO Image WINDOWS 11 did not change the unsuccessful boot.
I’m have question about the usb recovery drive. For some reason the recovery will not boot into the bare metal utility, it stops and shows a command window. I’m running latest windows 11 so any thoughts as to why this would be?
thanks
I had the same issue, I created a veeam recovery disk on my old PC and successfully booted into the veeam bare metal recovery with that USB recovery disk.
Hey, i’ve got the same Problem. Windows 11, Veeam Recovery media Boots into command prompt (X:\Windows\System32)
newest Version of Agent and Recovery Media.
tried UEFI and Legacy Boot also with Rufus on different machines
@SchrepfV - there is another user with same issue. For both of you which Windows 11 version are you running? The initial release or an Insider build by chance? If you run WINVER you will get a screenshot of the Windows version screen.
+20
+14
+10
