Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


dencorso

[SOLVED!] List of issues due to newer versions of oleaut32.dll and current workaround

Recommended Posts

Well, after revising the full POSReady 2009 updates ported to Windows XP SP3 ENU, I'm sorry to say the original posts describing the initial issues observed are among those which fell down the memory hole, so I need your help to reconstitute their contents. I do remember that I was among those who 1st noticed something was wrong because (i) when downloading any archive with FF, then clicking on the folder icon to the right of the file name at the downloads list nothing happened (instead of it causing a windows explorer window to open at the folder where the downloaded file were); (ii) when right-clicking on any desktop icon, selecting "Properties", then clicking on the "Go to file" button, nothing happened (instead of it causing a windows explorer window to open at the folder where the linked-to file is); . But I seem to remember dimly there was (iii) an issue with Avast, too (or was it with Malwarebytes Antimalware; ?), IINM. (iv) an issue with Windows Live Mail; (v) it broke down copying files in between partitions/disks;  (vi) "Cannot write file. Code 10,242,7" error on attempting to scan from a Canon scanner/printer combo; (vii) the network tray icon stops working or doesn't appear anymore ... And last, but not least,  (viii) Karspersky stops working (and crashes on trying to run it)!

On 7/18/2018 at 6:29 PM, heinoganda said:

There were problems with KB4074852, KB4134651 and currently KB4134651-v2, where a modified update was created. For the modification, the file oleaut32.dll was taken from KB4018556-v2 with a change of the file version.  :)

On 6/2/2017 at 4:08 AM, heinoganda said:

KB4018556 has been revised and is now available as KB4018556-v2!  (POSReady 2009 KB4018556-v2 via WSUS catalog)
Info: In the WSUS catalog, all possible language variants are now offered at the download, with the web browser Firefox or Google Chrome. Miracles still happen!   :)

The workaround is to PM @heinoganda and install his modded update, which uses the oleaut32.dll from KB4018556-v2, but renumbered to satisfy MU/WU. Those of you all who remember more details please do post a reply and I shall include your info here in this post. TIA. :yes:

Edited by dencorso
Updated contents

Share this post


Link to post
Share on other sites

I do remember that the issue you were talking about was with Malwarebytes not Avast. The person who had it reported it to Malwarebytes but they weren't able to reproduce the issue so he wrote about it here and he found out that it was due to oleaut32.dll.

Edited by FranceBB
  • Like 1

Share this post


Link to post
Share on other sites

Please, can anyone tell me exactly which version of oleaut32.dll should be currently installed?

I have version 5.1.2600.7494 in both the System 32 and Dll cache

and version 5.1.2600.5512 in my service pak folder

Share this post


Link to post
Share on other sites

Did you install KB4134651? If so was it from MU or WU, or was it Heinoganda's patched version?

I believe 5.1.2600.7248 is the version from KB4018556-v2 (last known good version).

5.1.2600.7494 is probably the one from KB4134651-v2, but it could be either the bad version from Microsoft, or heinoganda's modded copy of the above good version.

Share this post


Link to post
Share on other sites

KB4074852 and KB4134651 no longer play a role, both have been replaced by KB4134651-v2.
If KB4134651-v2 is installed from MS (oleaut32.dll version 5.1.2600.7494), the file oleaut32.dll has a size of 534 KB (546,816 bytes).
In the modified KB4134651-v2, the file oleaut32.dll was taken from KB4018556-v2, only the file version was changed from 5.1.2600.7248 to 5.1.2600.7494 and has a size of 550 KB (563,200 bytes).
If KB4134651-v2 is installed as a modified variant, the file oleaut32.dll should be present in the folders %windir%\system32 and %windir%\system32\dllcache with the file version 5.1.2600.7494 with a file size of 550 KB (563,200 bytes).

If KB4074852 and/or KB4134651 is installed, the modified update KB4134651-v2 can be easily installed, but if KB4134651-v2 is installed from MS, it must first be uninstalled.

