Boot media created with Windows 1809 does not work

[Norm24]

Case # 03536238 / Using Windows Version 1809

Hi I have a similar problem as described ...

My Recovery Media not completing Boot to menu. I get a cmd type window on VEEAM Green background with x: \windows\system32 and flashing cursor.
Veeam Agent 3.0.1.1039

My PC is ...
ASUSTeK COMPUTER INC. PRIME Z270-K
Microsoft Windows 10 Pro (64-bit)
Intel® Core™ i5-7600K CPU @ 3.80GHz
Intel® HD Graphics 630
NVMe INTEL SSDPED1D28 PCIE C: Drive

I created the Recovery Media direct to USB - with/without the Network Connections / Hardware Drivers tick boxes ticked.

I tried ...
2x different USB sticks / Different USB2/3 ports
Uefi Secure Boot on/off
USB Boot Uefi and Legacy selected

I had a 2017 Recovery Disc so I created an .iso and using 'Rufus' created a bootable USB stick.

This worked!
About 38" to get "Recovery Environment Initialising" message
Until about 51" to get the Veeam menu on green background
I would very much appreciate any help with this as my Disaster Recovery arrangement is depending on this 2017 Recovery Media.

Cheers Norman

[HannesK]

Hello,
and welcome to the forums.

It's good, that you opened a case. Please continue working with support.

One question: what do you mean with "2017 Recovery media"?

Best regards,
Hannes

[Norm24]

Hi Hannes,
The "2017 Recovery media" was a disc made in 2017 when I first installed Veeam Agent for Windows. This disc was made on previous hardware so I am surprised that it worked!
Thanks Norman

[Norm24]

Further just to say that I have received support after opening a case.
I was sent an iso file via ftp which I downloaded and used "Rufus" to burn onto a USB key.

This worked first time!

Entering # produced a \ so entering passwords was interesting .... the .iso was for an American keyboard. I am in the UK so the support staff re-sent an iso with UK character set.
All good! Recovery environment booted in 30" ready to go.
The iso I was sent does not include decryption key/Network support or hardware drivers.
Was my hardware/software an isolated case or will Veeam make adjustments in the next Windows Agent Recovery Media release?

Very helpful and prompt support ... Well Done!

Norman.

[rcabrera]

Case #03599975

Hello. I am going through the same situation in that I had created a recovery disk a week or so ago and then yesterday updated Veeam Endpoint did a full backup and replaced an M.2 SSD which now is producing that same CMD window on VEEAM Green background with x: \windows\system32 and flashing cursor.

[Dima P.]

Robert,

The recovery media was created from the machine you are restoring? Can you go to BIOS properties and check what boot mode is set for your machine (i.e. UEFI or legacy BIOS)? Thanks!

[matthewr]

This sounds similar to my issue (link below, case #03589686), the only difference is I was using Windows 10 Home build 1903 not 1809.

It was suggested in that thread that this issue would be fixed in the next release of Veeam.

veeam-agent-for-windows-f33/veeam-recov ... 59691.html

[Dima P.]

Thanks Matthew!

Indeed there is a problem with recovery media creation for Windows 10 1903 but it's related only to this specific build, so I assume Robert is having different problem.

[matthewr]

Thanks for clarifying!

[DeadEyedJacks]

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

[DeadEyedJacks]

Also worth noting that Recovery Media no longer fits onto a CD , DVD or USB required

[Dima P.]

worth noting that Recovery Media no longer fits onto a CD , DVD or USB required

Any chance you've added additional drivers to the recovery media? Thanks!

[Nick-SAC]

FWIW, The VAW 3.0.1.1039 Win10 1809 Recovery Media ISO I just created is 735 MB (with WiFi Drivers) whereas the Win7 and Server 2008-R2, 2012-R2 and 2016 ISOs range from 300 to 500 MB

Personally I don’t see this as an issue since I prefer using Flash Drives anyway and (other than for some special systems) I just keep the ISOs on the Backup Server Repos and use Rufus to create the Bootable Flash Drives as needed.

Also FWIW, I had no problem Booting the 1809 system (Lenovo Laptop UEFI) from a USB Flash Drive Recovery Media created directly (not ISO to Flash) with the VAW.

[Dima P.]

Thanks for confirmation Nick! Recovery Media components are very light weight (thanks to Windows RE engine), however sometimes due to hardware drivers being included in can consume more space.

[Alan_ORiordan]

I am using the latest Veeam Endpoint release as of 10/7/19 - 3.0.1

The PC I am trying to restore to is Windows 10 1809

The iso file was created on the PC before swapping out to an SSD

I used Rufus to created a GPT bootable USB key, it still boots to the command prompt just like the bootable DVD did only faster

[Nick-SAC]

In light of Alan’s above result ( which unnerved me ) I just repeated my test but this time by creating the Recovery Boot USB Flash Drive from an ISO (instead of Directly to Flash using VAW) and it too worked flawlessly.

Test System:
Windows 10 1809 (Lenovo Laptop SSD UEFI GPT)
VAW 3.0.1.1039 (used for the Backup and to create the Veeam Recovery Media ISO)

Recovery Boot Flash Drive created on a Win7 Pro x64 box using:
Rufus 3.1.1320 (Portable)
Partition Scheme: GPT
Target System: UEFI (non CSM)
File System: FAT32 (Default)
Cluster Size: 8192 bytes (Default)
Advanced Drive Properties: None Selected

Could it be that Alan’s problem is that his Recovery Media ISO was created with a HDD installed but he’s now trying to Boot it with an SSD installed?

[GolanTrevise8]

Case # 03658691
Testing boot media created on Windows 10 Pro 1803. Tried both DVD and USB stick. Same result on both. They boot to the recovery menu with no mouse pointer and keyboard does not respond.

[Dima P.]

Dan,

Please keep working with our support team as it looks like an input device driver issue. Cheers!

[Dungbeetles]

Check your USB,how many gb is it?And how did you get Windows iso?As i dont think Rufus has a problem with creating boot media.

[Dungbeetles]

Get 2 programs for this problem:
https://rufus.ie/
https://www.uubyte.com/
Creating a bootable disc with them.