Announcing Windows 10 Insider Preview Slow Build 16299 for PC Insider

24c said:

Not sure why I bought this monitor - not one of my better investments - I get a sore neck going back and forth from side to side.

This is my normal desktop - a pic looking north on Myrtle Beach in South Carolina
Attachment 156010

Nice pic! Looking north, huh.... as opposed to what?

24c said:

Not sure why I bought this monitor - not one of my better investments - I get a sore neck going back and forth from side to side.

Nothing wrong with an ultra-wide monitor. I could use a couple of those.

If you get a sore neck while navigating Windows, you are most likely sitting too close to the monitor. :)

f14tomcat said:

Nice pic! Looking north, huh.... as opposed to what?

Looking south - the ocean is on the other side

slicendice said:

Nothing wrong with an ultra-wide monitor. I could use a couple of those.
If you get a sore neck while navigating Windows, you are most likely sitting too close to the monitor. :)

Some of the "sore neck" comment was for effect -

Part of the issue is the Varilux glasses I have don't have a wide field of vision - require lots of head turning - the other part is I might be sitting too close to the monitor - :)

Is anyone else sick of Microsoft hitting us with NVIDIA beta drivers with the last couple of Insider releases

DooGie said:

Is anyone else sick of Microsoft hitting us with NVIDIA beta drivers with the last couple of Insider releases

Coincidentally I noticed some NVidia related weird stuff just now, in build 17004. Making preparations for screenshots for a tutorial I just now exported all drivers from current setup, to be "injected" to build 17004 ISO to make reinstall and especially post install update process faster. Was shocked to see the size of the folder I exported drivers to:



Notice that folder only contains exported drivers, being emptied before the process and used only for this purpose, store exported drivers.

Thought I had made a mistake, deleted the target folder and tried again, this time setting the export cmdlet in a variable, then when done getting a list of exported drivers using that variable. Everything else is as it should, but look at the amount of NVidia entries:



And, the weirdest thing is that those are all exactly the same version!

I wiped the HDD of this laptop early Tuesday and restored a recent Macrium image made a day before my old laptop died two weeks or so ago, but as that image was made from Windows in Skippy Fast ring and not clean installed since early summer, each successive upgrade has added some NVidia stuff.

Kari

Pleased you spotted this also Kari. Thing is the NVIDIA WHQL drivers run fine with the last couple of Windows builds.
However first I got delivered 387.76 then on this latest Windowes build 387.78.
Why! when NVIDIA version 385.69 WHQL works fine.

Can't you guys kill driver updates ?

CountMike said:

Can't you guys kill driver updates ?

Seemingly not on Home version Mike :)

Thought I had killed them but the latest Win 10 updates seem to overide it.