Fair enough... but releasing a build that precludes a specific CPU is premature IMHO... surely beta builds need to garner info from the broadest spectrum?

Totally agree with that and I posted a similar comment on another thread on the forum regarding the aMD problem. I got replies telling me that this was only to be expected and I should realise that this was only a beta build.
For me a build that doesn't work with a particular CPU isn't a beta build, it's Pre Alpha.

My ComputerYou need to have JavaScript enabled so that you can use this ...

Totally agree with that and I posted a similar comment on another thread on the forum regarding the aMD problem. I got replies telling me that this was only to be expected and I should realise that this was only a beta build.
For me a build that doesn't work with a particular CPU isn't a beta build, it's Pre Alpha.

I agree. The AMD fiasco was probably a low point. I seriously doubt that will happen again. Hope I don't have to eat my words.

My ComputersYou need to have JavaScript enabled so that you can use this ...

I was trying to be literal. I don't think that Microsoft will release another insider preview that would leave numbers of testers in such a predicament. I admit that is more hopeful than I usually would be
There is one AMD/Intel incompatibility that irritates me. That is that nested Hyper-V machine (running Hyper-V inside a Hyper-V VM) is only allowed on newer Intel chips.

My ComputersYou need to have JavaScript enabled so that you can use this ...

I was trying to be literal. I don't think that Microsoft will release another insider preview that would leave numbers of testers in such a predicament. I admit that is more hopeful than I usually would be
There is one AMD/Intel incompatibility that irritates me. That is that nested Hyper-V machine (running Hyper-V inside a Hyper-V VM) is only allowed on newer Intel chips.

There is a difference between only allowed and only possible. Hell if you use old chips, you cannot even use Hyper-V on host. That's life!

Last edited by cereberus; 02 Dec 2017 at 03:07.

My ComputerYou need to have JavaScript enabled so that you can use this ...

I was trying to be literal. I don't think that Microsoft will release another insider preview that would leave numbers of testers in such a predicament. I admit that is more hopeful than I usually would be
There is one AMD/Intel incompatibility that irritates me. That is that nested Hyper-V machine (running Hyper-V inside a Hyper-V VM) is only allowed on newer Intel chips.

Such a predicament maybe not, but they announced other "predicaments" with limited number of insiders.

My ComputersYou need to have JavaScript enabled so that you can use this ...

Totally agree with that and I posted a similar comment on another thread on the forum regarding the aMD problem. I got replies telling me that this was only to be expected and I should realise that this was only a beta build.For me a build that doesn't work with a particular CPU isn't a beta build, it's Pre Alpha.

I absolutely agree with this statement!

But it makes me wonder what drastic changes the devs has made to cause these issues. I bet they have re-enabled some ancient kernel code for some new and exciting features, like they did for the Linux Subsystem.

My ComputersYou need to have JavaScript enabled so that you can use this ...

But it makes me wonder what drastic changes the devs has made to cause these issues. I bet they have re-enabled some ancient kernel code for some new and exciting features, like they did for the Linux Subsystem.

I think it may have something to do with adjusting to new and coming AMD processors which are all new ballpark and all are not definitively defined yet.

My ComputersYou need to have JavaScript enabled so that you can use this ...

About Us
Windows 10 Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows 10" and related materials are trademarks of Microsoft Corp.