Windows 10 LTSC 1809 - Optimize Gaming/Poweruser/Runtime Profile, retaining maximum compatibility. For x64/UEFI systems

Status
Not open for further replies.
Ah yeha that must be the ones. Ill look more into it. I hjave to do some adjustments to the build anyway, VAC from Valve is complaining about some adjustments ._.
 
It pays to have a default install somewhere, in a vm or on another partition. I prefer on another partition incase the brown stuff hits the fan.
 
Yea prepping a new iso and installing the OS takes me less than 10 mins each time. pays to have hardware too :p
 
Yeah, 10 mins or so with an answer file. I like to keep a spare ssd around for when it does hit the fan, crucial bx500 120gb's are £20 thus very handy for a Code Brown and have got me out of crap creek a few times. hehehe
 
mhh I don't like this, Its not critical but: sfc /scannow shows integrity fault. So build is not clean.

"Repairing corrupted file \??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\\utc.allow.diffbase from store"

I wonder whats doing that. Might be related to diag*?
 
Ive never used sfc even on xp. The only time i check(of sorts) isif i do a dism cleanup after updates.
 
  • Like
Reactions: MT_
aaah mt iam not sure you added this or its even possible to add there is service called purgememcache wrote by somebody its cleaning programs cached data on ram and it has some good option i know there is other programs you can manually do or even with taskscheduler by executing a bat file ( although when i run games its no working automatically dont know why mybe its my system) i would say doing this has some cons especially if putting pagefile on a hdd btw after doing this (cleaning cache) games fell more responsive i can swear for this not sure its suitable for your profile just wants to say :)
 
  • Like
Reactions: MT_
Hi!

Do you mean clean standby memory? I'm not sure that is still a good idea. Pretty sure Microsoft fixed this memory pressure / stuttering bug. Also heard rumors memory compression had anything to do with it (not enabled in my profile)


Standby memory is actually a good thing in general, it can actually speed up / cache things so this actually can prevent frametime spikes in certain conditions.

As for testing: Do a benchmark which is known to spike because it doesnt properly preload everything first time round, and next run its way smoother. Now clear the standby cache and rerun the game/benchmark, certain stutters magically come back because it has to be re-loaded (from disk).

If I can integrate it, I think so but I want the profile (other than reg files) to be as compact as possible with minimal dependencies.
 
Clanger said:
evolve purge memcache?
MT_ i dont dick around with memory caches etc, 8.1 and 10 have better memory management than 7.
Click to expand...

True in general it is fine, but there was indeed a sloppy MS bug a while back that did indeed manage to make everything stutter once standby commit was filling up to max ram.

But since the fix that properly releases chunks of it when new programs require it, it works just fine!
 
MT_ the contents of the C:\ProgramData\Microsoft\Diagnosis folder are related to the telemetry client. If you removed this component this may be the cause of the sfc error. If this is the case NTLite needs a fix for the latest windows updates.
 
Last edited:
  • Like
Reactions: MT_
Yea, most likely. But it didn't do this a while back. Yes most likely something with latest update.

It is only a (log) file in there I think, or some unimportant part of it. No sign of compattellogger.exe or anything else.
 
Last edited:
@evolve purge memcache?
Click to expand...
Do you mean clean standby memory? I'm not sure that is still a good idea. Pretty sure Microsoft fixed this memory pressure / stuttering bug. Also heard rumors memory compression had anything to do with it (not enabled in my profile)
Click to expand...
yes there is section in task manager called cached is this standby memory idk
17134.320 resolves the standby cache bug.
Click to expand...

iam a bit confused o_O
as i got from this link since my english is not that good :p in the last sentence he says: bug was meaning this flag was being ignored in the standby cache leading to regions being Zero'd over before games and applications could make use of it resulting in IO stutter.
this is interesting!!
i didnt know this was a bug but what i heard is the cache size was growing alot and people should manually using commands or software to clean it ! also i have to add somethings iam running 1607 ltsb and we know it has not fail creators update :p because i heared many people had the problem with cache after this update.
Standby memory is actually a good thing in general, it can actually speed up / cache things so this actually can prevent frametime spikes in certain conditions.
Click to expand...
yes i know its a good thing
As for testing: Do a benchmark which is known to spike because it doesnt properly preload everything first time round, and next run its way smoother. Now clear the standby cache and rerun the game/benchmark, certain stutters magically come back because it has to be re-loaded (from disk).
Click to expand...
that is true as i said (i would say doing this has some cons especially if putting pagefile on a hdd) i feels lots of stuttering like crazy stuttering because of i/o of running pagefile on hdd but i know many people these days not doing this so i thought if pagefile being on ssd it should be much better even ssds still alot slower than ram. i think you running your pagefile on ssd i have to test it for my self after getting a ssd but all of these are about spikes of i/o operations but i said ( games fell more responsive i can swear ) after cleaning cache although trade of between stuttering
but getting more responsiveness might not be a good thing. again i have to test on ssd by myself
If I can integrate it, I think so but I want the profile (other than reg files) to be as compact as possible with minimal dependencies.
Click to expand...
hmm got it :)
 
Last edited:
  • Like
Reactions: MT_
Mhh. Pagefile. I dont think that got touched in weeks (maybe few bits and bytes) but thats maybe because I also have 32GB ram :p

No but really, the whole standby cache manual clearing doesn't have to be done anymore on 1809 with latest updates.
Goes for this profile as well.

I'm not observing any i/o spikes anywhere either, this build does not do any unnecessary i/o operations afaik that can be noticable :p
 
MT_ said:
Mhh. Pagefile. I dont think that got touched in weeks (maybe few bits and bytes) but thats maybe because I also have 32GB ram :p

No but really, the whole standby cache manual clearing doesn't have to be done anymore on 1809 with latest updates.
Goes for this profile as well.
Click to expand...
32. nice number ;) good to know about new fixes by microsoft thanks will do pagefile test on ssd as soon as i get one
 
Last edited:
  • Like
Reactions: MT_
I think the build is a candidate for final release, enjoy! Pretty much tweaked everything I wanted to. Small reg crash but i think that is because it wants to apply something that cannot be applied yet in the earliest install stage, but eventually will. No prob!

Once future LTSC 2021+ is around I will start using this as blueprint.
 
Last edited:
Status
Not open for further replies.
Back
Top