heinoganda

@glnz Check the size of the oleaut32.dll file in the %windir%\system32 folder, which should be 550 KB (563,200 bytes) in size and equal to the file version 5.1.2600.7494. This ensures that the mod. KB4134651-v2 is installed. Otherwise, I am of the same opinion as @Dave-H. Excerpt from my PM to @glnz Microsoft throws us many sticks in the way at the moment to spoil Windows XP. To be sure you do not get in the way of virus scanners such as Avast, after you download both updates (mod. KB4134651-v2 and KB4339291 from MS) and temporarily disconnect the Internet (LAN cable), you can disable Avast, including self-protection. After installation, Avast can be activated again, including self-protection, and the Internet can be reconnected. Now I can only hope that your problem is solved. Did you do that?

It's just a stopgap, because the oleaut32.dll file comes from KB4018556-v2, where each version number has been adjusted. I would prefer synonymous if MS would finally solve this problem and again an update would appear where the file oleaut32.dll works correctly again. Hope dies last!

The best would be from me to install the modified update KB4134651-v2 and then again KB4339291, so that your system should feel comfortable again.

@glnz KB4134651-v2 was released this month, which causes the same issues as KB4134651 (oleaut32.dll). Therefore, uninstall KB4134651-v2 and not KB4134651! After that MalwareBytes should work again. Incidentally, a modified update is also available for KB4134651-v2, so send me a PM.

I'm about to create a workaround, it takes a while. Will notify you about PM. A modded update is now available on request!

Attention! KB4134651-v2 has the same problem with the file "oleaut32.dll" as KB4134651!

