Dave-H

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?

Yes, the option should be there if you click the "change settings" link on the left hand side, down at the bottom of that settings page. There's certainly an option there for me to switch back to Windows Update if I want to. Of course I'm sure you can always go straight to Microsoft Update anyway by using this link - http://www.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us

Link doesn't work, whatever it is!

The "Custom UserAgent String" add-on seems to do the job! I now have the default UA set to normal, and just send a different one to Facebook, so the videos work properly. All seems fine, but I'll be back if I find any other problems, and thanks for everyone's help as always!

One thing I've found straight away with the new arrangement is that going to the Firefox add-ons page now tells me that most of the add-ons aren't compatible with my version of Firefox! It fact is was quite frightening to find out just how many add-ons will not work with Firefox 57. There's going to be tears and tantrums from many Firefox users later this month mark my words! I will try to find an add-on that will allow UA spoofing on a site by site basis, as that seems to be the best answer. I can then change the UA only on sites that need it changed, as I used to do with Opera 12.

Classic Shell is wonderful (and no, I don't work for them ). It's one of those programs that's so good IMO that you can't believe that it's actually free! It was the only thing that made Windows 8/8.1 usable for me.

Doesn't work for me with Windows NT 5.1 in the UA. Like Facebook, it then wants to use Flash. Do extensions like User Agent Switcher allow site by site UA changes? Looks like Firefox 52ESR has a short stay of execution until next June.

Sadly not, Facebook wants to use the Flash Player for videos again with that UA. I guess it's sniffing the OS version as well as (or instead of) the Firefox version. Is there any way, preferably without using an extension, of changed the UA just for a specific site? You can to do that with Opera 12, but of course you can do a lot of things with Opera 12 that you can't do in any other browser!

Just to come back on this, I eventually restored the "Connect" app by doing a repair reinstall of Windows 10, which I guess is the only way to do it! I was then still getting the error messages on every boot about the system being unable to uninstall the Miracast app. I found the source of the problem eventually by a registry search, which I'll pass on for anyone else seeing this. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Deleted\EndOfLife There will be an entry for the Miracast app there, which shows how many times the system has tried to remove it, so it looks as if the system is trying to delete it on boot as "End of Life" for some reason. I deleted its entry, and the errors went away. Why it was trying to delete Miracast I have no idea, I can only assume it's because my system doesn't support it. Miracast appears in the apps list when viewed with Powershell, and it says it's OK, but there is no installed folder listed (it should be in C:\Windows\Miracast, which doesn't exist on my system) so I've no idea what its status actually is. Anyway it doesn't seem to be doing any harm, and at least the error messages have now gone away, let's hope they stay that way!

I'm less concerned about websites generally thinking you're not using XP as I am about Mozilla thinking that, as they haven't yet said whether they will keep on supporting 52ESR beyond its normal life expectancy. They did say they would make a decision based on the number of users that they detected were still using XP or Vista. I assume that changing the user agent will not change the data that Firefox sends back to Mozilla, so hopefully this will have no impact on that. Going to Mozilla's website now tells me I'm using a pre-release version of Firefox!

Thank you so much guys! Spoofing the user agent has completely fixed it! I love this forum so much..........