New
#101
OK, I take it back....maybe. I am completely capable of looking at the same code 10 times and missing my error 10 times. So I deleted my changes, downloaded Slipstick's opennew_win10.reg and it works perfectly! But just for the heck of it, what did I do wrong editing manually. To my dyslexic eyes my manual string was the same as the .reg files entry.
Beats me!
To my dyslexic eyes your manual string looks the same as the .reg files entry too!
I looked at the .reg file and the only thing I see is the typing convention (two back slashes): one an escape character, the other a text character. This is just the way regedit handles things - you don't want to manually enter two back slashes, the example on Slipstick also shows only a single backslash.
The good news is that the .reg file worked for you. Other members will benefit from your experience (if the manual method doesn't work, run the .reg file) - thanks.
This is bugging me. When I edited the registry, I copied and pasted the string value from Slipstick's site. Did that again and it's broken. When I type the exact string again, it works. So is there something about doing a Cntl+V to the string that doesn't work? Sure looks identical.