After installing July 2026 Microsoft Updates WNBD is no longer trusted
After engaging with Microsoft - this is the response:
we discovered that yes, the file is signed but not with the correct certificates, this is because windows update needs defined signature due to which it has removed the expired certificate signing while installing the update.
This happens when we do not sign the component files with the Microsoft security standard, in July month update we are not replacing or updating this wndb.sys file, rather requested for the correct certificate entry, which in our case is missing the certificates and is expired.
Issued to: Cloudbase Solutions Srl
Issued by: SSL.com Code Signing Intermediate CA RSA R1
Expires: Mon Aug 12 09:08:40 2024
SHA1 hash: E530EE278DEBA026C554FFF95790C66E4997061A
Your operating system needs a driver catalog file (.cat) that contains the .sys and the .cat file should be signed to cover everything in it. Once you have signed you can try installing only the driver files or just replacing the signed file in the parent locations. Please connect with the Cloudbase team once and discuss further signing the affected file.
MERGED FROM OTHER QUESTION Updated to new windows on Windows server 2022, and the rbd mapping no longer works. Reverted to the previous version to make it work temporarily. Error on manual mount cannot find wnbd adapter Running the driver manually gives a cannot verify signature error Driver version is 0.7.0.0.
