Microsoft Acknowledges Gaming Performance Issues Under Win 10 Creators Update

[wtfbbqlol]

When I tried the Creator's update by accident last month (somehow my defer feature update option expired then), I ran some benchmark numbers to compare to my usual Anniversary Update numbers.

Windows 10 Anniversary Update 1607
- SuperPi 32M: 7 minutes 03 seconds +/- 1 second
- 3Dmark Time Spy: 9900 +/- 50 points

Windows 10 Creators Update 1703
- SuperPi 32M: 7 minutes 20 seconds +/- 1 second
- 3Dmark Time Spy: 9800 +/- 50 points

3Dmark dropped only slightly, which I'm not worried about, but the single-threaded SuperPi 32M numbers dropped about 4% which got me annoyed. That's like taking 200+MHz off my CPU clocks (I run my 5960x at 4.5GHz constant). I spent a few hours checking things in the task manager but didn't see anything obvious that was chewing up performance. Did stuff like disable Cortana (which seems a lot more pervasive in the Creator's Update), manually setting core affinity for SuperPi but no help. So I rolled back to the Anniversary Update and performance is restored. I mentioned this performance hit when the windows update survey asked why I'm rolling back. I hope Microsoft figured out what is going on and fixes it.

 

[BrainCruser]

I can't even use my 7700k on Win 7 anyways. And 8's more tablet centric approach was atrocious.

But when you say you don't care about dx12, I question just how commited to gaming a person can be. You'll need it sooner or later.

I think it took the best of both 7 and 8, personally. And they'll fix this current issue soon enough.

You can use a 7700K.
I use a 7600K, All you have to do is find the update that microsoft uses to peg you, and erase it.

 

[Easo]

You can use a 7700K.
I use a 7600K, All you have to do is find the update that microsoft uses to peg you, and erase it.

And there is a real possibility of driver issues (Googling this shows bunch of people having BSODs), as those werent made for Windows 7. Especially if you are on the Intel integrated GPU.
And... People, please stop blocking updates. WannaCry was supposed to be a good teacher...

 

[StrayKAT]

And there is a real possibility of driver issues (Googling this shows bunch of people having BSODs), as those werent made for Windows 7. Especially if you are on the Intel integrated GPU.
And... People, please stop blocking updates. WannaCry was supposed to be a good teacher...

I like Win10 anyways. I appreciate his/her advice, but I don't plan on doing this.

Hell, I've grown fond of the Movies app anyways..in addition to some other things. Built a small library on it at this point.....they got me in their grips.

 

[Tomorrow]

And there is a real possibility of driver issues (Googling this shows bunch of people having BSODs), as those werent made for Windows 7. Especially if you are on the Intel integrated GPU.
And... People, please stop blocking updates. WannaCry was supposed to be a good teacher...

Generally speaking there are 3 problems that occur when running Win7 on Kaby Lake and Ryzen or newer:

* USB3 ports do not work during installation = USB3 drivers must be integrated into install media or you must use a DVD writer and a PS/2 keyboard. Installing win7 on another system and then moving the drive also works but is more messy.
* Integrated graphics does not work on Kaby Lake = You must use a dedicated graphics card.
* Windows refuses to install updates = You need to patch wuaueng.dll file. Updates are still being made. MS has just blocked them.

So a bit of tinkering to integrate USB3 drivers, install a cheap dedicated graphics card and tinker a bit with the DLL file and you have fully functional system. Nothing extremely complex. There's even an update that can be integrated and 3rd party drivers to install to NVME SSD directly.

The only things you really lose compared to Win10 are DX12 and some Win10 specific GUI updates to Task Manager, Windows Explorer etc.

 

[ironcerealbox]

Since the deployment of the Creators Update, I've turned all of the "features" (read as "ordures/garbage") associated with "Game Mode" off including the "Game Mode" option [after extensive testing or benchmark runs for several hours over the course of a week].

Saw absolutely no performance gain or saw a slight decrease in performance in certain benchmarks. Futuremark's Fire Strike is notorious for running about 3% to 5% worse with Game Mode turned on. And so is their [Futuremark] Time Spy (which is somewhat expected considering it is a DirectX 12-based benchmark). Most games at lower resolutions will not see a difference; however, at the 4 to 5 million pixel resolution, you'll see an ever so slight decline in average fps (and, yeah, I tested this with my UWQHD monitor or UHD monitor set to lower resolutions).

So, yeah, placebo update for me except that I had a good hypothesis that it would amount to nothing and, indeed, my own testing confirmed my hypothesis. I do say "for me" because, well, others will argue to no end that it did do something positive.

 

[Readlight]

Its slow, its full of bugs, its full off unnecessary stuff and not ready for old computers.