Even if it were fuzzy (which can be tested piping Powershell's 'Get-ChildItem hklm:\' into fzf for instance), you'd need a lot of filtering to make that useful

Even if it were fuzzy (which can be tested piping Powershell's 'Get-ChildItem hklm:\' into fzf for instance), you'd need a lot of filtering to make that useful though (I'm guessing you don't want to see recent files whichhappen to contain the name of the thing you're looking for) and/or search specific trees only and/or limit depth. But even that won't immediately solve the usage of cryptic names. Better starting point would be Group Policy, which is mostly a layer over the registry but containing pretty good descriptions of what a setting does. It has a Powershell module, so combining that with fzf and a preview pane which shows the description might ctually be pretty neat, but probably not very fast.