You can try following this but another option which might work is to use the media creator to do an ISO file then burn that to a USB after with a tool like Rufus.  I always use ISO and then burn it myself to USB for boot as it could be an issue with UEFI vs BIOS boot in your system as well so this utility allows you to create the proper one and burn the ISO image.

Windows Version installed

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.

@Chris.Childerhose

Of course, they can be closed. Free, community and NFR licenses gets only support on best effort. If our support engineers have free capacity, they take on the free cases. 
But if the support load is high, then free cases will be closed after some days.

That‘s why it is important to have a paid license when you backup a production environment. In case of restore issues, you can lose a lot more money if you can‘t restore your data instead of paying a license with guaranteed support. 
 

The forum can help sometimes, but not always. Technical issues should be solved by our support :) If it‘s an environmental problem, then log analysis is required, which cannot be done by the R&D forum.

Completely understand, thanks

This is why preview builds should NEVER be used.

Hi,

I unfortunately do not have another PC to make the media with but I can confirm that all other bootable usb drives that I have made and tested without the Veeam media work fine. Also I have been using the free version of Veeam for years and have made many bootable USB’s with the Veeam media with no problem. Really believe it is an issue with this latest windows 11 update and the Veeam media that is the issue as it was working on this PC before the update. Also it appears that others are having the same issue  with their windows 11 updates and the Veeam bootable media.

I have the same issue with a Dell XPS-9520 and Windows 11 22H2. Did the support find a solution in the meantime? I like Veeam as a backup system for my private windows PC but if it does not work for me any more, I might have to look for other solutions...

I just reproduced the issue on Win 11 22H2 and I can tell you what worked for me: spinning up a VM with Windows 10, installed Veeam Agent in it and creating the recovery media from it passing the USB stick.

Thanks, I tried this and it worked.. little bit of a workaround but at least I have recovery media on usb stick that now works.. Thanks so much

@sekrz

The issue with the recovery medias is confirmed. 

Please see our statement in the RnD forums:

https://forums.veeam.com/post467837.html#p467837

@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.

Windows Version installed

So that is the next release of Windows from the original 22000.xxx.  Not sure if that might be the issue and Veeam needs to update the 5.x agent or wait for the 6.x with v12.

I tested the restore process on 22000.xxx builds and it worked.  I have not yet tested it on this build nor the DEV channel for Insider builds.

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…

Did you use the newest Version of VBR or Agent to create the recovery Media?

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.

Sure there are many more with this issue and can only hope that the next update (6.0) will fix it.

Very nice to see you found the issue and a fix is coming. 

@masterase Windows 11 22H2 is currently not supported by Veeam. It's a known issue that the recovery media doesn't work:

https://forums.veeam.com/servers-workstations-f49/windows-11-22h2-not-officially-supported-by-veeam-t83134.html

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.

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 

I’m running 22621.160, I’m not in the insider build.

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.

Or you have an alternative for backups should the Veeam Agent not work.