Interesting. I've installed the most recent experimental build and found that it (in this case, the standalone copy) launches just fine if I point it at Oblivion or Fallout New Vegas. Oblivion is installed on E: whereas FNV is on F: (which is where Skyrim and Skyrim SE are). A note in the troubleshooting page says if Wrye Bash refuses to load at all it's probably because there are unicode characters in the path. I can't imagine why that would be the case, since it always worked before and then just suddenly decided not to one day. Steam chooses the directory name (I would have preferred SkyrimSE over Skyrim Special Edition, for simplicity's sake, if nothing else). I suppose I could try to manually rename that folder (the exact same, just retyping it manually) to see if that fixed whatever the fuck is wrong, without causing the system to suddenly not recognize the install any longer? Best to wait until I'm ready for a new run, because I'm not at all liking the idea of things fucking up and having to do a complete reinstall, again.