Dave-H

Well I'm not holding my breath for any patches for my 2009 motherboard and processors!

Just got the update on my Windows 10, which just uses the built-in Windows Defender. It will be interesting to see if we get another update in a weeks time when it should have been! No sign of anything for POSReady/XP as yet on Microsoft Update.

That whole message was just spam? Shows how perceptive I am about that sort of thing! I guess it was just to get you to go to moviesonline.gy?

@yazzie03 Why have you got exactly the same signature as me, surely we can't possibly have identical machines!

The last full version of AutoPatcher was released in December 2007. The file is 286MB. Subsequently an update was released in December 2008, which should be 45.3MB. You cannot use that by itself, install the full version first, and then the update.

Indeed so!

I have no idea what you mean by that!

Well this month everything seems to be back to normal! It says "x64-based" again in the label for the Cumulative Update instead of "amd64-based", and the Malicious Software Removal Tool entry looks normal again now too. I guess last month was a one-off glitch!

LOL! Thanks, that explains it. It never occurred to me that was the reason as everything in your version is still in English, even the text in the Window title bar!

Thanks! Mine are now the same apart from the time stamps being one hour different as they always are. Always been puzzled why my updater has slashes as dividers in the dates, and yours has full stops!

Same issue here. Error 0x80248015. Hopefully just a temporary glitch. I think that error refers to a connectivity problem.

Thanks for this! The exe installer downloads seem to be working now for me.

Strange, that box displays absolutely fine in my copy of Firefox 52ESR, and I haven't done anything special to make it work.

Thanks as always den! I've installed the update and all seems fine. My winlogon.exe is now 5.1.2600.6443. I guess I was lucky that BSOD hadn't happened before if my system was vulnerable to it. It was just bad luck that the first time it happened was just after a set of updates, which made me think that one of them had caused it of course! I'd be interested to know too if there are any other patches like that which we should have, mainly because presumably eventually Microsoft will remove them. Cheers, Dave.

@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.

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!

Thanks guys. I won't worry about it, and I'll wait with interest to see what happens next month! Cheers, Dave.

Thanks very much! That probably explains why my system is being detected as amd64, but it doesn't explain why the labelling of the updates in the list has apparently suddenly changed. Presumably this applies to all systems, not just mine, so is everyone now seeing this? As I said, the Flash Player update is still labelled x64 as it always was. As you said, probably just Microsoft being Microsoft! The Malicious Software Removal Tool is a bit of a mystery though, as the catalogue shows a version for "normal" Windows 8, 8.1, and 10. Why I would be getting a different version (which may not actually be different at all of course) is very strange. Anyone else seeing this?

Thanks, that's interesting to know, I had noticed folders called "amd64....." on the system myself, and wondered why. However, I'm pretty sure that my Windows Updates were not labelled with "amd64" before, I'm almost certain that they always said "x64" until today.

Well true enough, but a bit of a surprise!

I've just had the latest Patch Tuesday updates, and am a bit puzzled by the labelling of a couple of them in the "View installed update history" window. The main update is labelled "2017-11 Cumulative Update for Windows 10 Version 1709 for amd-64 based Systems (KB4048955)" The Malicious Software Removal Tool is labelled "Windows Malicious Software Removal Tool for Windows Insider Preview and Server Technical preview x64 - November 2017 (KB890830)" I'm not on any "preview" version of Windows 10 as far as I know, and surely the first one should say "x64" not "amd-64" on an Intel-based system, which mine is? The Flash Player update seems to be labelled as I would expect. Is everyone seeing this, and is it actually wrong?

I thought support for Office 2007 and the Office Compatibility Pack, and therefore their updates, ended last month??

If you are accessing Microsoft Update rather than Windows Update, as you clearly are, it should be offering you updates for Office if you need them. However, as has been stated, at the moment the presence of any Office updates will cause extremely extended scan times, so you are far better off finding and installing all the Office updates manually.

Always worked fine for me too, I'm using version 1.7.

So if you changed the setting, what are you now getting if you click the "Windows Update" entry on the "Tools" drop-down on the menu bar of IE8? Are you getting Windows Update or Microsoft Update?