Instructions for "Windows Installer patch cache size"

pmikep

Active Member
It's not clear (at least to me) that one can enter a number (an Integer) where the default NTLite field says "Default."

From the note at the bottom of the window there is a hint that one can put in a "numerical value" in the field, and so, years ago, I stumbled into this fact.

But so that others don't have to stumble into it, perhaps the note should say "You can enter a number from 1 to 100" (?), which is the value ..."

And, since nuhi knows best, is there a suggested value for this field? Or a "best" value? I always enter 1, since I don't want to clutter up my disk with cache stuff. If so, then perhaps the note should offer this too.
 
Ah. So then my "ergonomic" suggestion is that NTLite should show a bold number "5" in the field (indicating the default) and then users will know that they can change the number.
 
The default is not to limit the cache size
what i ment, wimboot installation (used mainly to reduce OS footprint) set the size to 5% as recommendation
 
Mine is empty - you can put 0 and it'll remain empty on W10, still after different installations/ upgrades of programs need the hided cache (IE. Office updates before 2019 from the MSI packages). Haven't discovered any slowdown speeds on this depending on hardware of course. Other than that haven't seen any problem put it set to 0 (zero).
 
0 disables the cache as informed in the link I posted. I use 0 on this. Default uses a maximum of 10% of the disk for the cache.

If the value of the MaxPatchCacheSize policy is set to 0, no additional files are saved.
If the MaxPatchCacheSize policy is not set, the default value is 10 and a maximum of 10% of the disk space can be used to save old files.
 
Back
Top