Creator's Update's GAME-functions are SINISTER and non-removable!

Perhaps you should have just disabled game bar in settings? Just checked and it prevents both game bar presence writer and broadcast dvr from running. At least im not seeing them in task manager. No need to butcher your system.

 

Ir runs, when you start the game.

 

From the perspective of the owner of a windows 10 gaming machine that will never use windows store games because of principle: If the only way to kill game mode right now is to kill edge, then I'll gladly kill edge until a better way is found. I don't use edge anyway. I do play games. I realize that some people use edge for whatever reason, but let's leave it up to them to choose using edge over the option of killing game mode. Just make a disclaimer: This method kills game mode but also kills edge. Serious gamers would be able to make an intelligent decision as to what is most important to them.

 

Depends on the game? I never see it running on the games I play

 

It is most noticeable on games you run that used to run fine but starting with 16188 now won't run at all--I've got three games in that profile to date. And it really has nothing whatever to do with Windows Store because I don't use the Windows Store at all for anything--and D3d games that used to run fine simply stopped running at all beginning with 16188. If I change APIs, however, for instance to use GLIDE instead of D3d, then the games will run fine. Whatever Microsoft is doing is negatively impacting d3d--and they need to cut it out, ASAP. Donna's notes for 16199 make mention of it--but do not shed much light on it--in "known issues" she says "Game like Civilization VI may not run"--but that's it. What she means by that cryptic remark is anybody's guess. Microsoft needs to really do a lot better in the future when they break something--to explain what's going on. And, turning off all game mode switches has no effect--the games that used to run still won't run--because the dlls are still being loaded. You have to look for them, though, as they are buried inside running svhost instances.

 

Stupid and dumb question? Isn't this having to do with the new driver model Microsoft is introducing in CU? IIRC it's WDM 2.2 or something...

 

killing explorer while gaming is not an option?
something like this .bat file

Code:

taskkill /f /im explorer.exe
cd C:\gamez\DAI
start /WAIT DragonAgeInquisition.exe
start explorer

 

you had to do the same thing in windows vista/windows 7 with explorer for much older games....lol

 

The 'optimizations' are based on MMCSS and all it does is give games a higher priority.

 

Hey did you make a write up on the steeps needed to cleanup any left over keys/other elements?

I'm also starting to look into the MDT.

 

Any update on this ?

 

Either use 2016 LTSB or go with the recommendations in this thread. Those are the only options I see.

 

Hello @MonarchX - Thanks for the suggestion. I mentioned the problem in Chatbox about a week ago that Win10 Fall Creator's Update slowed down/disabled several of my games, and mentioned it again on another thread several days ago, but no one seemed to be interested or cared. Glad to see someone on the forum finally taking on this problem. One thing worth noting: I had zero issues with Build 1703, these problems only began for me with Build 1709. Maybe a side by side analysis will reveal whatever was added and/or changed between the two builds that affects gaming so badly.