Veeam recovery media fails to start - Windows 10

[matthewr]

Hi there,

I find the Veeam Recovery Environment fails to start, when the Recovery Media has been created with Windows 10. However, Recovery Media that was created using Windows 8 functioned normally.

When booting from the USB disk containing the Recovery Media, a Windows command prompt starts (at X:\windows\system32). But the Veeam Recovery Environment never starts. A screenshot is here: https://imgur.com/a/uuwxCLJ

Things I have tried:
- using cmd to navigate to Veeam.Endpoint.Recovery.exe and running it - it does not start
- looking for log files - could not find any
- creating the Recovery Media without adding hardware drivers - no difference
- creating the Recovery Media by burning it directly to a USB stick, or making an ISO and imaging to the USB stick later (with Rufus) - no difference
- using Recovery Media created using Windows 8 - this works fine

The context is:
- Dell XPS 13 L322X
- Windows 10 Home (version 1903)
- full disk encryption with VeraCrypt
- latest Veeam Agent for Windows 3.0.1.1039 Free Edition

Many thanks in advance for your help,
Matthew

[wishr]

Hi Matthew,

Welcome to Veeam Community Forums and thanks for posting!

VeraCrypt may be causing this behavior, but not 100 sure... Have you had a chance to discuss this situation with our support team? If so, what's your support case ID?

Please note that you should include a support case ID when posting about any technical issue, according to Forum Rules.

Thanks

[wishr]

Dear Matthew,

Just spoke to VAW QA team. It's a known issue that will be fixed in the next version. As of now, please reach out to our support team to get a solution.

Thanks

[matthewr]

Thanks wishr. My support case ID is 03589686.

[tinkererguy]

Just an FYI, same issue, any bootable recovery media I create using Veeam Agent for Windows 3.0.1.1039 Free Edition from Windows 10 1903 has the same issue Matthew reported. Creating it from Windows 8.1 works fine.

[DeadEyedJacks]

Ditto Veeam Agent v3 recovery media created post Windows 10 1903 update goes to an X:\ command prompt.

[jwood.ok]

I have the same issue - was attempting from Win 10 1903. If I made recovery media from Windows 10, say 1809 on a machine with the same hardware, would it still work? or does it even matter where I make the recovery media, as long as it isn't on this machine where it just comes up with a cmd line?

[Gostev]

All, Windows 10 1903 is not yet supported, and Recovery Media creation is specifically one of the issues to be addressed. We're planning to ship version 3.0.2 with the official support before the end of this month. Thanks!

[stefaanvanderbeeken]

Any updates about the fix? We use the free version for all our standalone pc's. Without working recovery media this tool is unusable for stand alone pc's.

[wishr]

Hi Stefaan,

First, welcome to Veeam Community Forums and thanks for posting.

Please refer to the post by Gostev above - it answers your question. The update will be released very soon .

Thanks

[agreimann]

I'm seeing the same error with Windows 10 Pro 1809. This post suggest the issue is limited to 1903

[wishr]

Hi Alex,

Have you already discussed this situation with our support team? If so, what's your case ID?

Thanks

[matthewr]

Any indication of when 3.0.2 will be released? I'm still on 3.0.1.1039 (Free Edition). Have checked for updates just now. Thanks.

[wishr]

Hi Matthew,

It's coming very soon, stay tuned!

Thanks

[stvajnkf]

May I consider "soon" the end of the month?

[Mquadrat]

Soon should bei today!
End of month is still to long for such an important fix!

[Vitaliy S.]

Marvin, you can obtain 3.0.2 bits through our support team today. Thanks!

[JMcG26]

Vitality, I opened a support ticket #03661144 asking for a download link.

Can you just post a link for everyone here?

[Vitaliy S.]

Currently, VAW bits can only be obtained by contacting the support team, but we are planning to make it generally available to everyone soon.

[GolanTrevise8]

Vitaliy, just curious, what is a VAW bit?

[Vitaliy S.]

Veeam Agent for Windows (VAW)

[moabrunner]

Any update on the release? I have several PC's that are already on 1903 and ESET cause some major issues with the same update. I was unable to do a bare metal restore because of this issue, wasted may hours having to reinstall windows 10 because it would not let me remove the update.

[wishr]

Hi Shane,

Welcome to Veeam Community Forums!

Per latest digest by Gostev: "Update 4b for Veeam Backup & Replication 9.5 has been downloaded close to 4000 times now, and things are still looking good thus far - so we're planning to make both the update and standalone agents generally available for download from our website this week."

As of now, updates for Veeam Agents can be obtained through our support team.

Thanks

[agreimann]

Will the updates be posted this week?

[tapeterson]

It appears the new version of recovery media only allows the selection of .vbm files without the ability to select a .vbk. I have a .vbk on an external disk, booted with the new recovery media, which loads fine, but... I can't simply select my .vbk. I'm using backup media from another system. I just want to be able to bring up the recovery disk and select any .vbk and do a full restore if it's what I want.

[wishr]

Hi everyone,

@tapeterson, currently such scenarios are not supported (the same was before in the previous versions - no changes in this term) since .vbk does not store any metadata. This metadata is required for certain recovery operations including restore from recovery media.

Is there any specific reason explaining why you do not have a .vbm in the chain?

What you might want to do if your machine is alive with Agent installed is: deploy a VBR server, connect the Agent to this server, put your .vbk to the VBR repository and restore from it.

Will the updates be posted this week?

It has been already posted.

Thanks

[MEEMxyz]

Just in case it was not clear (it was not clear for me):

1) The issue is that Veeam Backup Agent 3.0.1 does note create a good Recovery Image in Windows 10 19.03.
2) You can NOW download 3.0.2 in the Veeam website. For some reason the "auto update" is not working and states "there is no new version". I manually downloaded 3.0.2, and upgraded.
3) Now the Veeam Recovery Media works PERFECT.

Hope this quick summary helps!

[tapeterson]

Hi everyone,

@tapeterson, currently such scenarios are not supported (the same was before in the previous versions - no changes in this term) since .vbk does not store any metadata. This metadata is required for certain recovery operations including restore from recovery media.

Is there any specific reason explaining why you do not have a .vbm in the chain?

What you might want to do if your machine is alive with Agent installed is: deploy a VBR server, connect the Agent to this server, put your .vbk to the VBR repository and restore from it.



It has been already posted.

Thanks

Yep, sorry my mistake on this. In the filename I enter a *.vbk wilcard, it lists the vbk and with the vbm in the directory it restores perfectly. Thanks.

[it@ott.co.za]

Hi everyone,

I have the same problem, was this issue resolved?
Problem Recovery media booting up with the command prompt x:\

[MEEMxyz]

Download Version 3.0.2 from Veeam Backup website into the system you want to use to create the Recovery Media, and it is now working fine.
The Automatic Update is not working to update the Agent from 3.0.1 to 3.0.2 for some reason yet.