EV-Signing an existing driver

Pummelo

Hello,
we have a rather old kernel mode driver which is fully functional under Win64. However, this driver is not signed with an EV certificate and therefore requires to Disable Driver Signature Enforcement.
Unfortunately we don't have any source code of this driver anymore i.e. the only files are the .inf and .sys.
Question: Is it at all possible to get this driver (re)-signed with an EV certificate and send it to MS attestation.
In particular, we don't have a .PDB file to include in the CAB.
I tried to do this by creating a new driver project in VS 2019 and simply add these files, however checking of the inf file fails, because it uses some unsupported settings which may even be faulty to some degree, even though the driver as such works for our purpose.

Thanks for any help,
Roland

Dejan_Maksimovic

How old is it, was it signed and timestamped by any valid cross-cert before
June 2015?
If so, it should load on x64 W10, IIRC.

You need a valid .INF otherwise, to submit for attestation.

Kind regards, Dejan Maksimovic.
FS Lead: http://www.alfasp.com

Pummelo

@Dejan_Maksimovic said:
How old is it, was it signed and timestamped by any valid cross-cert before
June 2015?

No, unfortunately it had not been signed with a valid cross certificate. It is from 2010 or so and therefore it does not load under Win10 64.