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. lmacri 2,505 Reputation points
    2020-04-14T17:57:42+00:00

    I also had this problem (endless update search) several years ago.

    And by the moment I suddenly found THIS I was ready to drop Vista at all.

    If IE9 is installed, its standalone version (KB4014661) will not install (message will be like "This update doesn't fit your system" or similar).

    Hi Peter Starling:

    Volume Z's instructions <here> recommend a slightly different set of speed up patches but both set of instructions achieve the same result and fix the "Checking for updates..." hangs if Service Pack 2 is installed.  Volume Z's instructions use KB4018271 (*Cumulative Security Update for Internet Explorer 9: May 9, 2017)*while mine use KB4014661 (Cumulative Security Update for Internet Explorer 9: April 11, 2017) but either set of "speed up" patches can be used.  If you read Volume Z's instructions it states that KB4018271 is "equivalent to KB4014661".

    Please read Note 3 of my instructions in m#l's thread Updates not working, it has been searching for updates for hours, which states "If you try to install a speed up patch that is already installed on your computer, download an installer that does not match the bit architecture of your OS (e.g., you try to run a 64-bit .msu installer on a 32-bit Vista machine), or try to install a speed up patch that has beensuperseded (replaced) by a newer update you will see a "The update is not applicable to your computer" error - see the MS support articleWindows Update Troubleshooting for other common causes of this error."  If you have IE9 installed on your computer and try to manually run the April 2017 KB4014661 .msu installer after the May 2017 KB4018271 update is installed you will see this "update is not applicable..." warning because the older KB4014661 has been supersceded (replaced) by the newer KB4018271 update.


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

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-04-14T16:05:40+00:00

    I also had this problem (endless update search) several years ago.

    And by the moment I suddenly found THIS I was ready to drop Vista at all.

    If IE9 is installed, its standalone version (KB4014661) will not install (message will be like "This update doesn't fit your system" or similar).

    Was this answer helpful?

    0 comments No comments
  3. lmacri 2,505 Reputation points
    2020-04-14T15:33:15+00:00

    ...Please read the VistaForums FAQ *How to Fix Vista SP2 "Checking for Updates..." Hangs and Slow Windows Updates*I mentioned <above>, which states in part "Users who perform a clean re-install of their Vista OS will encounter these "Checking for updates..." hangs as soon as Service Pack 2 (SP2) is applied." ...

    ... and further to my previous reply, if you are not sure if Service Pack 2 (SP2) is installed check at Control Panel | System and Maintenance | System as shown in the image below.  Download links for any missing service packs are provided in RayPilkington's Re-installing Windows Vista thread.

    Most users who have reinstalled their Vista operating system or performed a factory reset in recent years have reported that Windows Update is unable to find and install Service Pack 2, so unless the installation media you were using was "slipstreamed" with both SP1 and SP2 you are likely missing Service Pack 2 and ~ 200 other newer security updates unless you:

    1. Manually install Service Pack 1 (rel. 04-Feb-2008), if missing, since it is a pre-requisite for Service Pack 2.
    2. Manually install Service Pack 2 (rel. 25-May-2009), if missing (note that SP2 includesIE7, not IE9).
    3. Manually run the standalone .msu installers for the 4 or 5 required "speed up" patches listed in the instructions on page 1 of m#l's Updates not working, it has been searching for updates for hours [KB3205638(rel. 13-Dec-2016); KB4012583 (rel. 14-Mar-2017); KB4015195 (rel. 11-Apr-2017); KB4015380 (rel. 11-Apr-2017) plus KB4014661 (rel. 11-Apr-2017) if IE9 is installed]. Once Service Pack 2 is installed these "speed up" patches will be required to fix your Windows Update "Checking for updates..." hangs so that you can patch your Vista SP2 OS to end of extended support on 11-Apr-2017.

    Note that if IE7 is eventually upgraded to IE9 then the IE9 "speed up" patch KB4014661 must be manually installed or Windows Update will begin hanging on "Checking for updates..." again.


    32-bit Vista Home Premium SP2 * Firefox ESR v52.9.0 * Norton Security v22.15.2.22 * Malwarebytes Free v3.5.1

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

    Was this answer helpful?

    0 comments No comments
  4. lmacri 2,505 Reputation points
    2020-04-13T12:40:26+00:00

    ... as of early March 2020 Norton "forced" all of their accounts to upgrade to Norton Security 360 Deluxe which DOES NOT SUPPORT Windows Vista at all (which is what started this whole mess, why I had to reinstall Windows Vista and run Windows Updates.)  My Norton will not even run anymore on my Vista computer.  I am currently experimenting with Bullguard and Avast free antivirus to replace the Norton on this computer as they seem to be the only one's that still support Vista.  Any thoughts on a replacement for Norton?

    Hi Frederick Risener:

    Please read the VistaForums FAQ *How to Fix Vista SP2 "Checking for Updates..." Hangs and Slow Windows Updates*I mentioned <above>, which states in part "Users who perform a clean re-install of their Vista OS will encounter these "Checking for updates..." hangs as soon as Service Pack 2 (SP2) is applied."  Vista users who have performed a factory refresh or clean reinstall always encounter these Windows Update hangs as soon as Service Pack 2 (rel. 25-May-2009) is installed (see RayPilkington's Re-installing Windows Vista thread for download links for both SP1 and SP2) and must follow the instructions on page 1 of m#l's thread Updates not working, it has been searching for updates for hours in order to receive the missing ~180 to 200 security updates released after May 2009 that will patch them to the end of extended support on 11-Apr-2017.  If you installed the MS .NET Framework v3.5 or higher (which are optional Microsoft updates that are not part of the Vista OS) before you were patched to 11-Apr-2017 that might explain why you were missing the necessary 2011 Microsoft certificates 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).

    I live in Canada and use the EN-US version of Norton so your experience might be different than mine, but as far as I know the forced Norton updates described in the 08-Mar-2020 announcement Active Customers in Legacy Versions Are Being Upgraded should have only affected Win XP/Vista users who were still using v22.14.x or earlier.  My Vista SP2 was patched to 11-Apr-2017 and I was already using the Norton Security v22.15.2.22 (the recommended legacy version for Win XP/Vista, released March 2019 per the product update announcement <here>) so I was not affected by this forced upgrade. I don't have my Vista SP2 computer at home and probably won't have access to it for at least another month or two (I'm working from home with a Win 10 laptop during the COVID-19 shutdown) but the last time I checked my Norton Security Deluxe v22.15.2.22 was working correctly.  I know of a few Win XP SP3 users with Norton v21.7.0.11 who were forced to upgrade to v22.15.2.22 in early March 2020 and are now seeing application errors when they close some of their third-party software, but Norton LifeLock is hoping to release a bug fix in the next few weeks per employee SarojaK's 30-Mar-2020 post <here>.

    I purchased a perpetual (lifetime) license for Malwarebytes Premium a decade ago that isn't being used right now, so when my Norton Security subscription expires this year I'll probably activate that license and use Malwarebytes Premium v3.5.1-1.0.365 (the latest legacy version for Win/Vista; see <here> for the v3.5.1 download link) for my real-time protection. For now I just use Malwarebytes Free and run a manual Threat Scan once or twice a week just to check for any low-risk threats that might have been missed by Norton.


    32-bit Vista Home Premium SP2 * Firefox ESR v52.9.0 * Norton Security v22.15.2.22 * Malwarebytes Free v3.5.1

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

    Was this answer helpful?

    0 comments No comments