>Have a VFP Application which does a File Copy from a mapped Drive. Works fine in XP, Win7 & Win8.
>
>In Windows 10 am getting a File Not Found Error even though the Mapped Drive and File are visible in Windows Explorer.
>
>Anyone else had this issue?

How is the copy being performed? Is it using COPY FILE, using low-level file operation (e.g. FOPEN(), FREAD(), FWRITE() ), or "shelling out" to execute a command in a command processor?

When performing the copy operation, are you using a fully qualified path for the file, or is it relying on relative paths? I'd run into occasions where the current directory isn't always what you thought it was at the time some command was executed (usually the result of doing something that implicitly changes the current directory)..

Are you copying to/from a root directory of the drive? If so, does the situation change if they resided in directory?

Have you verified that the runtime library installed on the computer in question is the correct version? I'd occasionally run into a situation where the customer's computer had the wrong revision (i.e. had an older revision of the DLLs) which resulted in seemingly random errors that couldn't be explained, and updating the runtime DLLs with more recent revision corrected the problem.