Hi, i have been getting a 'write failed' error when using flat assembler. I think this may have been because i installed it in C:/Program Files/. I moved the folder out of that folder into just the C:/ directory.
Despite the fact i had moved the main folder (and all sub folders/files) into C:/, when i opened flat assembler it looked in the old folders (which didn't exist) for my old project files. I could open this files even though when i navigated to the location in windows explorer it said it did not exist. Additionally, when i checked the project folder that did exist in windows explorer it did not have any of the project files.

Here is a video of the problem

The folders are exist but they are virtualized in win7+ it is a feature (or bug of windows). (I thing it`s a bug, but MS thoght it`s a feature, I dislike it).
Virtualized folders are located somewhere in %userprofile%/.../temporary internet files/Virtualized/C/.
Virtualized folders are NTFS objects like folders, but not folders.
Windows explorer never see them, but in savedialog and opendialog virtualized folders supported and seen.
in win7+ on the kernel level it is denied that applications to store their data to "Program File", for that purposes exist folder "ProgramData".
However if the application will try to store to "Program Files" subfolder, SaveDialog will be pointed to virtualized folder (and yes OpenDialog will see that virtualized folder too, but in compile state fasm can`t merge links of virtualized sources and sources in real folders).
Use for fasm unprotected folder like subfolder of C disk or subfolder of ProgramData.

If you want copy any binary file from virtualized folders use farmanager. (Your virtualized text sources you can copy w/o farmanager by opening them in fasm and than saving them to normal (enabled) location.

WinXP is the best of Windows forever! There no such bugs.

It is a "security" measure to prevent killing your system accidentally (or something like that). You can always reset all the ACLs to allow all access to everybody to the root drive, and other folders you choose. Not everyone will recommend that but it is up to you how you want to configure things and how much risk you feel is warranted and how much is just hype.

I think it has something to do with your fasmw.ini. Check that one out first.