Hal,
How could simply unzipping files into a folder, then *moving that folder* mess up something in the files themselves...? It doesn't mess up anything in the files. The problem is caused because Windows created a registry key that included where the *original* executable was located -- likely when Jonathan's Fractint SDL was first run in the *original* directory.
Knute ran CCleaner to try and solve this exact problem, and CCleaner found that the key no longer matched the folder that the .EXE was in, and complained, which allowed me to see the key problem. This key mismatch explains why you can move the zip file -- but not the exe -- to another folder, *especially* if you have already run Fractint.
I just tried this in Windows 10 several times with no problems. A more plausible explanation may be that the path (from the root directory to the executable) exceeded 256 characters. This is hard coded and doesn't fail gracefully. I will increase this limit. A month or two ago, we were seeing a similar problem with putting the folder on the desktop in Windows. This has been fixed. The problem was that there were some buffers overflowing. We could be seeing it again. Jonathan