Is not related to the problem described by @Mathwiz. Furthermore, I have published a definition updater for Windows Defender (Windows XP x86), where definition updates are still installed. (Is out of date, as most users use Microsoft Security Essentials and there is no demand / https://msfn.org/board/topic/175514-microsoft-security-essentials-and-windows-xp/?do=findComment&comment=1123808) English: https://msfn.org/board/topic/175514-microsoft-security-essentials-and-windows-xp/?do=findComment&comment=1122993 https://msfn.org/board/topic/175514-microsoft-security-essentials-and-windows-xp/?do=findComment&comment=1123087 https://msfn.org/board/topic/175514-microsoft-security-essentials-and-windows-xp/?do=findComment&comment=1123096 https://msfn.org/board/topic/175514-microsoft-security-essentials-and-windows-xp/?do=findComment&comment=1148188 https://msfn.org/board/topic/175514-microsoft-security-essentials-and-windows-xp/?do=findComment&comment=1150054 https://msfn.org/board/topic/175514-microsoft-security-essentials-and-windows-xp/?do=findComment&comment=1150206 https://msfn.org/board/topic/175514-microsoft-security-essentials-and-windows-xp/?do=findComment&comment=1150237 Int: https://msfn.org/board/topic/175514-microsoft-security-essentials-and-windows-xp/?do=findComment&comment=1147612 German: https://msfn.org/board/topic/175514-microsoft-security-essentials-and-windows-xp/?do=findComment&comment=1150451 And for the definition updates: https://msfn.org/board/topic/175514-microsoft-security-essentials-and-windows-xp/?do=findComment&comment=1122545

@Mathwiz This problem is with me in the VM with MSE (4.8.204.0) likewise present. Due to the increasing virus definition, which takes its toll on memory and processor performance, MSE inevitably becomes more and more slower. The size of the definition of MSE in the period from May 2016 to today has increased by 30%! Other virus scanner manufacturers are also struggling with this problem. In that sense, it is not a mistake.

Update for root certificates: New: CN = Microsoft ECC Product Root Certificate Authority 2018 O = Microsoft Corporation L = Redmond S = Washington C = US Note: Because this is an ECC certificate, this update is not relevant for Windows XP. Update for Cert_Updater: In Cert_Updater a feature was added.

At this point I would like to point out again that there are still problems with the MS servers when downloading the SST files for the cert_updater and should look like this. If necessary, try several times.

What do you expect? Official end of support was April 2014, now we are already in June 2018 and have at least until April 2019 the opportunity to get security updates. They were shown ways to at least circumvent the problems with the modern encryption technologies in OE6. I also had to choose a solution for myself. Make even a few thoughts about it.

If a certificate is deleted, causing various problems, then this is certainly not a good idea. At least in your case the "cert_updater" was not to blame. By the way, I have an updated version of ProxHTTPSProxyMII. If interested, send me a PM.

@glnz It should now also be known to you, that with each more recent update with "cert_updater" gradually root certificates are deleted with outdated, insecure encryption technologies (since there are no more modern encryption technologies in OE6, these problems occur). I do not know OE8 (make MS the suggestion for an OE6 successor), that's what Live Mail is known to me. Since I still use my OE6 like you, it does not work without an HTTPS proxy! By the way, your link to the doc file works through Internet Explorer 8 only with HTTPS proxy!

@Dave-H In no case should a manual deletion of invalid certificates occur in the Certificate Manager, unless the certificate can be assigned exactly. Typically, a certificate update (cert_updater) deletes the certificates that are no longer needed based on the downloaded "delroots.sst" file. Certificates that were imported manually are not deleted in this process! Recently I offered you the certificates from the file "delroots.sst", which are still valid within the time frame (only in this file the invalid certificates were deleted). @glnz Still working with Outlook Express 6, corresponds with Internet Explorer 6. Using an e-mail from Dave-H could open the images with HTTPS proxy in OE6 without certificate error message. The first possibility would be to upgrade OE6 with current encryption technologies (I think more of Santa Claus), the second possibility to use OE6 with HTTPS Proxy (ProxHTTPSProxyMII) and as a third option a more modern e-mail client.

@MaterSystem Then we can try the following, first stop the service "Automatic Updates", delete the content from the folder "%windir%\SoftwareDistribution" and restart the service "Automatic Updates". Now in the Internet Explorer delete all temporary files and start a search for updates (the first search takes longer!).

@MaterSystem Did you activate "Automatic Updates" where the updates already installed? You can check the registry at "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix" where all installed updates for Windows are listed.

Off Topic @FranceBB Thanks for your efforts. @Dibya For me MBAM 3 works just as well, it was about the statement "MBAM v3 dropped suport to XP long ago" and the claim that MBAM 3 could not be installed. Following information about this from Malwarebytes. Support for older versions of Windows operating systems Document created by xxxxxxx in 05/19/2017 Malwarebytes is committed to continue support for Windows XP, for as long as Microsoft allows us to. In fact, we're one of the few providers still willing to do so. This stand means that we'll continue offering our core anti-malware protection to the bed of our ability, given technical limitations. New features added over time will be supported as technically feasible. If a new feature , such as our Anti-Ransomware protection, relies on newer technologies not supported on older operating systems. Any features not support are listed in our official system requirements by product. Source: https://support.malwarebytes.com/docs/DOC-1469 In addition I will not write any further comment, because off Topic!

Unfortunately, there was no official fix for KB4134651 this month.

Definitely I can tell you, because I create my own update rollups and make monthly test installs in my VM, so that the support for TLS 1.2 works for IE8 with KB4230450 without previous updates KB4316682 and / or KB4103768. Condition is that KB4019276 is installed! The two registry entries HKLM,"SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1","OSVersion" HKLM,"SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.2","OSVersion" should be deleted so that the possibility exists to activate TLS 1.1 and TLS 1.2 in IE8. Update: The version number was not changed, but the creation date. Think in a binary comparison, there are certainly some differences. In this case, because of the same file version, the update KB4230450 can not be found when checking for updates if KB4316682 is installed.

https://support.malwarebytes.com/docs/DOC-1469

Off Topic Then explain the following screenshot to me:

Off Topic If you have had the opportunity to speak with someone from MS, have you also addressed the issues with KB4134651 (oleaut32.dll)? Many programs are no longer working properly, like MBAM v3.

@MaterSystem The Windows update server cluster, which is distributed worldwide, has been struggling with various problems lately. This has been commented in this topic by me and other users who were affected (Non-availability and various error messages). Unfortunately, a certain amount of time has been lost after a crash with the server for the forum. You can try at WU / MU in IE8 (currently only TLS 1.2 Encryption is enough) via https connection, has partly helped. https://update.microsoft.com/windowsupdate https://update.microsoft.com/microsoftupdate

Purely of logic, why should MS publish a Cumulative Update for IE8 where TLS 1.2 works properly and a little later a Cumulative Security Update for IE8 where TLS 1.2 stops working? IE8 is a no longer up-to-date web browser where many features are missing for which current web pages are needed. MS removes root certificates for each certificate update where they are classified as unsafe and therefore the IE8 (required for WU / MU) had to be retrofitted with TLS 1.2. Ironically, perhaps MS takes pity and releases the IE11 for Windows XP. @Dave-H Not only you are affected by the e-mail notifications from the forum. There seems to be a problem with the forum software.

I can reassure you, the files of KB4230450 are a little bit newer than those of KB4316682. The only thing MS has forgotten to change the version number of the files. @Mathwiz In the translation, an error has crept in, actually I wanted to write, the MS only further upgrades (ECC), if TLS 1.2 is uncertain.