Microsoft Roots Update Instructions

gunemalli

Verified User
Joined
Jul 22, 2009
Messages
86
Location
Sheffield, UK
MODERATOR'S NOTE:
Please do a dig on the domain name www.download.windowsupdate.com and and also a reverse dig on the IP# to get the rDNS, before you decide to download anything from windowsupdate.com. While windowsupdate.com appears to be owned by Microsoft, the specific IP# for the above looks a bit suspicious to me.


Something all you webhosts and website owners need. Microsoft has finally released an update for their aging and really old Root Certificate list. This brings the CA list and Certs known to MSIE at par with Firefox and will bring down the monopoly of the CA giants. Here are the details.

Some instructions we received from Microsoft:

You can visit https://www.microsoft.com/downloads...FamilyID=c14f8940-71b7-41e3-8749-a00e01e22f17 to download and install the Root Update Package (the package of every root certificate in the Windows Root Certificate Program, including the StartCom root certificate).

You can also invoke automatic root update of new root certificates by visiting an https URL protected with a certificate that chains up to your root certificate. _Please note however the issues about relying on automatic root update and the likely necessity of clearing the Windows CRL cache on your own systems to allow it to work_.

*A note on Windows Update mechanics and the Windows CRL cache*. Often when corresponding with CAs after a root distribution, we hear that their new root certificate does not download automatically from Windows Update when they visit a website hosting a certificate that chains to it. This is because Windows draws a copy of a root certificate from its CRL cache before it visits Windows Update, and often an earlier version of a CA’s root certificate is present in the CRL cache even when they have deleted that root certificate from their system (removing a root certificate from a certificate store does not clear the CRL cache of that certificate). Windows is set to update its CRL cache and other services once a week, which can mean it will take one week for Windows XP or Vista to overcome the CRL cache issue naturally. Deleting the CRL cache, however, forces Windows to visit the Windows Update site and dynamically download the most current root certificates. I find that with the CRL cache cleared, an XP, Vista or Windows 7 machine will properly download a new root certificate from Windows Update.

Steps to clear the CRL cache:

On Windows XP:

1. Delete everything in the folder %Appdata%\Microsoft\CryptnetUrlCache (including subdirectories);

2. Delete (remove) any of your root certificates in the root store (from Internet Explorer select Tools / Internet Options / Content / Certificates, then delete (Remove) your root certificates, if present, from the Trusted Root Certificate store.

3. Restart all instances of IE. Make sure you shutdown all instances of IE before restarting it.

On Windows Vista:

1. Delete everything in C:\Users\[username]\AppData\LocalLow\Microsoft\CryptnetUrlCache (including subdirectories).

2. Delete your root certificates from the Microsoft Management Console with the Certificates snap-in From the Vista prompt, Start / Run / certmgr.msc).

1. Restart all instances of IE.

On Windows 7:

1. Delete everything in C:\Users\[username]\AppData\LocalLow\Microsoft\CryptnetUrlCache (including subdirectories).

2. Delete your root certificates from the Microsoft Management Console with the Certificates snap-in From the Windows 7 prompt, Start / Run / certmgr.msc).

3. At a command prompt, run “certutil –urlcache * delete” to remove any remaining cached root update CTLs.

4. Restart all instances of IE.

You will need to remove **any** semblance of the Windows CRL cache to see proper root certificate download behavior. Your customers may have difficulties following instructions to clear the CRL cache on their systems. Remember, the CRL cache is updated once a week, so proper root certificate update behavior will commence for all Windows users no later than one week.

Notes:

On Windows Vista and later, \AppData is a hidden directory, make it visible by typing %temp% in the address bar.

If you cannot delete the \CryptUrlCache subdirectory or its contents, it may be held by crypto services; at a command prompt (w/Administrator privileges) stop the cryptographic services

net stop cryptsvc

then restart them again

net start cryptsvc

Delete \CryptUrlCache and its contents. Close all IE, then visit the test website once more.
 
Last edited:
@gunemalli:

Please be so kind as to post the original location of the quote. See my not added to the thread. I'll be glad to remove it if someone can prove to me that my fears are ungrounded, but this is a serious issue; if someone other than Microsoft has told you how to update the certificate store en masse then this could be a major security issue.

Jeff
 
Hi,

Sorry if I've stirred things up. I received the info via my CA, startssl.com . I'm currently on my mobile. So I can't post much info on this. Also I will notify my CA about the IP address and ask him to check on it and i will check about that myself.
 
No problem. I may be overcautious, but to me it appears like updating from a forged update site could be a major security hole. I don't run Microsoft so I'm not sure if this site is real or not. Please let us know what you find out.

Thanks.

Jeff
 
Thanks for following through on this. A forged certificate update, if possible, could be an incredibly dangerous attack vector.

Fortunately I don't use MS systems ;)

Jeff
 
Back
Top