glnz Posted November 15, 2017 Author Share Posted November 15, 2017 den, heinoganda, bersaglio and mcinnwwllrrll- From a link on Askwoody, I just noticed there is ALSO this: Word Viewer Description of the security update for Word Viewer: November 14, 2017 (KB4011264), which leads you to https://support.microsoft.com/en-us/help/4011264/descriptionofthesecurityupdateforwordviewernovember14-2017 . I remember that you all said we SHOULD run the "Word Viewer" updates if we have Office 2003 with the 2007 Compatibility Pack. (Correct?) So, should we manually install this update for Word Viewer: November 14, 2017 (KB4011264) ? Thanks. Link to comment Share on other sites More sharing options...
dencorso Posted November 15, 2017 Share Posted November 15, 2017 You might try it. In case it does not apply to your system it'll just say "the expected version of the product was not found on your system" and install nothing, so it's totally harmless to try it. 1 Link to comment Share on other sites More sharing options...
heinoganda Posted November 15, 2017 Share Posted November 15, 2017 2 hours ago, SD73 said: HOTFIX ID: EOL-MIICROSOFT-WINXP EOL-MIICROSOFT-OFFICE03 If a program shows me such a message, it can be assumed that there are no updated entries here, after in terms of the official end of support. This program might display many older updates (until April 2014), which are replaced by more recent ones from May 2014. @glnz KB4011264 is for Word Viewer 2003 and not applicable for Office 2003. Unfortunately this time not usable. Link to comment Share on other sites More sharing options...
Destro Posted November 15, 2017 Share Posted November 15, 2017 (edited) Those 2 updates, are just Microsoft fake news. scare tactic updates. They were part of microsofts fake news campain where they released fake updates and paid 100s of people to make fake news articles about how XP was dead and to scare you into buying new software. Edited November 15, 2017 by Destro 1 Link to comment Share on other sites More sharing options...
SD73 Posted November 15, 2017 Share Posted November 15, 2017 Yep. I wasn't concerned about those two. I'm glad my PC was smart enough to avoid them as the last thing I want to see when it boots are those messages. Now I'm looking forward to next months updates to see how smooth they go. Thanks again, fellas! Link to comment Share on other sites More sharing options...
heinoganda Posted November 15, 2017 Share Posted November 15, 2017 (edited) Before I publish a list of the most recent updates for Windows in this forum, I check these in my virtual machine to see if they are a problem or cause a malfunction. Each update is extracted individually to see which files or entries in the registry are changing and, as in the case of KB4048968, whether the application has been restricted to other XP variants. @SD73 Happy to hear when you finally get all the latest updates. If necessary, I still have some medicine available. Edited November 15, 2017 by heinoganda Link to comment Share on other sites More sharing options...
SD73 Posted November 15, 2017 Share Posted November 15, 2017 Thank you my friend. Save the medicine for next month. I may need it! Link to comment Share on other sites More sharing options...
glnz Posted November 16, 2017 Author Share Posted November 16, 2017 Thanks heinoganda! Link to comment Share on other sites More sharing options...
bluebolt Posted November 16, 2017 Share Posted November 16, 2017 Perhaps the Office Compatibility Pack will receive security updates until April, 2018: https://www.microsoft.com/en-us/download/details.aspx?id=3 Link to comment Share on other sites More sharing options...
Dave-H Posted November 16, 2017 Share Posted November 16, 2017 Yes, it does look that way! I had a bit of a nasty moment when doing the latest updates. I had installed the three problem ones without incident, and then did the other four using MS Update. All went well until the restart, at which point instead of a normal restart, I was greeted by this - Not what I wanted to see! Fearing the worst, I restarted the machine, and it restarted normally and now seems fine (touch wood!) The only possibly relevant things in the logs are this in the System log - Event Type: Error Event Source: SideBySide Event Category: None Event ID: 58 Date: 16/11/17 Time: 22:29:40 User: N/A Computer: AshfieldCourt Description: Syntax error in manifest or policy file "D:\WIN-NT\WinSxS\Manifests\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.6028_x-ww_61e65202.Manifest" on line 5. For more information, see Help and Support Center at http://localhost:90/redirect.php. and this in the Application log - Event Type: Error Event Source: Windows Search Service Event Category: Gatherer Event ID: 3025 Date: 16/11/17 Time: 22:29:43 User: N/A Computer: AshfieldCourt Description: Critical error 9 occurred, and the index was shut down. The system is probably low on resources. Free up resources and restart the service. Context: Application, SystemIndex Catalog Details: Insufficient system resources exist to complete the requested service. (0x800705aa) For more information, see Help and Support Center at http://localhost:90/redirect.php. Whether they are at all relevant to the BSOD I don't know. A nasty moment! Link to comment Share on other sites More sharing options...
Yellow Horror Posted November 16, 2017 Share Posted November 16, 2017 (edited) 11 minutes ago, Dave-H said: Whether they are at all relevant to the BSOD I don't know. Is there any new files in the %SYSTEMROOT%\Minidump directory? Edited November 16, 2017 by Yellow Horror Link to comment Share on other sites More sharing options...
dencorso Posted November 16, 2017 Share Posted November 16, 2017 @Dave-H: That's a classic one! If your machine has a winlogon.exe which version is less than 5.1.2600.6443, I strongly recommend you to install this hotfix: KB2878379-v2. I've never again got a "c000021a" error after installing it. 2 Link to comment Share on other sites More sharing options...
Dave-H Posted November 16, 2017 Share Posted November 16, 2017 (edited) @Yellow Horror No, the most recent one is from last June. It didn't look like a normal BSOD. @dencorso My winlogon.exe is version 5.1.2600.5512. I'll try updating it. Edited November 16, 2017 by Dave-H Additions Link to comment Share on other sites More sharing options...
dencorso Posted November 16, 2017 Share Posted November 16, 2017 10 minutes ago, Dave-H said: My winlogon.exe is version 5.1.2600.5512 Then my diagnosis is right: your system fell victim of a race condition (a bug) existing between threads in winlogon.exe. It quite rarely manifests itself, but sometimes it does. Rest assured the crash you saw has nothing whatsoever to do with the updates you had just applied. Link to comment Share on other sites More sharing options...
liamZ Posted November 17, 2017 Share Posted November 17, 2017 8 hours ago, dencorso said: Then my diagnosis is right: your system fell victim of a race condition (a bug) existing between threads in winlogon.exe. It quite rarely manifests itself, but sometimes it does. Rest assured the crash you saw has nothing whatsoever to do with the updates you had just applied. Interesting!!, I didn't know about this!! Is there a list of available hotfixes for windows xp not included in windows update or even in the catalog? Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now