Group: Forum Members
I'm getting lots of "You need to format the disk ..." errors. The Windows dialog box says I need to form E, F, G or whatever. The Hyper-V BIOS screen appears and a message says "No operating system found." No viboot error at all.
I believe I have two explanations - maybe.
1. Seems like I got the error once when I didn't have enough free space on C drive. The image file is on D drive. Apparently there's significant space needed on C drive? After guessing the issue was lack of free space on C drive, I cleaned up and got farther.
2. Most of my machines run Windows Insider builds. There's been no problem with Macrium Reflect - thank you. However, viboot seems to whitelist Windows 10 and throws a critical error if you are using a Windows version higher than RTM.
Logging initialized for viBootDate Time Level TID File Line Function Description
02/03/2017 21:45:43.0380 3616 Logging started
02/03/2017 21:45:43.0518 Critical 3616 viBoot.cpp 746 CVirtualImageBootApp::InitInstance Detected Windows version 10.0.14393 (SP0)ati
My expectation is:
1. viboot will run on Windows Insider builds. Afterall, that's a MAJOR use case for Reflect and viboot. They're my insurance against a bad beta.
2. I expect better error reporting. A failure due to lack of disk space or non-whitelisted OS should be reported as a dialog box or such. It shouldn't silently fail. If the log file shows the reason, it should be presented to the user UI.