About VMs not working in last few insider builds, it would be interesting to see what will happen when spring update is released. If not, that would mean that something is quite different in the system base. VMware and others will have to do some serious adjusting. Methinks it something to do with Sandbox because problems started at same time.
Well, if that were the intent and purpose of *running* any one (or more) of those VM suites, then purpose accomplished!
-------
WRT my comments re: testing:
What I meant was not that you should not be testing them by using them as you would your daily machine. What I meant, and this is something that I've known for almost 40 years of βeta testing software from a wide variety of developers, is this:
You cannot expect everything to work 100% in a βeta test / βeta version of software. And when you do, and more so, when you complain about something being broken, (which, mind you is not the same as reporting an issue), you really don't help the process at all.
Now, let's examine this process. If we look at IP builds, there are 2 levels - slow and fast. Or whatever Dona is calling them this week. Both are still not 'final' release builds, although, in my personal opinion, I'd categorize Fast builds as true βetas, and slow builds as closer to RC (Release candidate). [Yes, the case can be made here that anything not a for RTM is, in fact, an Alpha build, and anything actually RTM is only βeta, but that is a discussion for another time and place]
Going by that analogy, then Skippy (aka Skip Ahead) are αlpha level builds. Taking that tidbit along with the info in the ZDNet article, on what sources inside of M$ have told that reporter / blogger, and you get a clearer picture of "Hey, there's stuff in here that may not work until they get all of the core aligned with each *other AND* their vision."
If something doesn't work in an IP build, and particularly in a slow ring build, there is cause for concern. If something doesn't work in a fast ring build, there is *mild* cause for concern.
If something doesn't work in a Skippy build, guess what - report it and wait for another build - it's expected that something is broken.
There should be almost *no* ulcers being caused / headaches being induced / hair being pulled out when you run a skippy build of this OS. If you get any of those, you really need to take a step back and re-evalutate what you are attempting to run and remember why you should not be at all perturbed.
-------
Now, with that all being said, I run the latest IP / Skippy build as a daily driver on my desktop. I don't advocate it, but I do it. Mainly because my home desktop is, for all intents and purposes (indents and porpoises?) nothing but one big, huge testbed. I have multiple machines that I can reach for to get something done if need be, including desktops, laptops, tablets and even cellphones (yes, plural - my last 2 devices plus my current device all function very well, and all 3 are connected to my Wi-Fi). I can look up answers, talk to other people, check forum posts, all those silly little things we do at home on our 'off-time. And, if I really need to, I'm just a few clicks away from installing the latest version of Windows 10 (stable build, so 1803)back on my desktop if I need to use it for mission critical stuff. But I have work computers for that, so that, really, never comes into play.
@johngalt
I share your view about the Insider Program.
I have currently 2 computers that I use daily. Both are on insider program, but they are both on Release Preview. All the other Rings are running in VMs. The reason my computers never will go full Fast Ring or Skip Ahead, is because one computer is shared among family and the other is running as a VM server and development machine for me.
I used to run Fast Ring on my other computer, but the risk of having a broken system was too big and at that time they were pushing so many builds that most time went into upgrading, so I had to step back a bit.
I'm happy how I have everything setup right now. Once I get a proper Desktop built, I'll move all my VMs there and start using my other Laptop as a full time Insider test bed, meaning I use it most of the time, and switch to the desktop when the Laptop is upgrading or not working properly.
Quote
