This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 61%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVS%3C/text%3E%3C/svg%3E)
As you're aware, Microsoft supplies the NDIS miniport driver, Rndismp.sys, which is a Remote NDIS miniport driver maintained and distributed by Microsoft across all supported Windows versions. To utilize the Remote NDIS driver with a USB device, an IHV must furnish an INF file based on Microsoft's provided templates.
Following Microsoft's guidelines, We have created an INF file structured according to the template. We conducted HLK tests for Windows Server 2019/2022 and obtained Microsoft's certification (MSFT sign) for the custom.inf file. It's important to note that we(IHV) have not developed any drivers for the host side; our INF file simply loads the inbox driver rndismp.sys corresponding to the OS version installed, regardless of whether it's a Windows Desktop or Server variant.
Reference: Microsoft Dashboard Code Signing Requirements
(“A dashboard signed driver that has passed the HLK tests will work on Windows Vista through Windows 10, including Windows Server editions. HLK testing is the recommended method for driver signing, because it will sign a driver for all OS versions.“)
We've verified this by successfully installing the Windows Server 2022-signed INF file on Windows Server 2025 without any issues, confirming compatibility.
"For RNDIS driver support, AMI provides an INF file for which we have obtained Microsoft's certification through HLK submission for Windows Server 2022. Since rndismp.sys is provided by Microsoft as an inbox driver for all supported OS versions, and considering the successful HLK submission for Windows Server 2022, we believe a dedicated HLK submission for Windows Server 2025 is unnecessary. Can you confirm if we can use the MSFT-signed INF from our Windows Server 2022 submission in Windows Server 2025?"
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 62%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDZ%3C/text%3E%3C/svg%3E)
Hello VIGNESHKUMAR SRIDHARAN,
Thank you for posting in Q&A forum.
I am sorry, after my research, I couldn't find any official documentation indicating whether a resubmission for the 2025 version is necessary. I think you could use 2022 version on Windows server 2025 for test purposes.
However, I suggest that you should re-submit the 2025 version once it officially released to avoid any potential issues.
I hope the information above is helpful.
If you have any questions or concerns, please feel free to let us know.
Best Regards,
Daisy Zhou
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.
Hi Daisy Zhou,
Thank you for the response. HLK is not only for the driver. It is also for the hw. Since the hw is given by us and also as per your suggesion, I hope we may need to run the HLK for windows server 2025. We have started the process. I have other queries related to a HLK test failure. I will post the query in a new thread.
Thank you for your support.
Regards,
Vignesh