Hello,

I'm using ViBoot with VirtualBox and I created a full image "test" backup on my second M.2 drive. However, when I try to use it I get this pop up:



The strange thing is that if I click OK, it gives me the options to create the VM, I change the memory and it boots fine. It's like it's a false warning?

I tested an full image from my main external backup drive and I get the same thing. Am I missing something incredibly obvious, or is it a bug? It's not very reassuring to see that, even though everything seems to be working as it should.

Thanks in advance for any help.

Can you post a screenshot showing the partitions contained in one of these full images that you have tested?

                                

Hello, JK,

Yes, sure, here is my "test" image, the backups on my external drives contain the same partitions:



I have used the same definition files for a long time. Here is a screenshot of my local disk as if I were to "Image this disk" they do match:



Edit: I should probably add I'm on the latest version v8.0.6560

Edit #2: Sorry, not trying to nag people on this, but I've been thinking, I had previously contacted support because I was having a lot of issues with BSODs using viBoot/VirtualBox, and it was recommended to add some registry tweaks, which did help with the crashes, but could they also be causing this error? The registry settings were:



Is anyone able to confirm or deny this? That is the only noticeable thing I've changed. I'm not sure what the default values for those settings are, or should I be contacting support directly about this?

Many thanks.

Has this issue ever been solved? I did not see anything related in the release notes. I just got the same error using v8.1.7401 with two different images/systems I used viBoot for (on the same host computer). I too can adjust the VM and start it, even though I always get this error message. It happens with both VirtualBox and Hyper-V.

+x

 

Pim - 21 March 2023 5:35 PM

Has this issue ever been solved? I did not see anything related in the release notes. I just got the same error using v8.1.7401 with two different images/systems I used viBoot for (on the same host computer). I too can adjust the VM and start it, even though I always get this error message. It happens with both VirtualBox and Hyper-V.

Hello, yes this was fixed version v8.0.6635 4th March '22. I have not had the issue since so it's strange you are getting it:

+x

 

HallsOak - 21 March 2023 5:49 PM

+x

 

Pim - 21 March 2023 5:35 PM

Has this issue ever been solved? I did not see anything related in the release notes. I just got the same error using v8.1.7401 with two different images/systems I used viBoot for (on the same host computer). I too can adjust the VM and start it, even though I always get this error message. It happens with both VirtualBox and Hyper-V.

Hello, yes this was fixed version v8.0.6635 4th March '22. I have not had the issue since so it's strange you are getting it:

Thank you for your prompt reply. I must have overlooked that one. Yes, very strange that I am getting the same error with v8.1.7401. I only upgraded from v7.3.6391 to v8.0.7097 last November, but had participated in the viBoot v8 beta program. Like you mentioning the registry changes you made, I am now starting to wonder whether that might have something to do with it? I have not used viBoot much, I used it a couple of weeks ago and I think (but am not completely certain) that I did not get an error that time. That must have been with v8.0.7175.

+x

 

Pim - 21 March 2023 6:17 PM

+x

 

HallsOak - 21 March 2023 5:49 PM

+x

 

Pim - 21 March 2023 5:35 PM

Has this issue ever been solved? I did not see anything related in the release notes. I just got the same error using v8.1.7401 with two different images/systems I used viBoot for (on the same host computer). I too can adjust the VM and start it, even though I always get this error message. It happens with both VirtualBox and Hyper-V.

Hello, yes this was fixed version v8.0.6635 4th March '22. I have not had the issue since so it's strange you are getting it:

Thank you for your prompt reply. I must have overlooked that one. Yes, very strange that I am getting the same error with v8.1.7401. I only upgraded from v7.3.6391 to v8.0.7097 last November, but had participated in the viBoot v8 beta program. Like you mentioning the registry changes you made, I am now starting to wonder whether that might have something to do with it? I have not used viBoot much, I used it a couple of weeks ago and I think (but am not completely certain) that I did not get an error that time. That must have been with v8.0.7175.

For what it's worth, I am also using Macrium Home - v8.1.7401, I am also using an older version of VirtualBox 6.1.34 https://www.virtualbox.org/wiki/Download_Old_Builds_6_1  I know there was an issue with VirtualBox 7.0 so I rolled back. That is now fixed according to release notes. Plus, I don't use viBoot as much now as I did at the time so have not updated in a while. I don't think the issue was with VirtualBox though, but you could test the older version?

Edit: link broken

+x

 

HallsOak - 21 March 2023 6:40 PM

+x

 

Pim - 21 March 2023 6:17 PM

+x

 

HallsOak - 21 March 2023 5:49 PM

+x

 

Pim - 21 March 2023 5:35 PM

Has this issue ever been solved? I did not see anything related in the release notes. I just got the same error using v8.1.7401 with two different images/systems I used viBoot for (on the same host computer). I too can adjust the VM and start it, even though I always get this error message. It happens with both VirtualBox and Hyper-V.

Hello, yes this was fixed version v8.0.6635 4th March '22. I have not had the issue since so it's strange you are getting it:

Thank you for your prompt reply. I must have overlooked that one. Yes, very strange that I am getting the same error with v8.1.7401. I only upgraded from v7.3.6391 to v8.0.7097 last November, but had participated in the viBoot v8 beta program. Like you mentioning the registry changes you made, I am now starting to wonder whether that might have something to do with it? I have not used viBoot much, I used it a couple of weeks ago and I think (but am not completely certain) that I did not get an error that time. That must have been with v8.0.7175.

For what it's worth, I am also using Macrium Home - v8.1.7401, I am also using an older version of VirtualBox 6.1.34 https://www.virtualbox.org/wiki/Download_Old_Builds_6_1  I know there was an issue with VirtualBox 7.0 so I rolled back. That is now fixed according to release notes. Plus, I don't use viBoot as much now as I did at the time so have not updated in a while. I don't think the issue was with VirtualBox though, but you could test the older version?

Edit: link broken

Because it also happens with Hyper-V I do not think it is related to the version of VirtualBox. Therefore I did not try an older version. I had just updated to v7.0.6 because I thought the old v6 I still had installed was perhaps to blame.

I just also tried v8.0.7175 and with that version I get the error message too, so my memory failed me there. I then also tested an image of an UEFI installation, because the first two were both images of MBR installations. That one too resulted in the "No bootable drive detected" message.

I do not know what to do now and it seems others get no error message when using v8.1.7401. Fortunately, despite the error message I can use viBoot just fine, but I still would like to see this solved.

I tested using viBoot on another machine and on that machine I do not get the "No bootable drive detected" message. I then uninstalled Macrium on the affected machine, keeping all settings, and installed v8.1.7401 again. The error persists unfortunately. Hopefully somebody from Macrium can chime in.