New
#240
Last edited by M4v3r1ck; 14 Apr 2017 at 08:55.
Announcing Windows 10 Insider Preview Build 16170 for PC Insider
-
-
New #241
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
-
-
New #243
Update: New builds 16176 PC and 15204 Mobile soon today.
Tweet
— Twitter API (@user) View on Twitter
-
New #244
Just installing 15063.138 on Lumia 640.
Cumulative Update KB4015583 Windows 10 v1703 Build 15063.138 - - Windows 10 ForumsLast edited by Brink; 14 Apr 2017 at 11:26. Reason: added link
-
New #245
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.
-
-
-
-
-
Quote
Related Discussions
