Forum Discussion
We all know...
Speaking of testing Windows and Edge Insider releases on a VM, as you said its more rational approach from reliability and OS "polluting" standpoint. I add - from Privacy standpoint too. At this stage Edge Chromium is likely to "telemetry" home a lot more often than Win 10 does, despite the latter being a proclaimed "chatter".
So using Edge Insider as a daily internet driver is a questionable tactics for some privacy cautious users. Speaking of testing on a VM, another known drawback is filtered interaction with PC hardware, making some tasks like video playback less pleasant and less reliable to test.
Possibly the better approach is using a dedicated PC to test Windows and Edge Insider releases, making sure you don't touch private sides of your life at testing if possible.
sambul95
Sam, yes there are pros & cons to the vm approach. We, always, tell Folks run betas as dual boots, on a spare box or on a vm. In my case, beta testing since Vista, have used every way at some point over the years. One nice thing about the vm route ( yes there are short-comings, too) is being able to 'see' both the vm & the host machine at the same time or go back & forth quickly & easily. With Win10 it's made it easy to compare current installs to Insider Builds. And the fact that if anything does go awry, no harm done to anything outside the testing platform. And if the vm, the OS on it, really goes awry, just toss it & create a new vm. Certainly, we all know Enterprise IT rely heavily on virtual for testing before deploying.
Cheers,
Drew