@Psycogeek I find the two extrema to be safe: (1) Don't say how to modify the registry (in which case a user's ignorance and need to Google the how-to will protect him - this is why I didn't include a disclaimer), and (2) tell how to modify the registry, but with full safety disclosures. Unsafe is the middle ground where the user learns just enough to be dangerous. Although both extrema are safe, I am concerned about disclosure overload if every registry-related answer has instructions and a necessary caveat.

I don't think it's a good idea to add the status-bydesign tag. I did a quick sample of questions tagged both bug and status-bydesign. They all were items reported as bugs, but determined to ultimately represent desired site function. In this case, the site function is not desired. The error that lead to the undesired function occurred in the design phase of development, not the implementation phase, but it's still a bug - a design bug.