Is renaming an unmodified Visual C++ Runtime DLL allowed for redistribution?

Subject:

Is renaming an unmodified Visual C++ Runtime DLL allowed for redistribution?

We distribute a Windows x64 desktop application that includes the official

NumPy 2.5.1 Windows wheel.

That wheel was processed by delvewheel and contains the Microsoft Visual C++

Runtime DLL msvcp140.dll under a content-hash filename:

msvcp140-a4c2229bdc2a2a630acdc095b4d86008.dll

We verified that this DLL is byte-for-byte identical to msvcp140.dll from

the official Microsoft Visual C++ Redistributable 14.40.33810:

• identical file size
• identical SHA-256
• valid Microsoft Authenticode signature
• OriginalFilename remains msvcp140.dll
• no bytes in the DLL were modified

Only the filesystem filename was changed by delvewheel, and the dependent

Python extension modules were adjusted to reference that name.

Microsoft's redistribution documentation refers to distributing the

Redistributable files in "unmodified form".

Could you clarify whether changing only the filesystem filename, while

keeping the Microsoft-signed binary byte-for-byte unchanged, is permitted

under the Visual C++ Runtime redistribution terms?

Specifically:

1. Does "unmodified form" apply only to the file contents, or also require retaining the original filename?
2. Is filename-only renaming permitted if the binary and Authenticode signature remain unchanged?
3. If not, should applications instead use the original msvcp140.dll name or require installation of the official VC Redistributable?

Thank you.

<モデレーター注>
Microsoft Q&A (en-us版)で新規質問されましたので本スレッドはロックさせて頂きました。
下記スレッドにて質問を継続してください。
Is renaming an unmodified Visual C++ Runtime DLL allowed for redistribution?