Cannot write file attributes ERROR_NOT_SUPPORTED

[OhFFS]

I am trying to back up from NTFS to an exFAT volume via Samba, and I keep getting the above error:

Cannot write file attributes of "X:\Files\foo.exe"
ERROR_NOT_SUPPORTED: the request is not supported (SetFileInformationByHandle(FileBasicInfo))

This happens for quite a few files, not just .exe files.
When it happens with an .exe file, it reports it as an error.
When it happens with other file types, it reports it as a warning.

If I copy the files manually, it works with no problems.

Can anyone tell me what on earth is going on here?

[therube]

What OS are involved?

Might they be, the files have, ADS, Alternate Data Streams (that are not supported on exFAT)?

[Zenju]

There might be a workaround. Unfortunately I cannot reproduce the error when accessing an exFAT-formatted USB stick that is shared by a different PC via network.

[OhFFS]

What OS are involved?

Might they be, the files have, ADS, Alternate Data Streams (that are not supported on exFAT)?

Windows 11 (22H2), backing up via Samba to a Linux box (Xubuntu 20.04) with an attached external drive. Have updated exfat-utils and exfat-fuse. The files in question have no extra streams, and I have no trouble copying them manually, as I said.

[OhFFS]

There might be a workaround. Unfortunately I cannot reproduce the error when accessing an exFAT-formatted USB stick that is shared by a different PC via network.

Open to suggestions. Currently the only workaround I can think of seems to be to ditch FFS and write a quick Perl script to do the backup instead...

[tbain98]

I've had the same issue for several months. I'm using Windows 10 backing up to Samba exposed from my router (which I assume is running Linux). If memory serves, the Samba version is 1.0 because that's all the router supports.

I consistently see it fail while trying to sync files that were added on my computer, with an error that matches OP's, *except* that the files are all of the form `${FILENAME_WITHOUT_EXTENSION}~[4_ALPHANUMERIC_CHARS].ffs_temp`. It most often seems to happen with PDF files, though I can't say for sure that's not just a coincidence.

When I click `Ignore` for the files and attempt to manually copy them to the drive, Windows Explorer warns that the destination has files with the same names even though they aren't visible in the Windows Explorer UI and they aren't represented (size/count) in the properties viewer for the containing folder.

I'm tempted to blame the router and just move to a proper NAS, but also, it's hard to say that FreeFileSync isn't at least a partial cause of the problem, particularly since its file extension is clearly on the filename that's failing to copy.

[Zenju]

Open to suggestions. Currently the only workaround I can think of seems to be to ditch FFS and write a quick Perl script to do the backup instead...

I've installed exfat-utils on Ubuntu 18 LTS, mounted an exFAT-formatted USB stick and shared it via Samba. FreeFileSync on Windows was able to copy files via network and set file modification times without error. So whatever the problem is in your case, it must be something specific to your setup.

I'm assuming that ERROR_NOT_SUPPORTED is a warning only, and that the files are still copied, but without the correct modification time.

[OhFFS]

No, it's reported as an error, not a warning. It seems to happen when a new file is created, not when an existing file is updated. So for example I see things like this whenever I create a file:

16:47:51 Info: Creating file "B:\John\AppData\Roaming\Mozilla\Firefox\Profiles\c110gmj1.default-1552663754549\gmp-gmpopenh264\1.8.1.2\gmpopenh264.dll"
16:47:51 Error: Cannot write file attributes of "B:\John\AppData\Roaming\Mozilla\Firefox\Profiles\c110gmj1.default-1552663754549\gmp-gmpopenh264\1.8.1.2\gmpopenh264.dll".
ERROR_NOT_SUPPORTED: The request is not supported. [SetFileInformationByHandle(FileBasicInfo)]

but for an update, it succeeds:

16:47:51 Info: Updating file "B:\John\AppData\Roaming\Mozilla\Firefox\Profiles\c110gmj1.default-1552663754549\SiteSecurityServiceState.txt"

[Zenju]

There must be something to this file "gmpopenh264.dll", because FreeFileSync is using a fallback copy routine and this is where the error occurs. Perhaps it's sparse, or it has a corrupted ADS stream.

