Start->Run CMD prompted me to install the feature (NTVDM)... I allowed it. After it installed, Edit launched just fine.
Cool thanks for checking on this. I will try this on a different box and see if its some odd issue with Windows 10 and hardware of some kind. Also I will grab another HDD that I have and install Windows 10 to that drive on this same box to rule out any possibility of a drive problem, even though the drive was healthy when running prior OS on it.
As far as which edit I was using its the one that came with the build located at c:\windows\system32\
As far as the version of Windows 10 I only saw 2 ISO downloads available one for x86 (32bit) and the other for x64 (64-bit) that were English. I downloaded both of those and burned them to DVD-R.
Its interesting that NTVDM had to be installed to allow functionality of some of the command shell legacy features, when all prior Windows versions didnt require installation of any internal feature to allow legacy command shell functionality. Curious as to if this was intentional for security ( since why allow command shell features if your a home user that is strictly a GUI user and not a developer or an admin etc ) - or - because they are likely trying to steer away from the legacy command shell in the future and this is 1 step closer to its removal.
Thinking of Windows without a command shell, I would feel very restricted, and confined to only abilities that are part of Windows and applications or having to write programs that run only in GUI to do what i do so quickly within the command shell environment.
If it is for security reasons that they are eventually doing away with command shell, I dont see why they wouldnt just implement bare minimum privileges at the command shell, and require elevated privileges to do anything nasty from it. Similar to Linux distros requiring sudo. To do anything nasty credentials would have to be known for the targeted system(s).