Dave-H

Thanks @sdfox7, but my message wasn't worded very well. It was only the policy templates file I was after, not Chromium as a whole! Incidentally your link to 49.0.2598.0 seems to just prompt the download of a 3.3 kb .nupkg file. Just out of interest, what exactly do you do with that?

I've always used large fonts on Windows 98, 2000, and XP. Even at 1024x768 on my old CRT monitor I did, as I just found the text too small otherwise, and on my present 1920x1080 monitor it's really essential! The text size on Windows 8.1 seems to be fine on its standard settings, so I guess MS finally got it right! I did find in the past that some programs did not display their dialogues properly with large fonts selected, but that's pretty rare nowadays.

Thanks 5eraph, that worked perfectly!

Wise words as always Den! I've not been tempted to apply SP4 as I too think that with the POSReady updates a SP3 XP installation is as complete and secure as it can be now. I would certainly use SP4 if I had to make a new XP install now, but not otherwise.

Oh dear, so I missed the boat! I suppose there isn't an archived copy anywhere of the last Chromium 49 version?

@5eraph I tried your instructions here just out of interest, and the necessary option isn't listed in the Group Policy template for me. There are loads of options, but not "Suppress the unsupported OS warning". It isn't there at all. Any idea why? I'm using Google Chrome 49.0.2623.112.

Officially they released 12.18 to update security protocols which were out of date and starting to compromise the browser's stability, as well as presumably its security. I and many others were getting frequent random sudden shutdowns on Opera 12.17 which was of course a real problem! Since upgrading to 12.18 I haven't had a single one. It's very slow indeed now with javascript heavy sites like Facebook and YouTube, and one of the worst things now is that the submission of forms sometimes doesn't work after you've filled them in, meaning you've got to start again from scratch in a different browser, which is really annoying! It's still a great browser, arguably the best ever produced, and I wish Opera's new Chinese owners would tell them to revive it!

Thanks for that, I will certainly have a look at those options now that my preferred one has gone! It's mainly annoying because Vivaldi were specifically trying to create a browser that would substitute for Opera 12 for power users, who use things like the unequalled user configurability of Opera 12, which will probably actually never be equalled. I've been using Opera for many years, and it was very sad indeed when Opera decided to go down the Chromium route and re-build the browser as a shadow of its former self, even though I understand their reasons for doing it. There is of course no guarantee that the latest versions of any browser will always work on XP.

@vwestlife Yes, I just saw that, sad but I suppose inevitable. I was really hoping that Vivaldi would eventually be a long-term replacement for Opera 12 for me. I guess if you want a supported in-development browser for XP now it's Firefox or nothing, but I'm sure that Mozilla will drop XP and Vista support as soon as it becomes in any way awkward to continue with it.

I take it that you have an ATI or AMD graphics card, as MOM is part of the ATI/AMD Catalyst Control Center, which is built on .NET 2.0 IIRC. Try uninstalling and reinstalling the Control Center and hopefully you'll lose the error message. MOM.exe should be in the C:\Program Files\ATI Technologies\ATI.ACE\Core-Static folder. That's what I have, later installs probably substitute AMD for ATI of course. What happens if you do try to uninstall SP4, you said it was now listed in the installed programs list?

Check here for the catalog files error message. This was referenced in the first post of this thread.

That looks as if the SP didn't fully install, although it did do the registry tweaks to continue getting updates, assuming you hadn't done that yourself. What happens if you run the installer again?

If it's downloading POSReady updates, you must have the necessary registry modification, which would have been done by the SP4 installer. You should be able to check that the SP is installed by looking at the system properties, which should I assume now appear like the screenshot in the first post of this thread. It looks as if it still says Service Pack 3, but the date changes to 2014.

Already covered here, but thanks.

All the offered updates installed fine here on both my XP machines. The yellow shield does often come back after subsequent restarts in my experience, showing some but not all updates as still needing to be installed. This month it's the IE8 update KB3148198 and one of the Office 2007 Suite updates KB3114542. This often seems to happen, but if I just hold my nerve the shield always eventually stops appearing after a couple of days!

Sorry, I don't follow you. What update.exe file do you mean?

So I guess there's no need to keep the installation file for KB3099866 any more?

Thanks Den, I could have found that myself of course if I wasn't so lazy! I assume a Windows 10 based version will appear eventually. Back on topic, my yellow shield has appeared this morning, so it looks as if it's all working fine still with no further registry modifications needed. Rather amazed that the KB3135993 .NET 4.0 update is one of those offered, it's been a very long time since a .NET update was actually offered to me through Windows Update and didn't have to be installed manually!

I doubt there will be a mass outpouring of grief! Just as an off-topic aside, out of interest, what is Microsoft's current offering for new systems that would have used WEPOS/POSReady? Is there some sort of Windows 10 based offering to replace them?

The last hurrah for .NET 4.0 I guess. I've now manually checked Microsoft Update, and the new updates are being offered to me now, so I guess the presence of the WEPOS key doesn't matter. Still no yellow shield in the system tray, I'll see if it appears tomorrow.

OK, I'll see if I'm offered any updates tomorrow (I don't usually see them until the Wednesday morning here in England) and if they're not coming through I'll see if I can delete the key using Windows 8.1 as I have a multi-boot system.

Should the HKEY_LOCAL_MACHINE\SYSTEM\WPA\WEPOS key be removed now, or does it not matter if the "Installed" DWORD within it is set to 0?

Working fine here too thanks.

Yes, that's the error I was seeing too. Let's hope it's fixed soon!

Did you manage to upload it @jumper? That link just produces an error message.