New
#80
Opps..
In viBoot Options, what path is set for VM Repository? [C:\ProgramData\Macrium\viBoot]
Opps..
In viBoot Options, what path is set for VM Repository? [C:\ProgramData\Macrium\viBoot]
@DarHorse
I contacted Macrium about this issue of yours, seems that although it works in my tests with Windows XP images, there's something in viBoot that occasionally causes issue like yours with XP images.
The answer from Macrium in all its simplicity was "We have just become aware of this issue ourselves and we will be releasing a fix ASAP."
Let's wait a bit and give geeks at Macrium a chance to fix the bug :)
I have been using Hyper-V to run a Linux VM for a while now with no issues and saw this tutorial to mount old backups.
I am using Macrium free v6.3.1835.
I installed the viBoot as in the tutorial, mounted a VM from one of my old backups, so seemed to work. This was on 8/13. Just more as curiosity than anything else.
Today I was in the Hyper-V manager and noticed the VM from viBoot, and decided I was done with it, and just deleted.
Now I can't uninstall viBoot.
Thinking I maybe messed it up by deleting from Hyper-V manager, I then checked on my system image backup, to see if I could just restore from my daily 6:00 am backup from before I messed it.
That is when I see that my daily system image (Macrium) has been failing since the day I installed the viBoot.
No notification from Macrium Reflect, so word of warning, if you don't go into Macrium daily and check your logs, you will not notice it is failing. But any way, my latest backup is the one just prior to installing the viBoot. so restoring the image to earlier today is not an option now.
Can anybody give me a suggestion on how to remove viBoot? I am concerned that my system might be unstable now with this extra drive?
I went in disk manager and saw that it had a disk 9 with a SCSI driver the same size as my C: Drive that wasn't connected properly, so I disable it, but still have the problem.
EDIT: I solved it finally, what I think finally worked: In the viBoot, it showed the "Deleted VM". I deleted the deleted vm, and then it let me uninstall.
Last edited by IsaacFL; 23 Aug 2017 at 14:35. Reason: Solved
NoteA Macrium Special at TF Saturday Live Chat on April 28th, 2018:
Read more: Welcome to TF Saturday Live - The Macrium Special Solved - Windows 10 Forums
OK geeks, first of today's three webcasts online, start in less than half an hour. Join us: TF Saturday Live - The Macrium Special Part 1
Read more: Welcome to TF Saturday Live - The Macrium Special - Windows 10 Forums
Second of today's three webcasts online, start in less than half an hour. Join us: TF Saturday Live - The Macrium Special Part 2
Read more: Welcome to TF Saturday Live - The Macrium Special Solved - Windows 10 Forums
OK geeks, the main event, third and last of today's three webcasts starting in half an hour. Our special guest, Macrium founder and CEO Nick Sills will tell about Macrium Reflect and answer your questions in Q&A.
Join the webcast, we are already online: TF Saturday Live - The Macrium Special Part 3
Read more: Welcome to TF Saturday Live - The Macrium Special Solved - Windows 10 Forums
Just read the guide on Page 1. I have a large external disk where I store my Macrium backups.
With ViBoot, can I install the image on ANY drive (as my C Drive is small (ish)?
Also, have I understood correctly that running the Virtual Machine does not affect at all the main C Drive system? So, I could as example download an ISO an apply it only to the VM, without affecting my main C Drive Windows 10 system (testing Skip Ahead versions)? (I presume I would have to download it within the VM to apply it??)
Sounds very interesting if that's the case.