MicrosoftJim_B175 - you're not wrong. That's part of why I scripted the change, so there's less room for error. Adding a value is far less risky than making changes to existing keys and values. In most cases, getting the value name or value wrong will simply do nothing. Although I didn't mention it, good practice is to make a backup of the registry before any edits. If the instructions were followed, it's hard to see what possible harm could come from adding the value. There is massive harm that could come from just telling people to dive into the editor and make changes, but that's not what this is. And, yes, it's very possible that this value will only affect operations for a limited time then quit working. If that happens, so be it. At least I've delayed the pain for as long as it works.
To everyone reading this, if you're as risk averse as Jim, don't create the .reg file and run it to move the buttons back where they came from. If not, and you don't like the new location, maybe it's worth a try. There's room here for you to make your own decision if you're willing to live with the consequences. Without the added value, you have no choice - Microsoft already decided for you.
Wolverines!