Does the following test version work for this file? https://www.mediafire.com/file/z3g9bd9lzgjhkke/FreeFileSync_12.3_%255BBeta%255D_Windows_Setup%25283%2529.exe

[OhFFS]

I'll try it, but bear in mind this was only one example. I have error message for several hundred files which failed in exactly the same way. And they are certainly not all corrupt, or many applications would not work. For example:

19:57:04 Error: Cannot write file attributes of "B:\John\AppData\Roaming\uTorrent\uTorrent.exe".
ERROR_NOT_SUPPORTED: The request is not supported. [SetFileInformationByHandle(FileBasicInfo)]

And yet uTorrent works perfectly well. Or a newly compiled program:

19:41:27 Error: Cannot write file attributes of "B:\John\Documents\new1.exe".
ERROR_NOT_SUPPORTED: The request is not supported. [SetFileInformationByHandle(FileBasicInfo)]

[Zenju]

A corrupted ADS wouldn't have any impact on other applications that don't read ADS. But that was just an example. To find out what's up with these files, you would have to do a trace. But let's try the beta first.

[J700_be]

FYI:
I'm, also having this issue copying files from NTFS (Windows 10 and 11) to FAT32 NAS or EXT2/3 NAS.
With admin rights using version 12.2.
The rights of the destination need to be applied to the copied files.

[Background_Basil_945]

Hi all. I'm facing the same issue on 12.2 syncing MP3 music files from an NTFS NVMe drive to an NTFS NAS SSD. Is there any further update?

EDIT: found the issue for my situation at least. Access to my NAS (via SAMBA share on ASUS AX86S router) is restricted with username/password authentication , but I ensure access is available in windows explorer before running the sync. If I disable authentication (enable guest mode, so no username/password required) then the sync completes fine, so it appears to be an issue with network access authentication. In the meantime, I will disable password protection for syncing!

[Plerry]

> ... I will disable password protection for syncing!
Not the safest idea.
Simply use the Windows Credential Manager to save the user/password for your NAS.

[Background_Basil_945]

> ... I will disable password protection for syncing!
Not the safest idea.
Simply use the Windows Credential Manager to save the user/password for your NAS.

Thanks - you're right, but the sync doesn't work if authentication is enabled. I only temporarily disable to sync. Hopefully to be fixed in a future update :)

[Plerry]

> Hopefully to be fixed in a future update :)
Update of what?
This does not seem to be a FFS problem, nor a Credential Manager problem, as that combination works perfectly fine with Samba-shares, at least Samba/SMB-shares on other Windows machines and on Synology- and QNAP-NASses.
Your description suggests (if I understood correctly) that your "NAS" is actually your ASUS AX86S router, and your (Network Attached) Storage, likely the router's internal memory, or a stick or disk USB connected to your router.
Most likely, the problem is then in the routers firmware.
Perhaps you should search the ASUS forum.

[Background_Basil_945]

Thanks Plerry, but it appears to be an issue with FFS.

I can copy and paste in windows explorer when authentication is enabled, but FFS generates the above error.

[Zenju]

To find out what's up with these files, you would have to do a trace.

[Background_Basil_945]

Thanks Zenju, trace run and sent to you.

[Zenju]

Thanks Zenju, trace run and sent to you.

Now we're getting somewhere! This is a variant of viewtopic.php?t=7898 but without the remnant .ffs_tmp files - instead the server returns ERROR_FILE_NOT_FOUND.

1. For clarification, can you post the *full* error message for one of these failed copies, e.g. the one for "01 - The Number of the Beast.mp3".

2. Can you check if .ffs_tmp files are left behind on the server, after the error occured?

Update 2023-07-05: Your logs contain lots of entries like

Deleting file "\\[...]\03 - Wolves-8d77.ffs_tmp

so this is only a minor variant of the case in the other thread, in that the server returns an incorrect (cached) ERROR_FILE_NOT_FOUND, although the file is existing.

[Background_Basil_945]

Thanks Zenju.

