-1

I was attempting to create a Veeam Recovery Media (a rescue disk for a backup app) today. Although it was created, it is unbootable, due to a problem with Windows RE, that is used to run this bootable disk. Later, I created a new USB Windows Rescue Disk from a scratch with my Windows 10, to check if the problem persists. Unfortunately, it doesn't work indeed. The symptoms are the same: the Windows RE disc can not be launched. While booting from a rescue disc, I received BSoD saying that the operating system couldn't be loaded because the kernel is missing or contains errors.

File: \windows\system32\ntoskrnl.exe Error code: 0xc000a004

I want to underline that the computer works fine so far, and I don't see any distressing symptoms. Windows boots each time normally.

I will appreciate any help in resolving the problem. enter image description here

Ramhound
  • 44,080
gordom
  • 69

1 Answers1

0

Though I've never used that tool before, there are a plethora of free reputable Windows recovery tools using Windows RE, such as Macrium Reflect Rescue Environment, EaseUS Rescue Media, Hiren's BootCD PE x64.

During the creation of the Windows RE recovery media, a WIM file containing all the "innards" of Windows RE is constructed. Evidently, Veeam Recovery Media is not building that WIM correctly. Rather than trying to troubleshoot that application, just use another Win RE builder. For example, Macrium Reflect downloads all needed files to build the WIM at the time the media is created, if the WIM has not been built before, or if you wish to change it.

Build WIM in Macrium Reflect

Note that the default base WIM is downloaded from Microsoft's Windows Kits, if not already present.

DrMoishe Pippik
  • 37,887