Yes, I really need a solution as well. Right now when copying something to NAS I have to create zip-files for everything, then copy and extract it from the File Manager of Synology. Very time consuming!
Unable to Copy Files Smaller Then 481KB to Network Driver via SMB
Hello
I was directed here after a topic I opened in the Microsoft Community forum.
After I opened the topic, I continued to do tests about the problem and reached the results that I will state below.
I am connecting to a hard drive connected to the router using SMB 1.0 on Windows 11 Pro (Build 22621.1). I can read files from this HDD without any problems and write files of 481KB or larger to the HDD without any problems. But I cannot write 480KB or smaller files to HDD.
At first I thought the problem was with the SRT files as I was trying to write the SRT and MKV files to the HDD. MKV files were copied without any problems. However, as a result of my experiments, I realized that I could not copy 480KB and smaller files, regardless of file type. I created different size files using the below command and noticed that the problem occurs at 480KB and below.
fsutil file createnew <filename.type> <size_bytes>
The English translation of the error message for the problem is as follows:
An unexpected error is preventing you from copying the file. If you continue to receive this error, you can use the error code to seek help with this issue:
Error 0x80070026: End of file reached.
When I connect to the same HDD via FTP, I can write files without any problems.
Thanks.
Ferhat
17 answers
Sort by: Most helpful
-
-
Simon Walshe 6 Reputation points
2022-08-01T11:07:01.857+00:00 Does the "xcopy" command work? I don't think that that command uses the troublesome CopyFileEx API.
No - I've just tried using XCopy and it doesn't work either.
-
Simon Walshe 6 Reputation points
2022-08-31T10:01:59.51+00:00 I was given the impression that Microsoft had fixed this - if so they are taking a very long time to roll it out.
-
Martin Keller 1 Reputation point
2022-09-21T12:11:39.53+00:00 I just upgraded to the final version of Windows 22H2 and am running into this issue, so it is unfortunately still there. I will now roll back to the previous version.
Is there any workaround or do we really have to wait until there is a fix one day?
-
Martin Keller 1 Reputation point
2022-09-21T14:40:29.307+00:00 I just discovered that in the Release Preview Channel, there is now a Build 22621.521. I installed this Build and the problem appears to be resolved.