Leaderboard

Hi guys, I have signed up specifically to thank Dave H for his solution to the problem of Office 2010 modules not opening on XP after the latest Windows updates. Before I found this thread I was about to uninstall MS Office and replace it with OpenOffice instead (I might still do that!). Now that I have removed KB4461522 everything has returned to running as it should. Thanks once again, Dave, and I hope all others in the same predicament will find your fix.

Microsoft Update offered me two suppsedly important updates for Office 2010 on Windows XP a couple of days ago, KB2863821 and KB4461522. They installed fine, but the next day I came to use Word, and it would not run, with the error message - Application popup: winword.exe - Entry Point Not Found : The procedure entry point GetDateFormatEx could not be located in the dynamic link library KERNEL32.dll. This was followed by "The operating system is not presently configured to run this application". I quickly found that no Office programs would now run, with the same error messages. I removed the two updates, and all returned to normal. I have no idea which of the updates caused the problem, and I haven't been offered either of them again so far, but if you are offered them, beware as they may well completely break your Office installation!

There were indeed several Office 2010 updates in this month's Patch Tuesday package, but none replaced MSO.DLL again. I did see there was an update to kernel32.dll for the first time in a while, and I wondered if perhaps they'd added the missing GetDateFormatEx function, but sadly not. I reinstalled KB4461522 and Office immediately completely failed again. Let's hope they do address the problem soon, as surely XP compatibility should be maintained for as long as Office 2010 is itself supported, as it was sold on the basis that it was compatible with XP.

https://support.microsoft.com/en-gb/help/4461522/november-6-2018-update-for-office-2010-kb4461522

Yes, we do pride ourselves in at least trying to figure out actual solutions, rather than the typical "just reinstall Windows" or "update your antivirus" type posts you see a lot of other places.

I booted my W10 partition on my main PC today to be greeted with a Windows update screen. At that moment I immediately and instinctually pressed the reset button on my tower and booted back into my W8.1 partition. I think I am getting old lol!

Regarding AV for Windows Vista: I never used it myself, but Vipre posted a Notice in February 2018 that version 11 would not support Vista, and their system requirements have since been modified to exclude Vista (support for XP having been dropped much earlier). If I believed in paying for antivirus protection, I might consider ESET or Webroot for Vista - but I wouldn't consider buying more than a 1-year license at this late date.

That time of the month again, and Microsoft has some Win Server 2008 SP2 updates at the MS Update Catalog site. So far, they've come up with KB4466536 Nov 2018 Security Update for IE 9 KB4467700 Nov 2018 Security Only Quality Update for WS 2008 KB4467706 Nov 2018 Security & Monthly Quality Rollup for WS 2008 KB4467243 Nov 2018 Security & Quality Rollup for .NET Framework (with KB4459933 for NDP 2.0, KB4459945 for NDP 4.5, KB4459942 for NDP 4.6) As usual, I'd suggest waiting a bit before installing things -- Microsoft's been known to change things within a few days (or even hours, on recent occasion). Wait for GreenHillManiac to give them his blessing, that's the safest policy. ----------- And almost as promised, a couple of these did get revised. KB4457700 and KB4467706, the Quality Rollups for Win Server 2008 SP2, were originally dated 9 November. The KB numbers, hashcodes, and sizes don't seem to have changed, but the dates went to 13 November., suggesting some change in the packaging info. Same old spam but a different label on the can, that's my take, but I'm not infallible.

Direct links for November 2018 updates - WES09/POSReady 2009 (5 updates, English only), IE8 cumulative security update (English) and Office 2007 compatibility pack SP3 security update (international): http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/11/windowsxp-kb4466388-x86-embedded-enu_b177578d5bc6c95cf31dd1848a22ddbe10b9501b.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/11/windowsxp-kb4467689-x86-embedded-enu_471a3ffee9661ee17087bd244ecec7edee0eff55.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/11/windowsxp-kb4467689-x86-embedded-enu_b974cbc4675474ddb38c41f7926f493cde207eee.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/10/windowsxp-kb4470118-x86-embedded-enu_eb3fe70a186545d1745f48eda37ecf21a1d330d9.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/10/windowsxp-kb4470198-x86-embedded-enu_7b13aaf44e4587d599a456d888e42f40e8b5ff3b.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/10/ie8-windowsxp-kb4466536-x86-embedded-enu_3edc5c600667b0925a02e757737942009abf643e.exe http://download.microsoft.com/download/D/E/5/DE510014-CB14-4027-B510-D2534694A6B9/xlconv2007-kb4461518-fullfile-x86-glb.exe

Yes, just uninstall KB4461522 from Add/Remove Programs and it should come good. That update replaces MSO.DLL, which then seems to be making a call to a function which does not exist in XP. I still hope we might get a fixed version in the latest Patch Tuesday updates, which I haven't been offered yet.

Windows 2000 does not support dynamic frequency scaling, so my guess would be that your CPU is simply running at 100% all the time, hence the high temperatures. You will need 3rd party software to control the frequencies.

Office 2007 won't receive this update anyway, as it's out of support. I've now reinstalled KB2863821, and it is fine. I guess I'll just hide KB4461522 and hope a version that works appears next Tuesday, but I'm not holding my breath!

Thanks. It doesn't actually look as if the updates are that important, just something to do with changes to the Japanese calendar. I'm now being offered them both again. I suspect that @Mathwizis right, MS have indeed broken XP compatibility with KB4461522. I hope they fix it, and don't just say that XP isn't supported any more. I wasn't sure BTW whether to put this thread here or in the Office forum. As it almost certainly does only affect Office 2010 users running it on XP, I guess this was the right place, but mods do feel free to move it!

This web page is very useful (to me): Master Patch List As for software, I like BatchPatcher Downloader and WindowsPatchLoader. I especially like BatchPatcher Downloader because it allows me to save detailed info about the updates to a text file. Phil