By the way, there are also problems with WLAN with KB4134651-v2 from MS.

:)

Edited by heinoganda

Share this post


Link to post
Share on other sites
9 minutes ago, heinoganda said:

If [the] KB4134651-v2 installed is [the] modified variant, the file oleaut32.dll should be present in the folders %windir%\system32 and %windir%\system32\dllcache with the file version 5.1.2600.7494 [and] a file size of 550 KB (563,200 bytes).

Furthermore, the modified variant of the file oleaut32.dll has the following hashes CRC32: 150C877B; MD5: 603DE674582F4D37B9D4C01C9D675F79 and SHA-1: 7944B2ABC7D9B1E7B4FE84E09F1B2A975BD7E4BD

Share this post


Link to post
Share on other sites

For the sake of history - KB4074852 broke down copying files in between partitions/disks.

Share this post


Link to post
Share on other sites
On 9/27/2018 at 2:09 AM, dencorso said:

(i) when downloading any archive with FF, then clicking on the folder icon to the right of the file name at the downloads list nothing happened (instead of it causing a windows explorer window to open at the folder where the downloaded file were);

(ii) when right-clicking on any desktop icon, selecting "Properties", then clicking on the "Go to file" button, nothing happened (instead of it causing a windows explorer window to open at the folder where the linked-to file is);

Does anyone find out a workaround to this 2 big related issue?

The KB4134651-v2 didn't resolve that problem that is relevant also to Chrome download list, not only FF

Share this post


Link to post
Share on other sites
On 9/26/2018 at 9:09 PM, dencorso said:

The workaround is to PM @heinoganda and install his modded update, which uses the oleaut32.dll from KB4018556-v2, but renumbered to satisfy MU/WU. Those of you all who remember more details please do post a reply and I shall include your info here in this post

Now, if you need it in Italian, for instance, that's OK, because @heinoganda created the workaround in all languages. Do PM him.

  • Like 2

Share this post


Link to post
Share on other sites

I remember when this  patch came i installed it on my old dead xp pc and kaspersky literly didnt work it didnt open and it complained it was crashing.:unsure:

  • Like 1

Share this post


Link to post
Share on other sites

:cheerleader: Aha! I did remember there was some issue with an antivirus! I thought it might be with Avast!, but it turns our it was Kaspersky! Thanks for the info! Added to the 1st post! :yes:

  • Like 1

Share this post


Link to post
Share on other sites
On 9/27/2018 at 2:09 AM, dencorso said:

(i) when downloading any archive with FF, then clicking on the folder icon to the right of the file name at the downloads list nothing happened (instead of it causing a windows explorer window to open at the folder where the downloaded file were);

(ii) when right-clicking on any desktop icon, selecting "Properties", then clicking on the "Go to file" button, nothing happened (instead of it causing a windows explorer window to open at the folder where the linked-to file is)

The workaround is to PM @heinoganda and install his modded update, which uses the oleaut32.dll from KB4018556-v2, but renumbered to satisfy MU/WU. Those of you all who remember more details please do post a reply and I shall include your info here in this post. TIA. :yes:

I installed the Heinoganda mod KB4134651-v2.

At the first reboot everything looks good. No wi-fi icon tray issue and also chrome downloads/properties-go-to-file work, but after a second reboot everything returned break.

At this point can be uninstalling KB4074852, KB4134651 and KB4134651-v2 the only option for the cited issus?

Share this post


Link to post
Share on other sites
1 hour ago, Vistaboy said:

At this point can be uninstalling KB4074852, KB4134651 and KB4134651-v2 the only option for the cited issus?

Yes. but one only needs to uninstall KB4134651-v2, if already added, to install @heinoganda's mod. The bad file in the previous one is overwritten by either. 

  • Like 1

Share this post


Link to post
Share on other sites

It's still early but it appears KB4466388 (released today) finally includes a permanent fix to these OLEAUT32.DLL issues.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...