Message boards : Questions and problems : Windows 10 getting BOINC certificate error
Message board moderation
Author | Message |
---|---|
Send message Joined: 12 Nov 06 Posts: 13 ![]() |
BOIN 7.6.33 64 bit installed a service. Windows 10 Pro 10.0.14393 When I power up this PC and logon, sometimes I get the Windows 10 UAC box regarding BOINC making changes to my system. I have not yet tracked down what might be changing in the BOINC system to cause this, and cannot find an event in the Windows event log. When I inspect the certificate for the exe involved (from the UAC box), it shows as expired on 14 Jan 2017. PC has the correct time/date (locale Australia). I presume Windows 10 is complaining about this. This never happens on my Windows 7 box. Is there a way to update the cert? Or is there something else I should look at. I have downloaded and installed the latest version of BOINC. |
![]() Send message Joined: 13 Jun 14 Posts: 81 ![]() |
The ca-bundle.crt file in 7.6.33 expires on 2018/08/13. On my Windows 10 notebook (also Version 10.0.14393) I'm not getting and messages about expired certs. I do not have BOINC installed as a service,but I don't believe that should matter... unless it does. |
Send message Joined: 12 Nov 06 Posts: 13 ![]() |
The GTE Cybertrust Global Root certificate in the bundle is installed on my PC. I presume the install does this. But all the BOINC EXEs with certification have the same COMODO cert, which is valid from 14 Jan 2015 to 14 Jan 2017. I'll do a little more checking... |
Send message Joined: 12 Nov 06 Posts: 13 ![]() |
The message is not about the expired cert as such. It's the User Account Control box which, for example, pops up when you run a program "as Administrator". The UAC box has informational links, and the certificate information is accessed via one of them. |
![]() Send message Joined: 29 Aug 05 Posts: 15636 ![]() |
The message is not about the expired cert as such. It's the User Account Control box which, for example, pops up when you run a program "as Administrator".What I think happens here is this: when you install BOINC as a service, it runs with its own limited user account . Running extra as administrator will give problems here, as BOINC then tries to run the privileged account in elevated form, which Windows won't allow. |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.