1.Full error message:
Cannot write file attributes of "\\AX86\Music (at MX500)\Big Wreck\FLAC\Albatross\01 - Head Together~4ed6.ffs_tmp".

ERROR_NOT_SUPPORTED: The request is not supported. [SetFileInformationByHandle(FileBasicInfo)]

2. I can't see any .ffs_tmp files, and hidden files are shown!

[Zenju]

1.Full error message:
Cannot write file attributes of "\\AX86\Music (at MX500)\Big Wreck\FLAC\Albatross\01 - Head Together~4ed6.ffs_tmp".

ERROR_NOT_SUPPORTED: The request is not supported. [SetFileInformationByHandle(FileBasicInfo)]

This is puzzling: I'm not seeing this type of error in the log at all. But perhaps we're dealing with two different issues here.

1. About the error message I mentioned earlier ("01 - The Number of the Beast.mp3"): You can retrieve it from:
C:\Users\JRC\AppData\Roaming\FreeFileSync\Logs\Network - D Music to AX86 2023-07-22 103219.259 [Stopped].html

2. About the ERROR_NOT_SUPPORTED error: Can you send me a .pml log for when this error occured? I don't think this error happened in the log you sent me.

[Background_Basil_945]

Thanks Zenju - both sent!

[Zenju]

For reference, here's the full error message related to the issue discussed in viewtopic.php?t=7898

Cannot copy file
"[...]\01 - The Number of the Beast.mp3" to
"\\[...]\01 - The Number of the Beast~f943.ffs_tmp".
ERROR_FILE_EXISTS: The file exists. [CopyFileEx]
Cannot read file attributes of "\\[...]\01 - The Number of the Beast~f943.ffs_tmp".
ERROR_FILE_NOT_FOUND: The system cannot find the file specified. [CreateFile]


I think the ERROR_NOT_SUPPORTED is a subsequent error that only occurs if the above ERROR_FILE_NOT_FOUND does not happen. In other words, when the workaround from viewtopic.php?t=7898 works as expected. But we'll see when we get there:

ERROR_FILE_EXISTS and ERROR_FILE_NOT_FOUND at the same time, is a new variant to me, and apparently also a server bug. I believe we can apply the same workaround: https://www.mediafire.com/file/xax5zdvzkxnadjm/FreeFileSync_12.6_%255BBeta%255D_Windows_Setup.exe

[Background_Basil_945]

Thanks Zenju. Tried the beta but the same issue occurs.

Cannot write file attributes of "\\AX86\Music (at MX500)\Big Wreck\FLAC\Albatross\01 - Head Together-7aed.ffs_tmp".

ERROR_NOT_SUPPORTED: The request is not supported. [SetFileInformationByHandle(FileBasicInfo)]

[Zenju]

This is the second error I mentioned, and is expected. But I don't know how it's possible that setting file attributes could fail with ERROR_NOT_SUPPORTED. Can you send me a PML log file for this case, too?

[tbain98]

I've been able to reproduce this problem, and have run with both the normal FFS version (auto-updated yesterday) and with the beta linked by Zenju. For me, the beta failed with two sets of errors.

In some cases, no .ffs_tmp files were left behind, and the errors were like the following:

```
Cannot write file attributes of "B:\Main\Documents\Tim\Games\Aquamarine\DIVER LOGS\MAP02\DiversLog_Map02-41d0.ffs_tmp".
ERROR_NOT_SUPPORTED: The request is not supported. [SetFileInformationByHandle(FileBasicInfo)]
```

For other files, .ffs_tmp files were left behind, and the errors were like the following:

```
11:55:13 PM Error Cannot copy file
"D:\Documents - Shared\Tim\Games\Aquamarine\DIVER LOGS\MAP03\DiversLog_Map03_Letter.pdf" to
"B:\Main\Documents\Tim\Games\Aquamarine\DIVER LOGS\MAP03\DiversLog_Map03_Letter-495e.ffs_tmp".
ERROR_FILE_NOT_FOUND: The system cannot find the file specified. [GetShortPathName]
```

