Jump to content

Recommended Posts

Posted
On 1/19/2019 at 2:47 PM, Dave-H said:

You should be able to hide it in Windows/Microsoft Update so it doesn't install again.
I assume you've got automatic updating switched on.
I would recommend that you switch it off, and configure it just to prompt you when updates are available, not actually install them!
IMO it's important to keep control now of exactly what is updated on your machine.
:)

Thanks a million Dave! I just switched off the automatic updates, hopefully it will be the end of that 

All the best,

 


Posted

KB4461614 now replaced by KB4462157.
Same problem, but different error message!

"winword.exe - Entry Point Not Found : The procedure entry point EnumCalendarInfoExEx could not be located in the dynamic link library KERNEL32.dll."

:angry:

Posted
27 minutes ago, Dave-H said:

KB4461614 now replaced by KB4462157.
Same problem, but different error message!

"winword.exe - Entry Point Not Found : The procedure entry point EnumCalendarInfoExEx could not be located in the dynamic link library KERNEL32.dll."

:angry:

Why?just why whats wrong with MS again!

Posted

Actually, it looks as if KB4462157 hasn't replaced KB4461614.
Although when I first installed KB4462157, KB4461614 seemed to vanish from my hidden updates list on MS Update as I expected, it then came back again and still said I'd hidden an important update.
I noticed on the KB4462157 KB page that it says "Fix: After KB 4461614 is applied, Access 2010 and Excel 2010 stop working."
I therefore tried reinstalling both of them, but the problem was still there, they give different error messages, and you get the KB4462157 one until you uninstall it, and it's then replaced by the original KB4461614 error message.
Both updates do replace MSO.DLL it appears, but I guess they're just two different versions which are both incompatible with XP in different ways!
Strange that having KB4462157 installed doesn't seem to override KB4461614 though.
:dubbio:

Posted
On 1/22/2019 at 2:21 PM, Tamris said:

Maybe they think that nobody uses Office 2010 on POSReady 2009 and regular XP users are extinct?

They would know how many XP systems are in operational condition due to Windows Update polling, since the client reports a limited software inventory such as version of Windows, Office, etc. And you can be certain that they record and use that data. They just wouldn't know about the XP systems that never hit Windows Update or the internet.

Posted
On 1/22/2019 at 6:46 PM, Dave-H said:

Actually, it looks as if KB4462157 hasn't replaced KB4461614.
Although when I first installed KB4462157, KB4461614 seemed to vanish from my hidden updates list on MS Update as I expected, it then came back again and still said I'd hidden an important update.
I noticed on the KB4462157 KB page that it says "Fix: After KB 4461614 is applied, Access 2010 and Excel 2010 stop working."
I therefore tried reinstalling both of them, but the problem was still there, they give different error messages, and you get the KB4462157 one until you uninstall it, and it's then replaced by the original KB4461614 error message.
Both updates do replace MSO.DLL it appears, but I guess they're just two different versions which are both incompatible with XP in different ways!
Strange that having KB4462157 installed doesn't seem to override KB4461614 though.
:dubbio:

Dave-H, thanks again!

  • 2 weeks later...
Posted

New one today: KB4462172

Quote

This update makes improvements to enable the new Japanese era when it is available.

Note To enable these improvements, you need to install KB4462187, KB4462157 and KB4461579 together with this update.

File Oart.dll was updated.

Seems harmless, albeit probably pointless since KB4462157 can't be installed on XP.

Posted
10 hours ago, Mathwiz said:

New one today: KB4462172

File Oart.dll was updated.

Seems harmless, albeit probably pointless since KB4462157 can't be installed on XP.

hm:dubbio:got 2 more then KB4462172

http://prntscr.com/mhb6mo

Posted

Yes, I got those three.
All installed OK, but whether they are doing what they should without the latest MSO.DLL installed I don't know.
I'm still hoping the XP non-compatibility problem will be addressed on Patch Tuesday next week, but I'm not holding my breath!
:(

Posted

Can someone please tell me which of the following updates should be avoided?

o2k10upd.png.a9550701fd48e630afe7c0ac9f3be665.png

Also, does anyone know why KB3001652 won't install?  I tried looking for an error log for it, but I'm not sure which log file it would be in.

Thanks

Posted
Just now, mockingbird said:

Can someone please tell me which of the following updates should be avoided?

o2k10upd.png.a9550701fd48e630afe7c0ac9f3be665.png
 

AFAIK KB3115314 and KB4462157

Posted (edited)

Also KB4461614.
KB3115314 was replaced anyway I think.
KB4462157 and KB4461614 are the only two I have now kept uninstalled and hidden.
All the others seem to be OK.
:yes:

Edited by Dave-H
Additions

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...