Announcing Windows 10 Insider Preview Build 16170 for PC Insider

CountMike · 08 Apr 2017

SuperConker said:

That worked perfectly, thank you very much!

Just remember to do it BEFORE you hit Restart.

slicendice · 08 Apr 2017

Just upgraded computer to build 16170.1000, and here we go again...surprise, surprise, display driver problems. Who would have thought that?

CountMike · 08 Apr 2017

slicendice said:

Just upgraded computer to build 16170.1000, and here we go again...surprise, surprise, display driver problems. Who would have thought that?

Ah those laptops, never satisfied with drivers.

slicendice · 08 Apr 2017

CountMike said:

Ah those laptops, never satisfied with drivers.

Easy fix, just disable nVidia driver and everything works again. Intel and nVidia display drivers does not seem to like to co-exist on Windows 10, for some reason. Just interesting that, they fall back to a build that has all the old bugs, when they could have used 15063 as base for rs3 development.

Kari · 08 Apr 2017

CountMike said:

Ah those laptops, never satisfied with drivers.

I've been lucky, apart from first 9XXX builds back in 2014 I've never had any driver issues with upgrade and / or clean installs. Never since first 10XXX build (I believe it was 10041?) have I had to manually install any drivers although a few times I've had to uninstall display drivers after an upgrade and let Windows to find correct drivers after restart.

Kari · 08 Apr 2017

slicendice said:

Easy fix, just disable nVidia driver and everything works again. Intel and nVidia display drivers does not seem to like to co-exist on Windows 10, for some reason. Just interesting that, they fall back to a build that has all the old bugs, when they could have used 15063 as base for rs3 development.

Again, no issues here. Intel and NVidia working fine together.

slicendice · 08 Apr 2017

Kari said:

Again, no issues here. Intel and NVidia working fine together.

Yes, but you have a bit newer nVidia chip and system chipset than me. ...and it does not matter which drivers I choose, the problem is in Windows. I have tried over 100 different driver combinations and none have worked on Windows 10 for this issue. NOT going to do that dance again. I 100% blame MS for this. :)

BunnyJ · 08 Apr 2017

For me.. I'm going to wait a bit before I try this again. With any luck the procedure will get better and/or I can get my head wrapped around the issue I'm encountering.

Either way.. I have lots of other things that are more important to do today.

Sigh.. this process used to be so easy.

Jeff

waltc · 08 Apr 2017

Worked fine from start to finish in upgrading from 15063.xx to 16170 via WU. Took about ~35 minutes. No problems, save for the text, "Hi! Are you the idiot who has been upgrading your OS every week or so? Hang on while we disorganize your GUI! Bla, bla, bla..." simply never showing up anymore at the end of a successful upgrade. Screen just drops out to a blank black screen that refuses all keyboard mouse interrupts--but drive light is churning so I know the routine is still functioning. Wait till drive light stops activity, then hard reboot and the new build comes up fine from then on.

One of the new build's fixed issues relative to System (Enhanced) High DPI scaling in a game I'm running turned out to be have been corrected in this build as reported (broken in 15063.xx), so that alone made 16170 worthwhile for me...!

magilla · 08 Apr 2017

well, after at least 8 tries on my desktop, which is relatively new and which always updates with new builds and is problem free, I gave up. Woke up in the night (I'm old so I don't sleep well) decided to try my laptop, which is about 10 years old. I downloaded and updated to 16170 and it works flawlessly as far as I can tell at this point. Go figure!.