KB4014984 doesn't install on Vista (standalone either)

Anonymous
2020-04-03T13:51:17+00:00

Hello there,

once again I have installed my beloved Vista Business (x86), everything goes fine except one of the last updates.

The system finds and suggests me to install the one which is exactly called

"April, 2017 Security and Quality Rollup for NET. Framework 2.0, 3.0, 4.5.2, 4.6 on Windows Vista SP2 and Server 2008 SP2 (KB4014984)".

Installing via Windows Update Center throws out the 800B0109 error.

What I have already tried: I do have NET. Framework 4.6 installed and there is an appropriate (?) update for it (KB4014553) as well as its standalone installer.

After successful file extracting this installer shows the same message with explanation in which it is said that

"A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider (error 800B0109)".

I also tried to download a standard Microsoft certificate file (found somewhere over the internet) and to import it to MMC (Run/mmc/etc.) - DOES NOT WORK.

But this rollup update (KB4014984) DID work during the last year, what could have happened?

Please help. Appreciated in advance.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2020-04-12T16:01:54+00:00

Hi Great White North, (COMPLETE SOLUTION TO PROBLEM)

Happy Easter.

I tried the method you suggested posted by Greenhillmaniac by downloading his Microsoftrootcertificate2011.cer file and installed it by the command line method he suggested.  Like Mikey said, this method "worked like a charm", and windows update installed the April 2017 rollup perfectly.  The "meticulous scientist" in me (you can probably tell by the way I post) was curious as to why this method worked so much better than the solution I posted yesterday, so I ended up restoring the Windows Vista partition several times and running several trials to answer this question.   It turns out that his certificate file is identical to the one I exported from a Windows 7 computer; however, the "command line" method of installing this certificate is a superior method of installing it that the method I was using, which was to import the certificate into the Trusted Root Certification Authorities tab by using the import button.

To anyone else who may encounter this problem, my recommended solution is outlined below:

Obtain a copy of the Microsoft Root Certificate Authority 2011 certificate either by downloading it (see previous posts in this thread) or exporting it from a more modern up to date computer (I used a Windows 7 computer.)  I would recommend also obtaining the Microsoft Root Certificate Authority 2010 certificate, but for the purposes of this solution the 2011 certificate alone works fine.  Copy this root certificate file (or files) to your C: drive by clicking the My Computer button, then the C: hard drive icon, and move or copy the file(s) to this window (for simplicity, do not put the file inside any folder on the C drive.)  Click the start button, then move the cursor to programs, then the accessories folder, then RIGHT CLICK the command prompt icon and choose "Run as administrator" from the pop up menu that appears.  Type cd\ and hit enter.  Then type certutil -addstore "Root" "c:\XX.cer" and hit enter. Type this command exactly as written including the quotation marks except substitute the name you chose for the certificate file for the XX.  You should get a confirmation message telling you that the command action was successful.  Run this command twice if you are installing both the 2010 and 2011 certificates.   Close the command prompt window and restart the computer.  You should now be able to install the Security and Quality Rollup April 2017 now either by running Windows update (easiest way) or by using the stand alone installers that I discussed yesterday (earlier in this thread.)  You can now delete the Microsoft Root certificates from your C: drive, or move them to a storage folder, or just leave them where they are (they won't hurt anything.)  My thanks to GREAT WHITE NORTH and GREENHILLMANIAC for their contributions to this solution.

Was this answer helpful?

4 people found this answer helpful.
0 comments No comments

56 additional answers

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Anonymous
    2020-04-19T18:33:11+00:00

    Hi Peter,

    The reason that the April 2017 rollup update "appears" to install correctly prior to the installation of .net 4.5.2 is because this patch updates .net 2.0 and whatever version of .net 4 you are using.  You can actually make Windows update install it 3 times if you wanted to (why you would want to, I have no idea.)  If you run the April 2017 rollup before installing .net 4.52 it will appear to install correctly but will only udate .net 2.0.  If you then install the .net 4.5.2 update, it will again appear on the Windows Update list and this time when you install the April rollup, (after correcting the root certificate error) it will update .net 4.5.2 and again appear to install correctly.  Now at this point if you download and install the stand alone installer for  .net 4.6, the April 2017 rollup will again appear in Windows update.  If you install it again, it will update .net 4.6.  Updating .net 2.0 does not need the Microsoft 2011 root certificate; however, updating the .net 4.5.2 or 4.6 does.

    Not that anybody sane would actually want to do this craziness, but I hope this explains the rollup behavior than you observed.

    Was this answer helpful?

    0 comments No comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. lmacri 2,505 Reputation points
    2020-04-19T14:17:11+00:00

    Hi Great White North,

    Does Microsoft Email you when I reply to your post?

    Hi Frederick Risener:

    Yes, and just to be clear I'm not doubting that updating your list of trusted root certificates by either importing the MicrosoftRootCertificateAuthority2011.cer file or using the Win XP utility Rootsupd.exe utility fixed your 800B0109 error when Windows Update tried to install 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).

    Going forward, if this 800B0109 error is going to be a problem for all Vista SP2 user performing a clean reinstall because of some recent policy change Microsoft recently made then I need to revise my instructions on page 1 of m#l's thread Updates not working, it has been searching for updates for hours and warn users that they must now manually update their trusted root certificates if they encounter this 800B0109 error .

    I just wanted to make sure that there isn't something odd about the way that you, Peter Starling and mickey1188 performed your clean reinstall before I do that (e.g., like manually installing the optional .NET Framework v4.6 from a standalone installer) before you were patched back to end of support on 11-Apr-2017. For example, mickey881 posted on 27-Mar-2020 in zoo10's Windows Vista Problems Installing Service Pack 2 that he tried to use a batch file to install Windows Server 2008 updates on his system after his clean reinstall of Vista SP2 but aborted the batch file before it had run to completion(note that Windows Server 2008 monthly rollups released after March 2019 will change the OS build from 6.0.6002.xxxxx to **6.0.6003.**xxxxx). My instructions in m#l's thread were first posted in June 2016 and I can't remember anyone else reporting they encountered this 800B0109 error when Windows Update attempted to install KB4014984.  However, you, Peter Starling and mickey1188 all performed your clean reinstalls in late March / early April 2020 so I'm open to the possibility that anyone performing a clean reinstall of Vista SP2 is now going to encounter problems with their trusted root certificates if they install the optional .NET Framework v4.5.2 or v4.6.

    And if you are correct that your problems updating to the latest Norton v22.15.3.20 (released 15-Apr-2020) was also caused by a missing trust certificate then Norton should be informed about this, because there are currently multiple Win XP SP3 users posting the the Norton forum that they are now having problems running their legacy Norton Security v22.15.x.

    I'll step out of this thread now since you and Peter Starling have both found the solution to your 800B0109 errors.


    32-bit Vista Home Premium SP2 * Firefox ESR v52.9.0 * Norton Security Deluxe v22.15.2.22

    HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS

    Was this answer helpful?

    0 comments No comments