Announcing Windows 10 Insider Preview Build 16170 for PC Insider
-
Interesting, for this build I had some minor graphics glitches during setup and on desktop even when running in Hyper-V. Got Green screens and artifacts. Haven't tested the system any further, but I am quite sure it will eventually crash or corrupt something. :)
Something is off in this build.
Running 10.0.16170.1000 directly on the physical hardware is completely out of the question. NVidia driver can not start and system is running really slow even without any significant CPU usage. Processes often crash or consume 50-100% CPU and system eats memory like crazy.
Host OS is Win Pro 10.0.15063.138 and same version does run really well in Hyper-V but 10.0.16170.1000 does not.
Weird...
Updating my VM-WIN10-15063u -> 16170u atm, I'll keep you posted if the same glitches occur in my VM as well.
Cheers
Last edited by M4v3r1ck; 14 Apr 2017 at 08:55.
-
-
Build 16170
I updated my personal laptop early (before the 11th). Using the software download site, I also updated another laptop and two newer desk side and one older desk side systems. Al the updates worked as advertise wit no obvious problems. I was impressed.
WEK
-
I updated my personal laptop early (before the 11th). Using the software download site, I also updated another laptop and two newer desk side and one older desk side systems. Al the updates worked as advertise wit no obvious problems. I was impressed.
WEK
Are you talking about Creators Update (Build 15063.0) or RS Preview (Build 16170.1000)??
As far as I know, there is no other way to download 16170, except via Windows Update for Insiders.
-
Update: New builds 16176 PC and 15204 Mobile soon today.
-
-
Last edited by Brink; 14 Apr 2017 at 11:26.
Reason: added link
-
Interesting, for this build I had some minor graphics glitches during setup and on desktop even when running in Hyper-V. Got Green screens and artifacts. Haven't tested the system any further, but I am quite sure it will eventually crash or corrupt something. :)
Something is off in this build.
Running 10.0.16170.1000 directly on the physical hardware is completely out of the question. NVidia driver can not start and system is running really slow even without any significant CPU usage. Processes often crash or consume 50-100% CPU and system eats memory like crazy.
Host OS is Win Pro 10.0.15063.138 and same version does run really well in Hyper-V but 10.0.16170.1000 does not.
Weird...
16170 runs fine next to the metal here... (But I don't have a laptop, either.) Driver upgrades work much differently for laptops than for standardized desktop components.
IMO, running in a VM is fine if you need to isolate the underlying OS for some critical reason--like you are working with a virus or malware that you want to keep contained, or for some other highly specialized reason--but it won't help much in beta-testing software for a particular hardware set because the VM manager supplies the OS running virtually with *exactly* what it expects/needs in order to function properly. Whether or not your actual hardware & UEFI/bios and device drivers will do the same is an entirely different question, however--and is one that cannot be answered by running a build in a VM--as you have discovered here. That's why I think running new builds in a VM if you own a laptop is probably a good idea--again, as you have discovered. In the early days of Win10 beta testing Microsoft advised use of the VM simply because the initial builds were so unstable they could/would crash the OS and bring it down--I think we are out of those particular woods now, however. But if you own a laptop, then again, maybe not... Caveat Emptor.
-
Update: New builds 16176 PC and 15204 Mobile soon today.
Not that I mind but in all honesty I was not expecting them to release anything this weekend. Cool :)
-
I win! I got it first
-
Yep, right on cue !! Exactly 7PM here.
-
-