Quote:
Originally Posted by JSWolf
But running a pre-release OS under a VM is not a good idea. 99.9% of the people using Windows 10 will be doing so without a VM. So because you don't know if the VM is the problem or not, don't say there is a problem with Windows 10 pre-release. Run it without a VM and if it till doesn't work, then say it's not working.
|
Umm... I have a couple of physical machines at work with various Insider Preview Builds. The same issue has occurred with them. I have not seen a similar issue with with Windows 7 and 8.1 nor with Linux (Fedora, CentOS and Mint) on a VM on my laptop. The issue with with Windows 10 Insider Builds has come and gone with various builds. I should mention that I've seen that issue with HyperV VMs as well as VMWare Workstation.
So I am fairly certain that it is a Windows 10 Insider Preview Build issue but there is a niggling doubt that it might be a VM issue.
As for not running the Windows 10 Insider Preview Builds using VMs? About 40% of the people I know who are running Insider Preview Builds run them using VM technology. It is just so much easier to revert from a failed install -- an example was where Build 14431 bluescreened my VM during install. I reverted to the previous snapshot and moved to the Slow Ring until the next build was released. That beats the heck out of re-installing the OS and applications.