(This may in Windows 2000 and older versions of Windows to play no role, but in Windows XP, there still functional updates are distributed.)Įdited Maby and Oracle Java has its own certificate management and is not dependent on the Windows Internal Certificate Management. Secondly, no problem at WU and MU is a corresponding query in order to introduce users to exclude from WU or MU. Rvkroots.exe v9 revoke certificates (KB3097966) SM Rootsupd.exe v47 ? Root certificates September 2015 SM Rootsupd.exe v46 ? replaced! Root certificates Juni 2015 SM

Rootsupd.exe v45 ? replaced! Root certificates April 2015 SM Rvkroots.exe v8 replaced! revoke certificates! (KB3050995) MSDC SM Rvkroots.exe v7 replaced! revoke certificates! (KB3046310) MSDC SM Rootsupd.exe v44 ? replaced! Root certificates March 2015 SM Rootsupd.exe v43 ? replaced! Root certificates Februar 2015 SM Rootsupd.exe v42 ? replaced! Root certificates November 2014 SM Rvkroots.exe v6 replaced! revoke certificates! (KB2982792) MSDC SM Rootsupd.exe v41 replaced! Root certificates March 2014 MSDC Rvkroots.exe v5 replaced! revoke certificates! WU MU MSDC Rootsupd.exe v40 replaced! Root certificates November 2013 WU MU MSDC Note: Has anyone ever looked at the date to the contribution of 'rvkroots.exe' and 'rootsupd.exe' I have posted on the forum? That irritates me very 'rvkroots.exe' one can understand the version number yet, but with 'rootsupd.exe' there is a future confusion if everyone thinks he would have updated again at a current time. Because Microsoft is starting as Windows Vista, after a system update, only the root certificate loading when required or tested for revoked certificates and thus stripped on an elegant way of Windows XP users.) (In May 2014 it was still relevant because I have occupied myself at an early stage with the problem of root certificate updates. I see an attack point to the Windows XP user to get rid not pay for extended support.)! Now, the current status () are not root certificate update and revoked certificates offered more! What ultimately means that the unique identifier of 'rvkroots.exe' and 'rootsupd.exe' no more influence has in Windows Update or Microsoft Update (As for me, I would this regard, do not change these Version entries. Have taken the trouble and made in VMware a clean Windows XP SP3 installation.

On the topic of unique identifiers for Windows Update or Microsoft Update by 'rvkroots.exe' and 'rootsupd.exe'.

Microsoft authenticode root authority