The first case seemed to happen only to a few files per run (sometimes none, sometimes up to three that I saw) out of the nine files I was synchronizing, and I only ever saw it happen to the ones that were first in the list. And when I started trying to reproduce it to capture it with Process Monitor, I stopped seeing the first case, so I'm not sure what to make of that, but the trace I just sent you was from when only the second case occurred for all nine files since that's all I managed to capture.

This behavior matches what I saw with the non-beta version, so there doesn't seem to be a difference with the beta vs with the official release.

[Zenju]

For me, the beta failed with two sets of errors.

Thanks, tbain98, for the log and also your helpful descriptions!

In some cases, no .ffs_tmp files were left behind, and the errors were like the following:

```
Cannot write file attributes of "B:\Main\Documents\Tim\Games\Aquamarine\DIVER LOGS\MAP02\DiversLog_Map02-41d0.ffs_tmp".
ERROR_NOT_SUPPORTED: The request is not supported. [SetFileInformationByHandle(FileBasicInfo)]
```

This seems to be the same problem as discussed with Background_Basil_945 above: an error in the fallback copy routine. I have a few ideas, how to work around the ERROR_NOT_SUPPORTED, although, it's essentially a server bug. But when FFS is in a position to help, the tool will do so, no matter who's responsible.

For other files, .ffs_tmp files were left behind, and the errors were like the following:

```
11:55:13 PM Error Cannot copy file
"D:\Documents - Shared\Tim\Games\Aquamarine\DIVER LOGS\MAP03\DiversLog_Map03_Letter.pdf" to
"B:\Main\Documents\Tim\Games\Aquamarine\DIVER LOGS\MAP03\DiversLog_Map03_Letter-495e.ffs_tmp".
ERROR_FILE_NOT_FOUND: The system cannot find the file specified. [GetShortPathName]
```

This error is nasty. The pattern is:

CreateFile    \\[...]\DiversLog_Map04_Letter-c5df.ffs_tmp    EAS NOT SUPPORTED


Windows copy routine detects EA (https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/ntifs/ns-ntifs-_file_ea_information) on the source pdf file, and tries to create a file on the network drive with EA, which the network share does not support. Hoever, this leaves behind a 0-sized file, that is not cleaned up. I'd estimate this is a network driver bug. (Theory: When requested for a file with EA support, the network driver first creates a 0-sized file, then tries to set EA, which fails. It reports the failure, but does not delete the remnant file.)

CreateFile    \\[...]\DiversLog_Map04_Letter-c5df.ffs_tmp    NAME COLLISION


The Windows copy routine sees the failure, and instead requests the network share to create a regular file without EA support. This fails with "ERROR_FILE_EXISTS", because of the remnant 0-sized file!

CreateFile    \\[...]\DiversLog_Map04_Letter-c5df.ffs_tmp    NAME NOT FOUND


Control is back to FreeFileSync: It received ERROR_FILE_EXISTS, so it want's to check it's file size. The server responds with *false* information: ERROR_FILE_NOT_FOUND. Likely a stale server cache, which is also a server bug, because the network driver knows of the previous ERROR_FILE_EXISTS)
FreeFileSync reasons: First there was ERROR_FILE_EXISTS, but now we have ERROR_FILE_NOT_FOUND, this looks like the SMB server bug. So let's try our own fallback copy routine, instead of Microsoft's CopyFileEx:

CreateFile    \\[...]\DiversLog_Map04_Letter-c5df.ffs_tmp    NAME COLLISION


The server once again changes its mind and finds the file existing again: ERROR_FILE_EXISTS
FreeFileSync also handles an unrelated problem with 8.3 file names. Since the server responded with ERROR_FILE_EXISTS, FFS tries to get the short name (GetShortPathName):

CreateFile    \\[...]\DiversLog_Map04_Letter-c5df.ffs_tmp    NAME NOT FOUND


The server once more changes its mind (again wrong information, as you already confirmed the remnant ffs_tmp files): ERROR_FILE_NOT_FOUND

