I’m having a very inconsistent problem with copying files from my remaining XP system to my Windows 10 system. Due to development software in use on the XP system, I’m keeping it active but without any use of a browser or email, and behind a Comodo firewall. Because of the development software and a couple of others that won’t install under Windows 10, I’ve settled on using its “public” folder as my main location for files shared across my network, with an image backup system protecting it, and an identical disk drive ready in case the current one fails.
My problem is that from time to time, Windows 10 (upgraded from Windows 8) fails to copy a file from the public folder of the XP system. Instead I receive a “failed to read” error.
If I try to force it as “Administrator” (despite using an admin account), I may get a UAC prompt asking if I want to allow this to change my system, and the copy still fails. Yet, often the copy operation will work without a problem. In fact, just now I successfully copied a few files from subfolders of Public into the Win 10’s Dropbox folder. When I tried the files that failed, they continued to fail. When (from the XP system) I copied those files to a different subfolder of Public, then (from Windows 10) tried to copy them to the Win 10 system, it worked!
The Public folder on the XP system has been marked “share this folder on the network” and “allow network users to change my files,” so there doesn’t seem to be anything obvious.
With the lapse of support for XP from Dropbox, I am trying to set up a batch command (under Scheduled Tasks on the Win 10 system) to use XCOPY to “sweep” any files I drop into a designated folder on the XP system. The batch file itself has run successfully a couple of times, but it consistently abends with “Access denied” when run on schedule, and running it manually later also fails.
This makes little sense and I can’t see a pattern in what is happening, so I’m hoping someone might have some ideas. Thanks!