"One or more external editors not be Launched."

If you must use an external editor in Reaper, simply does not run both the primary and secondary editor, is immediately displayed a sign saying "one or more external editors will not be Launched." I must say that this did not happen in reaper50rc14b version, now I'm evaluating reaper502pre3 version and despite correctly configured from the preferences, nothing works. As a note, I add the names of audio editors I've ever used, iZotope RX 4 and Adobe Audition CC2015, both work correctly independently and have also revised the route of release for each is correct. My English is bad with translate.google ... Sorry NEW NOTE: Also this happens in Reaper 5.0 and 5.01 Windows 8.1 Pro x64 Reaper 5.01 & 502pre4 x64 Soundcard: Alesis Multimix 16 USB 2.0 AMD FX(tm)-8350 Eight-Core Processor 4.00 GHz MoBo: Gigabyte GA-990FXA-UD3 (rev. 3.0) RAM: 16 GB

Help! 

Could anyone else have this problem or help to solve it? .... It is obvious that if this is not a bug, and if it was, someone please comment if you feel the same, I remind you that with versions 5rc14b not pass me that, everything works perfect, but since version 5 and subsequent, the problem persists, official versions, updates and prior to version 502. Thanks guys.

Win7, x64, Reaper v5.01 no problem here: right mouse click on wave, click "Open Items In Editor", "Open Items In Wavelab.exe" opens item in my wave-editor Wavelab.

Ok, thanks for the tip, is very rare in my case with previous everything works well and since version 5 and version 5.01 does not work for me, I have multiple versions in portable mode (maybe this is the problem here), if someone passes something similar, I do know please, I will not be extreme, but the problem persists, I go to reformat my computer and reinstall everything. Thanks for the reply

Solved 

Ok, good news, the problem persists in portable facilities, from there I was not able to run any external audio editor, but to uninstall and do a native installation, everything worked perfect. In any case it is very likely that the bug is only manifested in portable versions as has happened to me, anyway, and at least for a typical installation on the hard drive, this problem is solved.