Error 0x80090006 invalid signature

Hi all,
I’m facing the error as in the subject when trying to copy any file from my USB stick inserted into the router via network sharing (LAN). I found this page, but the proposed solution isn't suitable for me because the file isn't encrypted or signed. Furthermore, it's not even large and the issue affects any file.

0x80090006 (-2146893818 NTE_BAD_SIGNATURE) -- 2148073478 (-2146893818)
Error message text: Invalid Signature

FreeBooter said:

0x80090006 (-2146893818 NTE_BAD_SIGNATURE) -- 2148073478 (-2146893818)
Error message text: Invalid Signature

Click to expand...

Sorry, I don’t understand what you mean. Is that a solution?

You have provided minimal details of your problem; you have not told us what kind of file you're copying or what happens when you try other files. Is this the only file you are having the problem with?

Try disabling SMB signing.

From an administrative PowerShell session:

FreeBooter said:

You have provided minimal details of your problem; you have not told us what kind of file you're copying or what happens when you try other files. Is this the only file you are having the problem with?

Click to expand...

Actually I had already specified this thing:

UnsafeRelease said:

[...] when trying to copy any file from my USB stick inserted into the router via network sharing (LAN).
[...] Furthermore, it's not even large and the issue affects any file.

Click to expand...

So, these files can be images, pdf documents, etc.

pseymour said:

Try disabling SMB signing.

From an administrative PowerShell session:

Powershell:

Set-SmbClientConfiguration -EnableSecuritySignature $false -RequireSecuritySignature $false
Set-SmbServerConfiguration -EnableSecuritySignature $false -RequireSecuritySignature $false

Click to expand...

Unfortunately it didn't work.

Error code 0x80090006 means "Invalid Signature" and typically happens during large file copies over network shares (SMB).

Usually triggered when security software or network hardware interferes with data packet signing.

Third-party security tools (like Symantec Endpoint Protection) can block or misinterpret signed data streams during heavy transfers. Temporarily disabling your security suite or turning off intrusion prevention (IPS) features often resolves the issue.

Network driver features like Large Send Offload (LSO) can cause TCP flows to become out-of-sync on file copies. Disable Large Send Offload for IPv4 and IPv6 in your network adapter properties fixes SMB transfer failures.

Running an integrity check via Command Prompt (sfc /scannow) can repair system components causing signature verification failures.

I don’t use third-party security tools, and as I wrote the issue is also related to a single small file such as jpeg, pdf, etc.
sfc /scannow doesn’t show errors.