Search Results
6/16/2025, 2:03:24 PM
>>105591813
>I'm also noticing a pattern: this guy goes straight for tapping directly on registry keys, instead of using Group Policy - a common mistake, born from a misapprehension as to what GP actually IS. Too many people think it's just a front-end for setting registry values in HKLM\SOFTWARE\Policies - no, it also includes a mechanism to protect those values from being reset or overwritten.
Yeah, I'm pretty surprised how these tweak tools that touch the Policies don't try to do it the right way by modifying Registry.pol (hell, there's even a PowerShell module with the cmdlets for fiddling with), and I always thought the "mechanism" was nothing but that when the system or the user queries a Group Policy update (like somebody launching gpupdate - especially with the /force switch), it just (re)applies the settings from Registry.pol
Then again, I'm a lucky bastard - from what I know wpd.app, WuMgr (i think WUMT as well) and Win10Privacy do directly set up policy keys in the registry (currently using the last two), yet I haven't been fucked yet. Maybe it will backfire on me, who knows.
>If you've ever seen a Dunning-Kruger bitch and moan that all his customisations got reverted when he (for example) installed the latest Feature Update, now you know exactly how he performed this particular footgun.
I know for sure that there are a couple of updates that reappear sometimes in the client that are not offered at all from WSUS. One of them with the Update Health Tools - I was always convinced this was the primary reason why people complained about their update policy customizations being resetted when they have them installed (to be fair, update descriptions are meant to be checked if you were configuring automatic updates).
(cont.)
>I'm also noticing a pattern: this guy goes straight for tapping directly on registry keys, instead of using Group Policy - a common mistake, born from a misapprehension as to what GP actually IS. Too many people think it's just a front-end for setting registry values in HKLM\SOFTWARE\Policies - no, it also includes a mechanism to protect those values from being reset or overwritten.
Yeah, I'm pretty surprised how these tweak tools that touch the Policies don't try to do it the right way by modifying Registry.pol (hell, there's even a PowerShell module with the cmdlets for fiddling with), and I always thought the "mechanism" was nothing but that when the system or the user queries a Group Policy update (like somebody launching gpupdate - especially with the /force switch), it just (re)applies the settings from Registry.pol
Then again, I'm a lucky bastard - from what I know wpd.app, WuMgr (i think WUMT as well) and Win10Privacy do directly set up policy keys in the registry (currently using the last two), yet I haven't been fucked yet. Maybe it will backfire on me, who knows.
>If you've ever seen a Dunning-Kruger bitch and moan that all his customisations got reverted when he (for example) installed the latest Feature Update, now you know exactly how he performed this particular footgun.
I know for sure that there are a couple of updates that reappear sometimes in the client that are not offered at all from WSUS. One of them with the Update Health Tools - I was always convinced this was the primary reason why people complained about their update policy customizations being resetted when they have them installed (to be fair, update descriptions are meant to be checked if you were configuring automatic updates).
(cont.)
Page 1