Beware of Office 2010 Updates!

[Mathwiz]

Yet another Office 2010 update:

 

Quote

 

January 2, 2019, update for Office 2010 (KB4032217)

Improvements and fixes

---

This update makes some changes for the Japanese calendar in Excel 2010 so that the new Japanese era name can be displayed correctly when a new era begins.

 

I don't even have Excel 2010 (only have PowerPoint Viewer) but I was offered the update anyway.

[JohnnieB]

I am running Office 2010 on XP and today (9 Jan 2019) found I had had an automatic update which required an automatic computer restart and now I can't access Office Excel and Word. Received the same GetDateFormatEx and KERNEL32.dll messages as others reported previously. Looking in Control Panel/Add or Remove Programs (with updates ticked) I can't find Update 4461522, so am looking for advice. My updates for Office and its programs don't show dates so that doesn't help either. Has this problem recurred with another update? I have 4661521 but that is presumably something totally different. I am new to all this sort of stuff. Only came across your site whilst looking for solutions. Help please !!

[Mathwiz]

Yep - it's KB4461614, a "security" update to MSO.dll. Same stupid mistake as the one that started this thread: it "secures" Office 2010 (including even free products like PowerPoint Viewer) by making sure it doesn't run at all on XP. 8-)

Edit: Removed KB4461614 and PowerPoint Viewer runs OK again. Guess I'll have to hide it....

Edited January 9, 2019 by Mathwiz

[JohnnieB]

Thanks Mathwiz - you are a  wiz. Have removed update and all is back to normal.  Have also vetoed auto updates !!

Thanks again for help. Very much appreciated

[Dave-H]

Stupid, repeating exactly the same error they made in November and then fixed with a subsequent update!
Let's hope they do the same again this time.

Edited January 10, 2019 by Dave-H
Amendment

[Zapfenzieher]

On 1/9/2019 at 6:45 AM, JohnnieB said:

[...] My updates for Office and its programs don't show dates so that doesn't help either. Has this problem recurred with another update? I have 4661521 but that is presumably something totally different. I am new to all this sort of stuff. Only came across your site whilst looking for solutions. Help please !!

@JohnnieB, you can find out what updates you've received and the dates they were downloaded to your system by running Windows Security Centre and invoking the "Check for the latest updates from Windows Update" option (menu on left), then selecting the "Review your update history" option in the Windows Update explorer window which will subsequently appear (left side menu again, top option).

Cheers!

Edited January 10, 2019 by Zapfenzieher
add images

[yuhong]

Yes, the current MSO.DLL still has the problem.

[Nora]

Hi all,

Just a quick line to say you saved me before Christmas a couple of times and twice this week with that KB4461614 update!  It keeps making its way back to my computer but really thankful for your help. 

Best wishes,

Nora

[Dave-H]

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.

[NojusK]

40 minutes ago, 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.

Now,im going to install office 2010 on my xp pc and now i wonder what updates as of NOW i should hide/uncheck?

[Dave-H]

AFAIK the only current problem update is KB4461614.
Uncheck it and hide it when you see it in the Microsoft Update list.

[free1944]

This message just showed up, again,  a few days ago.   Does anyone know if another "bad" release caused this like it did in the November 2018.   Dave-H's solution worked for me back then, but cannot duplicate it since I no longer have KB4461552 listed as a "currently installed program".    Is anyone else having this problem?  Or is there something else I could do to try and remedy this? 

[XP-x64-Lover]

Same thing happened on XP x64 with that update. I simply re-imaged my backup since at the time I had no clue which update killed office 2010 on XP x64. Now I know, thank you.

[free1944]

Thanks for showing me how to rescue my Word.   I have a feeling that Microsoft doesn't like so many of us using our "free" Office programs!   That we all purchased many moons ago! 

[Dave-H]

17 hours ago, free1944 said:

This message just showed up, again,  a few days ago.   Does anyone know if another "bad" release caused this like it did in the November 2018.   Dave-H's solution worked for me back then, but cannot duplicate it since I no longer have KB4461552 listed as a "currently installed program".    Is anyone else having this problem?  Or is there something else I could do to try and remedy this? 

Same scenario, but it's now KB4461614 which is causing the problem.
Uninstall that and hide it and it should come good.
I'm still hoping they will release a substitute which does work soon as they did last time!