Jump to content

Certifacte Trust Provider error installing updates


mikey8811

Recommended Posts

Thanks for responding.

Now I downloaded the certificate from the above mentioned link and run the given command.

It shows an error 8007002. The image is as attached. Perhaps I do not know the proper procedure for it. Please guide.

I did attempt to right click the certificate and install it. Then checked the Event viewer after Reboot --

In the Event Viewer, earlier there used to be more than 50 entries of Error11 -CAPI2, now it has been reduced to 3 entries only. See the screenshot attached.

MSFN-ABBOD-BOSS.zip

Link to comment
Share on other sites


Got it! The cmd was modified to --
CertUtil -addstore "Root" "C:\MicRooCerAut_2010-06-23.crt"

But the Error11 - CAPI2 repeats in Event Viewer upon reboot.

See the screenshots.

11.jpg

22.jpg

Link to comment
Share on other sites

Hi Boss:

Try a slight variation of greenhillmaniac's suggestion <here>.  Download the MicrosoftRootCertificateAuthority2011.cer file from http://go.microsoft.com/fwlink/?linkid=747875&clcid=0x409 and save it to the root C:\ directory of your computer (i.e., so the location is C:\MicrosoftRootCertificateAuthority2011.cer). Then open an elevated command prompt with Administrator rights (search for "Command Prompt" from the search box next to the Start button and choose Run as Administrator), and enter the command certutil -addstore "Root" "C:\MicrosoftRootCertificateAuthority2011.cer" (include the quotes) to apply the required trust certificate.

Does KB4014984 (Security and Quality Rollup for NET. Framework 2.0, 3.0, 4.5.2, 4.6 on Windows Vista SP2 and Server 2008 SP2: April 11, 2017) install correctly after that trust certificate is applied?

Edited by lmacri
Link to comment
Share on other sites

Done -- CMD (Admin) > certutil -urlcache * delete

After the above step of deleting the contents from --

LocalService:

%windir%\ServiceProfiles\LocalService\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content

%windir%\ServiceProfiles\LocalService\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData

(It may be noted that in Windows Vista Starter 32 bit -- There is no LocalLow Folder but only Local and Roaming. So this step could not be carried out.)


NetworkService:

%windir%\ServiceProfiles\NetworkService\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content

%windir%\ServiceProfiles\NetworkService\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData

(This could be done).


LocalSystem:

%windir%\System32\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content

%windir%\System32\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData

(This could be done).

Restarted PC.

22.jpg.63486d3fe03fdb1d97027a8d3978268c.jpg

Attempted to install KB4014984 after downloading it from Microsoft Update Catalog -- KB4014984 consists of --

KB4015461 -- This update is not applicable to your system. (But when searched in Installed Update View, it already existed.)

KB4014553 -- This got re-installed.

KB4014559 -- This update does not apply or is blocked by another condition on your computer.

KB3078601 -- This update is not applicable to your system.

(see the screenshots attached in Zip File.)

 

 

MSFN-abbodi LMARCI.zip

Link to comment
Share on other sites

On 8/17/2021 at 5:09 PM, Boss said:

...Attempted to install KB4014984 after downloading it from Microsoft Update Catalog -- KB4014984 consists of --

KB4015461 -- This update is not applicable to your system. (But when searched in Installed Update View, it already existed.)...

Hi Boss:

Thanks for letting us know that updating your trust certificates seems to have fixed you CAPI2 errors.

There are multiple reasons why a .msu standalone installer will display that generic message - see the section titled "The update is not applicable to your computer" in the MS support article Windows Update Troubleshooting.  The most common reasons are that the update is already installed (e.g., like your KB4015461), the update is no longer required because it was superseded (replaced) by a newer update that is already installed on your system, or you tried to install an update that doesn't match the architecture of your OS (e.g., you tried to run a 32-bit/x86 installer on a computer with a 64-bit OS).  In most cases this message just means that the update isn't required for your system.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...