sdrplay wrote:Could you uninstall the driver completely, delete the *.log files in the c:\windows\inf file - then redo the install and send us all of the new .log files from the c:\windows\inf directory please, ideally on all machines so we can compare failed to succeeded, but if not the failed ones would be good.
You could copy and back up the old ones if you want to keep them instead of deleting them.
Thanks and best regards,
SDRplay Support
I rather not to uninstall it on the working machine, because I'm worried it would fail on that machine too.
So here's all the steps I did on the ThinkPad machine (plus logs and screenshot):
1- Uninstalled MiricsSDR from Control Panel
2- Deleted the "msi2500.sys" from system32\drivers folder (file version: 5.2.1.0 , size: 118KB)
screenshot of file's properties tab:
http://imgur.com/ke2JmJx
3- Rebooted the system
4- Installed again
As you can see in the attached logs, the problem seems to be related to the CA who signed the files:
(error:
sig: Key = msi2500.inf
sig: FilePath = C:\Windows\System32\DriverStore\Temp\{6c267424-01a4-1f18-33ea-68301eddf903}\msi2500.inf
sig: Catalog = C:\Windows\System32\DriverStore\Temp\{6c267424-01a4-1f18-33ea-68301eddf903}\msi2500.cat
! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
! sig:
Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 14:06:57.089
sig: {_VERIFY_FILE_SIGNATURE} 14:06:57.089
sig: Key = msi2500.inf
sig: FilePath = C:\Windows\System32\DriverStore\Temp\{6c267424-01a4-1f18-33ea-68301eddf903}\msi2500.inf
sig: Catalog = C:\Windows\System32\DriverStore\Temp\{6c267424-01a4-1f18-33ea-68301eddf903}\msi2500.cat
sig: Success: File is signed in Authenticode(tm) catalog.
sig:
Error 0xe0000242: The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted.
)
5- I Installed certificates manually (both Mirics's and GlobalSign's)
6- Uninstalled and installed drivers again, but it still fails
I have an idea: Maybe it just works on fully updated machines that have the latest CA certs installed (that's why the Samsung laptop with Windows 8 had no problem, but my two machines with Windows 7 fail)
Can I manually update my Windows's trusted CA list?