Windows 10 Version 2004

Minimax True, up to a point.. I was able to force-install branches from 22.* and 21.*, don't bother it's not worth doing, but it was interesting to see because WDDM stayed at 2, however on Windows 7 using the driver I use in 7 (which also has support for 10, build 4279) dxdiag reports it at wddm 1.1 in 7, and 2.0 in 10 using the same file. So the OS plays a role as well. I don't have the platform update installed, so that's probably part of it. Otherwise, 4279 is not worth using on 10.

Thanks for testing. Kind of weird how unpredictable it all is. I was poking around windows update catalog as well to see if I could find anything interesting. Not really, just intermediate builds, with 5107 being the last one. They never bothered to put 5126 in there. I have a feeling that it's going to be very infrequent to see updates now. There was a year + gap between versions recently which I think was only forced because of a security update.

Personally, without evidence, I think their update model must be awful at Intel. They have so many branches for different architectures and each is updated independently. To me it seems more logical to have a single harmonized universal driver, and for each silicon chipset, just have flags toggled on and off for support of various features.

I feel fairly confident that our Broadwell GPU is never going to be able to take advantage of the Windows 2004 support feature to allow for offloading from the CPU to the GPU.

Sunspark Personally, without evidence, I think their update model must be awful at Intel. They have so many branches for different architectures and each is updated independently. To me it seems more logical to have a single harmonized universal driver, and for each silicon chipset, just have flags toggled on and off for support of various features.

Probably explains why Intel couldn't find anything as part of their "investigation" into eyestrain issues. That and I strongly suspect they were looking into the wrong place anyhow.

Sunspark

Sunspark True, up to a point.. I was able to force-install branches from 22.* and 21.*, don't bother it's not worth doing, but it was interesting to see because WDDM stayed at 2, however on Windows 7 using the driver I use in 7 (which also has support for 10, build 4279) dxdiag reports it at wddm 1.1 in 7, and 2.0 in 10 using the same file. So the OS plays a role as well. I don't have the platform update installed, so that's probably part of it. Otherwise, 4279 is not worth using on 10.

Thanks. I stand corrected. The OS plays a significant role in WDDM support. So I think on Win 7 you will never get past 1.1.

https://en.wikipedia.org/wiki/Windows_Display_Driver_Model#WDDM_1.1

Sunspark I feel fairly confident that our Broadwell GPU is never going to be able to take advantage of the Windows 2004 support feature to allow for offloading from the CPU to the GPU.