-----------------------------------------------------------------
To sum up: If asked "does this file exist", the server responds with wrong (stale) information and denies it.
If asked to then go ahead and create the file, the server can't lie anymore and has to concede the file exists (creating a file necessarily needs to bypass caches).

[Zenju]

@tbain98: There are a few things we could try to work around this mess.

First, let's try FILE_FLAG_NO_BUFFERING, in order to (maybe?) get the server to return correct answers when asked if a file exists: https://www.mediafire.com/file/jc2duvu0x6s8sfz/FreeFileSync_12.6_%255BBeta%255D_Windows_Setup%25282%2529.exe

[tbain98]

Using that beta version, I still see the second case ("ERROR_FILE_NOT_FOUND" and the .ffs_tmp files were left behind) for all files, so no obvious change in behavior from that.

Full error log from one of the files:

10:18:05 PM    Error    Cannot copy file
        "D:\Documents - Shared\Tim\Games\Aquamarine\DIVER LOGS\MAP02\DiversLog_Map02.png" to
        "B:\Main\Documents\Tim\Games\Aquamarine\DIVER LOGS\MAP02\DiversLog_Map02-a377.ffs_tmp".
        ERROR_FILE_NOT_FOUND: The system cannot find the file specified. [GetShortPathName]


A new Process Monitor capture is in your inbox.

[Background_Basil_945]

This is the second error I mentioned, and is expected. But I don't know how it's possible that setting file attributes could fail with ERROR_NOT_SUPPORTED. Can you send me a PML log file for this case, too?

Thanks Zenju. Apologies for the delay, been tied up over the weekend. I've seen the further comprehensive replies above (thanks tbain9824!) - let me know if a further trace from my end would still be helpful?

[Zenju]

Using that beta version, I still see the second case ("ERROR_FILE_NOT_FOUND" and the .ffs_tmp files were left behind) for all files, so no obvious change in behavior from that.

Dang, this would have been too easy... I'm starting to run out of ideas, but there's one more thing we can try: We know the files are there, despite what the server says (ERROR_FILE_NOT_FOUND). So deleting them unconditionally should work? https://www.mediafire.com/file/e3r3bm3imm3dlya/FreeFileSync_12.6_%255BBeta%255D_Windows_Setup%25283%2529.exe

For the future, can I filter these at all, like maybe to "Process Name starts with FreeFileSync"? This file is 160MB, which takes a while to upload, so if I can safely filter down to what matters, that would make it faster to upload/download.

Yes, that's okay.


That said, I just noticed that your target network share is also accessed by Dropbox.exe. Dropbox.exe could also be responsible for all the issues, so it's worth a test turning it off completely.

[Zenju]

I've seen the further comprehensive replies above (thanks tbain9824!) - let me know if a further trace from my end would still be helpful?

Yes: In tbain9824's case we're tackling another problem that happens before the issue discussed with you.

[tbain98]

I tried the newest beta and still hit errors:

8:44:23 AM    Error    Cannot copy file
        "D:\Documents - Shared\Tim\Games\Aquamarine\DIVER LOGS\MAP02\DiversLog_Map02_A4.pdf" to
        "B:\Main\Documents\Tim\Games\Aquamarine\DIVER LOGS\MAP02\DiversLog_Map02_A4-9f6f.ffs_tmp".
        ERROR_FILE_EXISTS: The file exists. [CopyFileEx]
        Cannot delete file "B:\Main\Documents\Tim\Games\Aquamarine\DIVER LOGS\MAP02\DiversLog_Map02_A4-9f6f.ffs_tmp".
        ERROR_FILE_NOT_FOUND: The system cannot find the file specified. [DeleteFile]


A new PML file is in your inbox. Thanks for continuing to look at this!

Dropbox.exe could also be responsible for all the issues, so it's worth a test turning it off completely.

I ran both the most recent beta and the prior beta with Dropbox not running and saw no difference in behavior.

Yes: In tbain9824's case we're tackling another problem that happens before the issue discussed with you.

Would you like me to split my content into a separate thread? I replied here since it looked to me like the same symptoms, but since they're unrelated I'm happy to split out a new one if it'll make it easier to be sure we reach a resolution on both issues.

