Unable to Copy Files Smaller Then 481KB to Network Driver via SMB

Ferhat B 6 Reputation points
2022-05-31T18:59:54.707+00:00

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

Windows 10 Network
Windows 10 Network
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Network: A group of devices that communicate either wirelessly or via a physical connection.
2,274 questions
0 comments

17 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Martin Keller 1 Reputation point
    2022-09-23T09:10:59.397+00:00

    Maybe the fix is not yet in 22622.601 which I understand is still in Beta status. Let´s hope they implement this fix until release preview.

    0 comments
  2. RichardVI 1 Reputation point
    2022-09-22T13:30:56.337+00:00

    This does not make sense. Version 22621.521 fixes it, but the bug has regressed in 22622.601?

    How do I fix this then?

    0 comments
  3. Tom Callahan 6 Reputation points
    2022-09-21T14:54:41.267+00:00

    Confirmed, 22621.521 fixes it. But why would 22H2 not include it then? 22621.521 is supposedly the same thing. At least that's what I thought. I had just turned off participation in Insiders as of the next update, but maybe I'll turn that back on to avoid losing this fix.

    1 person found this answer helpful.
    0 comments
  4. 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.

    0 comments
  5. 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?

    0 comments