-
- Influencer
- Posts: 15
- Liked: 3 times
- Joined: Apr 13, 2015 8:38 am
- Full Name: Keith Drayton
- Contact:
Endpoint Recovery to VM - VCRuntime140_CLR0400.dll is missing
I have a image of a machine created using Endpoint (free version) and have been attempting to put it into a VM,
Image was taking a month or so ago before the machine was wiped and upgraded to Windows 10, We now find our selfs missing a setting for a piece of software, Thought the simple option would be fire up the image and check it on there,
I have carried out the following steps in both our VMWare Vsphere server and Hyper-V on a windows 10 laptop with same results.
First attempt - Convert the image to VMDK \ VHD, Create new VM with this disk and boot
Windows 7 gets stuck in a boot loop.
Second attempt - Full Endpoint recovery, Mount the recovery ISO and boot a blank VM from it,
On both Vmware & Hyper-Vim getting the following error before i get to the recovery console
The program cant start because VCRUNTIME140_CLR0400.dll is missing from your computer, Try reinstalling to fix this problem.
I was sure i had done this before and have seen articles on line demonstrating it but im getting this error from several recovery ISO from different systems,
Anyone have any ideas on this?
Thanks
Image was taking a month or so ago before the machine was wiped and upgraded to Windows 10, We now find our selfs missing a setting for a piece of software, Thought the simple option would be fire up the image and check it on there,
I have carried out the following steps in both our VMWare Vsphere server and Hyper-V on a windows 10 laptop with same results.
First attempt - Convert the image to VMDK \ VHD, Create new VM with this disk and boot
Windows 7 gets stuck in a boot loop.
Second attempt - Full Endpoint recovery, Mount the recovery ISO and boot a blank VM from it,
On both Vmware & Hyper-Vim getting the following error before i get to the recovery console
The program cant start because VCRUNTIME140_CLR0400.dll is missing from your computer, Try reinstalling to fix this problem.
I was sure i had done this before and have seen articles on line demonstrating it but im getting this error from several recovery ISO from different systems,
Anyone have any ideas on this?
Thanks
-
- Product Manager
- Posts: 14726
- Liked: 1706 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Endpoint Recovery to VM - VCRuntime140_CLR0400.dll is missing
Hello Keith,
Can you please clarify if it's possible to boot the resulting VM in the safe mode? Thank you!
Can you please clarify if it's possible to boot the resulting VM in the safe mode? Thank you!
-
- Influencer
- Posts: 15
- Liked: 3 times
- Joined: Apr 13, 2015 8:38 am
- Full Name: Keith Drayton
- Contact:
Re: Endpoint Recovery to VM - VCRuntime140_CLR0400.dll is missing
Hi Dima
If i carry out a conversion of the image to disk and add that to a VM it fails to boot in safe mode either, Again end up with a boot loop.
I have other ways of getting the information i want to start this image up for but now i also want to get it working to ensure its OK.
I dont currently have any real hardware i can restore to for testing so cant say if i have an image problem or VM problem.
Thanks
If i carry out a conversion of the image to disk and add that to a VM it fails to boot in safe mode either, Again end up with a boot loop.
I have other ways of getting the information i want to start this image up for but now i also want to get it working to ensure its OK.
I dont currently have any real hardware i can restore to for testing so cant say if i have an image problem or VM problem.
Thanks
-
- Influencer
- Posts: 15
- Liked: 3 times
- Joined: Apr 13, 2015 8:38 am
- Full Name: Keith Drayton
- Contact:
Re: Endpoint Recovery to VM - VCRuntime140_CLR0400.dll is missing
So about a month on from running into this problem that i had assumed was trying to recovery a physical machine backup from the agent to a VM i wanted to try it with another PC,
Recovery media created, ISO and direct to USB,
Agent backup runs fine on the physical PC,
Any attempt to recover to a VM fails with
The program cant start because VCRUNTIME140_CLR0400.dll is missing from your computer, Try reinstalling the program to fix this problem,
So this time after trying a couple different options to get a working VM i decided to head back to the original physical hardware and boot the recover USB, To my surprise im getting the same error so it appears to have nothing to do with recovering to VM and something to do with the recovery media its self,
Im running Agent version 3, I think there is an update available, Tomorrow i will update and create new media and see if that fixes the issue,
When recovering to original hardware i have not run into this before but have always been on earlier versions, I think these errors have only been with Agent version 3,
Anyone have any suggestions?
Thanks
Recovery media created, ISO and direct to USB,
Agent backup runs fine on the physical PC,
Any attempt to recover to a VM fails with
The program cant start because VCRUNTIME140_CLR0400.dll is missing from your computer, Try reinstalling the program to fix this problem,
So this time after trying a couple different options to get a working VM i decided to head back to the original physical hardware and boot the recover USB, To my surprise im getting the same error so it appears to have nothing to do with recovering to VM and something to do with the recovery media its self,
Im running Agent version 3, I think there is an update available, Tomorrow i will update and create new media and see if that fixes the issue,
When recovering to original hardware i have not run into this before but have always been on earlier versions, I think these errors have only been with Agent version 3,
Anyone have any suggestions?
Thanks
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Dec 09, 2019 12:04 pm
- Contact:
Re: Endpoint Recovery to VM - VCRuntime140_CLR0400.dll is missing
Hey,
Did you ever find a solution to this? I'm just trying to do a BMR using the boot disk and it's throwing up the same error message about VCRUNTIME140_CLR0400.DLL being missing.
Many thanks.
Did you ever find a solution to this? I'm just trying to do a BMR using the boot disk and it's throwing up the same error message about VCRUNTIME140_CLR0400.DLL being missing.
Many thanks.
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Aug 27, 2020 9:29 pm
- Full Name: Arick Severson
- Contact:
Re: Endpoint Recovery to VM - VCRuntime140_CLR0400.dll is missing
A workaround that solved this issue for our instance was using a Windows generated recovery media instead of the Veeam created recovery media.
We used Veeam for the backup and restore successfully, which was great since Windows and other imaging software repeatedly failed backing up the drive. It was frustrating to receive this error so close to completion. If I had to guess, the Veeam recovery media needed the dll to run, but the Windows recovery media did not. Before backing up, I tried replacing both dll files in the system folders and also used the repair function of the Microsoft Visual C++ Redistributable but neither solved the issue.
We used Veeam for the backup and restore successfully, which was great since Windows and other imaging software repeatedly failed backing up the drive. It was frustrating to receive this error so close to completion. If I had to guess, the Veeam recovery media needed the dll to run, but the Windows recovery media did not. Before backing up, I tried replacing both dll files in the system folders and also used the repair function of the Microsoft Visual C++ Redistributable but neither solved the issue.
-
- Product Manager
- Posts: 14726
- Liked: 1706 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Endpoint Recovery to VM - VCRuntime140_CLR0400.dll is missing
Arick,
Any change you have a case with our support team? If I remember correctly this issue can be addressed by the agent re-installation (including entire set of prerequisites). Cheers!
Any change you have a case with our support team? If I remember correctly this issue can be addressed by the agent re-installation (including entire set of prerequisites). Cheers!
Who is online
Users browsing this forum: Semrush [Bot] and 12 guests