[Zenju]

I tried the newest beta and still hit errors:

        ERROR_FILE_NOT_FOUND: The system cannot find the file specified. [DeleteFile]


Alas, this is as bad as expected. The "DeleteFile" is also fooled by the stale cache-response ERROR_FILE_NOT_FOUND.
But: We might be able to get the server to return accurate information via CreateFile's OPEN_ALWAYS disposition. This is a potential write-access, so it can't be cached: https://www.mediafire.com/file/9btl3cai4syeyy5/FreeFileSync_12.6_%255BBeta%255D_Windows_Setup%25284%2529.exe

Would you like me to split my content into a separate thread? I replied here since it looked to me like the same symptoms, but since they're unrelated I'm happy to split out a new one if it'll make it easier to be sure we reach a resolution on both issues.

No it's fine that way. You do have the same symptoms as the thread starter (once we get there), but also the other issue on top.

[Background_Basil_945]

I've seen the further comprehensive replies above (thanks tbain9824!) - let me know if a further trace from my end would still be helpful?

Yes: In tbain9824's case we're tackling another problem that happens before the issue discussed with you.

Run and emailed to you (#3). Thanks again!

[Background_Basil_945]

Alas, this is as bad as expected. The "DeleteFile" is also fooled by the stale cache-response ERROR_FILE_NOT_FOUND.
But: We might be able to get the server to return accurate information via CreateFile's OPEN_ALWAYS disposition. This is a potential write-access, so it can't be cached: https://www.mediafire.com/file/9btl3cai4syeyy5/FreeFileSync_12.6_%255BBeta%255D_Windows_Setup%25284%2529.exe

Hi Zenju

I've also run and sent a trace (#4) with log using this newer version too, in case it helps.

[Zenju]

Thanks Zenju. Tried the beta but the same issue occurs.

Cannot write file attributes of "\\AX86\Music (at MX500)\Big Wreck\FLAC\Albatross\01 - Head Together-7aed.ffs_tmp".

ERROR_NOT_SUPPORTED: The request is not supported. [SetFileInformationByHandle(FileBasicInfo)]

Run and emailed to you (#3). Thanks again!

It's like a Heisenbug: the "ERROR_NOT_SUPPORTED: The request is not supported. [SetFileInformationByHandle(FileBasicInfo)]" you received earlier does not occur anymore in this trace, instead it's the ERROR_FILE_NOT_FOUND.

[Zenju]

I've also run and sent a trace (#4) with log using this newer version too, in case it helps.

Looking good! Finally we're at "SetFileInformationByHandle(FileBasicInfo): ERROR_NOT_SUPPORTED" as reported in the very beginning of the thread! Here's a version that tries to work around. It might fail with a warning, but not an error. In any case I'll be interested in the log as always:
https://www.mediafire.com/file/zgn49q3ur10f6d9/FreeFileSync_12.6_%255BBeta%255D_Windows_Setup%25285%2529.exe

[Background_Basil_945]

I've also run and sent a trace (#4) with log using this newer version too, in case it helps.

Looking good! Finally we're at "SetFileInformationByHandle(FileBasicInfo): ERROR_NOT_SUPPORTED" as reported in the very beginning of the thread! Here's a version that tries to work around. It might fail with a warning, but not an error. In any case I'll be interested in the log as always:
https://www.mediafire.com/file/zgn49q3ur10f6d9/FreeFileSync_12.6_%255BBeta%255D_Windows_Setup%25285%2529.exe

Thanks Zenju - this latest version works exactly as you predicted - completes with a warning, not an error.

Great progress, thank you so much for your efforts!

However, while the files are updated (and I verified this), because the modify time isn't updated, the comparison for the next run still shows the same files to be updated in the next run.

Log and PML should be in your inbox.

[Zenju]

We're getting somewhere. The ERROR_NOT_SUPPORTED seems to be an issue specific to setting file attributes, but unrelated to file times. Question is, is it FILE_ATTRIBUTE_ARCHIVE in particular, or other attributes as well? Let's test: https://www.mediafire.com/file/20ajqgo815olcmz/FreeFileSync_12.6_%255BBeta%255D_Windows_Setup%25287%2529.exe

[Background_Basil_945]

We're getting somewhere. The ERROR_NOT_SUPPORTED seems to be an issue specific to setting file attributes, but unrelated to file times. Question is, is it FILE_ATTRIBUTE_ARCHIVE in particular, or other attributes as well? Let's test: https://www.mediafire.com/file/20ajqgo815olcmz/FreeFileSync_12.6_%255BBeta%255D_Windows_Setup%25287%2529.exe

Thanks Zenju. That errors:

Cannot write file attributes of "\\AX86\Music (at MX500)\Big Wreck\FLAC\Albatross\01 - Head Together-d599.ffs_tmp".
ERROR_NOT_SUPPORTED: The request is not supported. [SetFileInformationByHandle(FILE_ATTRIBUTE_ARCHIVE)]
ERROR_NOT_SUPPORTED: The request is not supported. [SetFileInformationByHandle(FILE_ATTRIBUTE_HIDDEN)]
ERROR_NOT_SUPPORTED: The request is not supported. [SetFileInformationByHandle(FILE_ATTRIBUTE_SYSTEM)]
ERROR_NOT_SUPPORTED: The request is not supported. [SetFileInformationByHandle(FILE_ATTRIBUTE_READONLY)]

Log and PML #6 sent to you.

[Zenju]

ERROR_NOT_SUPPORTED: The request is not supported. [SetFileInformationByHandle(FILE_ATTRIBUTE_READONLY)]

Log and PML #6 sent to you.

Perfect! I can finish the implementation now: The following version should fix all the issues discussed in this thread and should work for tbain98 as well: https://www.mediafire.com/file/qy678sks6o09n1n/FreeFileSync_12.6_%255BBeta%255D_Windows_Setup%25288%2529.exe

[Background_Basil_945]

ERROR_NOT_SUPPORTED: The request is not supported. [SetFileInformationByHandle(FILE_ATTRIBUTE_READONLY)]

Log and PML #6 sent to you.

Perfect! I can finish the implementation now: The following version should fix all the issues discussed in this thread and should work for tbain98 as well: https://www.mediafire.com/file/qy678sks6o09n1n/FreeFileSync_12.6_%255BBeta%255D_Windows_Setup%25288%2529.exe

Fantastic, thank you Zenju! Just tested and it ran with no errors or file read errors (only the usual, expected 'recycle bin not available').

Thank you so much for your efforts here.

[tbain98]

The latest beta version also ran without errors for me. Thanks for the fix!

[Lee-B]

I have been experiencing a very similar problem over the past few months, with errors syncing between a computer running Windows 10 Pro and a samba share. Interestingly, FFS was working fine on two other computers running Windows 10 Education connected to the same samba drive.

The latest beta version now runs fine for me on the machine running 10 Pro. Thanks so much for your efforts in fixing this!

I just made a donation to the project.

[Attilo]

Hi Guys,
I am getting this error (over 900 of them actually) just mirroring from my pc to an external hard disk for the first time:

Warning Cannot write file attributes of "E:\HD 1\DB At bkup\IC".
ERROR_INVALID_PARAMETER: The parameter is incorrect. [SetFileInformationByHandle(FileBasicInfo)]

Is it the same issue you are talking here above ? Any suggestion?

Thanks
At

[Zenju]

Warning Cannot write file attributes of "E:\HD 1\DB At bkup\IC".
ERROR_INVALID_PARAMETER: The parameter is incorrect. [SetFileInformationByHandle(FileBasicInfo)]

It's a different issue. What is "E:\HD 1\DB At bkup\IC"? Is it a file or a folder?

[Attilo]

Hi Zenju,
"E:\HD 1\DB At bkup\IC" is a folder.
I ran an update, after first mirror, and I got no errors there !?
I made some random checks...everything looks good.

Note I am synching to an external drive. On prevoius experiments working on folders of the same pc, I was getting no errors.

Should I care about this errors (over 900!?) ... or just ignore them ?

thanks