I agree. Some algorithms and filters used by my graphics software are awfully slow. :-(

AgentX20 I've just installed 2004. Initial impressions coming from 1909 are not good.

The image looks clean and solid, but I'm getting low grade eye strain that seems to build over time.

More testing is required, and I'm reinstalling the video drivers. Might even roll back if that's possible.

Quoting myself! So I've rolled back to 1909 and I'm more comfortable. I was then prompted to upgrade my video drivers to the newest version and... I thought there was eye-strain.

So, right now I'm very suspicious about v2004 AND the newest Nvidia drivers. I vaguely recall reading that 2004 users needed newer Nvidia drivers.

I dunno what to make of all of this, as the problem sensations are slow and insidious and can be hard to assess.

It took 2 weeks to recover. Now i can use again the iphone X, Ipad air 2, Oled tv LG B8(with PS4, Swtich and chrome cast) and the dell E5550.
Unfortunately i didn't make a copy of my old installation on my desktop and now i am still sick when i try to use it. I've tried the 1803 and 1903 with no success. I should try the 1709 or i can try to buy an nvidia 2070 but now i am scared / tired to try and get sick

si_edgey Switching to modern Intel drivers instantly makes my eyes unable to focus and I get the familiar dizzy / nauseus / eyegrain / migraine feelings coming on eventually. So in my case everything is working as it should except the Intel driver. Not a major issue at all though, the 2016 driver works just fine.

I'm beginning to think issues like this are a mix of hardware and drivers interacting with each other.

Like I've said before, wish you could visit me and there's a good chance with my capture hardware and analysis software we could probably find out what's different.

Upgraded today to 2004 and massive improvement. Seem to get no problems.

Only other things I did were move down from say 30% brightness to 20%. And re-try doing the IntelPWMcontrol although I got an error when I ran it.

(Dell laptop)

Windows 20H2 is out. Who will be the first brave enough to try it?
I am still on 1903 on my desktop and 1809 on my working laptop. I need to buy a second SSD for trying this type of upgrade.

Lauda89 Me, actually. Stuff blew up last night on my drives, so I had to clean up the mess which took a long time. I was just in 20H2 just now as a clean install in the testing partition I have for it. It's exactly the same as 2004 and the Intel drivers for it are still the same ones as before. Edge Legacy has been removed from this build--too bad because I used to stream from within that browser. People who are fine with 2004 will be fine with 20H2 too, the difference after the cumulative monthly updates is apparently only a few megabytes, that's how similar they are. 7 is still my daily driver though.. my computer is a dual-core and W10 is heavier and slower on it so I really only pop into it sometimes for streaming services.

You don't need another SSD, if you don't have other OSes other than Windows, then it's easy to have multiple Windows versions on the same drive. 40 GB is all you need for a W10 partition. When you do an install, you just select custom install and select the partition you want it to use. The bootloaders for 7 to 10 are aware of each other and you'll have a boot menu to choose from. The menu can also see other OSes as well, but it's harder to work with, and frankly next time I play with one of those on my external SSD, I am going to disable the internal SSD to do the install on the external, and then when I want to use it, I will use the computer's UEFI boot menu itself to select to boot from the other drive like a USB stick.. this way I can leave 1 drive with an untouched Windows bootloader instead of daisy-chained.

Minor update: I realized some of the slowness/heaviness was due to animations. Turning them off to match what I had set in 7 made it pretty comparable, so that was nice.

degen The 22 vs 26/27 isn't solely the thing.. it's also the build # as well in the same series.. I know from my own comp different build #s of the same branch will present differently which I find odd and annoying because there's no consistency, but it's reproducible. Instead of using what 10 serves up (which can be quite old in some cases) you could try downloading directly from Intel's site. Their drivers aren't OEM-locked anymore, so you can actually install them on any comp now and see if it is any better. There is also a setting in the W10 new control panel to turn off the OS force-installing drivers for you.. so I'm thinking if you liked that 22 branch driver, if you disable driver force-update in the settings--if you don't, it will re-install what it thinks you should have, you could manually force-install the 22.* branch on top of what's there now in the device manager. Something I've done many times with audio drivers. Might be worth trying. To make your life a little easier while testing, I suggest setting a system restore point before starting.

About Netflix, you don't necessarily have to use the HTML5 player.. you can also use the Silverlight player. On 7 I use waterfox classic 2020.01 still because it's quite comfy for me but I have the useragent adjusted for the netflix site so that it will use the silverlight plugin instead of HTML5, looks better. Pale Moon is an old fork and is too slow for me. To use Silverlight, in any Firefox-type browser about:config settings create a new string "general.useragent.override.netflix.com" and for the string value enter "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0". Leave out the quotes. Of course, also download and install silverlight itself from Microsoft's site.

What version of ditherig are you using? I was testing with 1.11 and I can see a subtle difference when it is active in 10.

Laptop machines are susceptible to manufacturing variances.. display panel, firmware bios, etc. cannot say it is the same machine unless you know for sure the parts and version numbers.

so better 2004 or 19xx? I don't know whether to update ... and I don't know whether to block other automatic updates. advice?

Sofista90 Go ahead and update if you're already on a Win10 build, 2004 is not worse than 1903. If you're not, then that depends, as the video driver you're using does make a difference as does how you connect to the display.

The 2004 version gives me the same eye strain as 1903. I still think the Intel UHD driver is the issue here. Uninstall this driver and use basic display driver, my eyes gets back to normal again.

Did anyone get a forced win update yesterday? did it change anything?