Content Type
Profiles
Forums
Events
Everything posted by Dave-H
-
Well my netbook finally showed me the list of updates on IE8 sometime during the night last night, after scanning since the afternoon of Wednesday 11th. I think five days has to be some sort of record! All installed fine. Let's hope things are better in future now that the Office updates have ended.
-
LOL! It will be interesting to see what happens next month with no more Office updates. The netbook's still scanning BTW........
-
Finally updated my main machine, using the normal IE8 interface. I started it scanning at 1230 yesterday, the yellow shield finally appeared at 1930, after 7 hours, and the scan completed and showed the updates on IE8 sometime during the night! All installed OK. My other machine, the netbook, is still scanning after 48 hours, the yellow shield appeared after about 36 hours of scanning. I'm being very patient.........
-
My two machines are taking an eternity to scan as before, but I'll just let them take their time and see how long they actually do take, I'm in no hurry! It will be interesting to see if in the future with no more updates for Office whether the scan times do reduce, as these seemed to be the main culprit. I seem to remember that the last time there were no Office updates for a month, it was a lot better.
-
Root Certificates and Revoked Certificates for Windows XP
Dave-H replied to heinoganda's topic in Windows XP
All updated, thanks! -
Do you have Microsoft Office with the Office 2007 Compatibility Pack installed on that machine? If so, that is the reason that the update scanning is taking so long. If you manually install any Office updates first, the scan should then work quickly. Any Office updates should be recorded in this thread, with links to them.
-
I wasn't aware that there was any problem with KB4039384, if anyone mentioned a possible one it wasn't me. If there is an earlier version of xpsp2res.dll in KB4039111 it doesn't seem to have overwritten the newer version when it was installed, which is good (presumably).
-
Just a quick clarification. My xpsp2res.dll file is version 5.1.2600.7248 (despite having installed KB4039111). My USP10.dll is version 1.420.2600.7334, and GDIPLUS.dll is version 5.2.6002.24180. I'm using Office XP(2002) with the 2007 Compatibility Pack. Does that sound right, or do I need any more updating?
-
The six offered updates installed fine for me. It took ages to scan again due to the presence of the Office updates. Are these likely to be the last ones, or will there be some more next month I wonder? I read somewhere (here probably!) that support for the Office 2007 Compatibility Pack ends next month, which would make sense as it's presumably 10 years after it was launched. I've also installed the optional update KB4039111. Anyone know what this actually is? Its page on the MS site, which is linked to from many other sites, is just "page not found"!
-
OK, I've now just deleted the PinRules which had expired. I had to delete the websites that were using them (which was all of those listed) before EMET would let me do that. I did read somewhere that these "protected sites" (Yahoo, Twitter, Facebook etc.) are only actually protected by EMET when using Internet Explorer. Is that right? If that's the case there's no point in having them set up anyway, as I never use IE now for websites, only for Microsoft Update, as the sites don't usually work properly now in IE8 anyway!
-
I'm getting security alerts popping up when I read some e-mails on Eudora 7.1. They say "the name on the security certificate is invalid or does not match the name of the site". If I dismiss them everything carries on fine. Viewing the certificate and installing it seems to make no difference. The one I'm looking at at the moment is issued to *.stackpathdns.com and I'm wondering if the wildcard asterisk is the problem.
-
So is EMET effectively now completely obsolete? I downloaded the latest version (5.52) and the installer contains the same PinRules that just expired. If you have the latest version installed (not on XP obviously) does it update the PinRules automatically still to a later version?
-
I'm now getting error messages in my logs that four EMET PinRules expired on the September 1st. Anyone any idea how I can update them? I'm using EMET 4.1.
-
Thanks Thomas, that's a good shout, but unfortunately Flash is enabled on Facebook for me, and always has been, but the GIFs still don't work. I'm wondering now whether they ever did actually work on Windows XP. I still think that H.265 is probably the key, it's probably supported natively in Windows 10 but not in XP.
-
Just as an aside, Adobe Reader XI is now up to version 11.0.22 for anyone who still uses it. I wonder how long they will keep updating it?!
-
KB4025398 was included in July's updates for me. It's to patch a vulnerability in MSInfo. I would install it manually if you haven't got it.
-
I've noticed that GIF animations don't work in my Facebook newsfeed on Firefox 52 ESR on Windows XP. They work fine (of course) on Firefox 55 on Windows 10. On XP I just get a white rectangle where the animation should be in the newsfeed, but if I click on it and it opens up bigger it then plays. I read somewhere that the Facebook animated GIF player needs the H.265 codec. Is that so, because if that's the case presumably it can never be made to work in XP. Do inline GIF animations work for anyone else with this configuration?
-
Ah, well if you're using add-ons that relate to YouTube that could be part of the problem. A friend to mine is using the latest Firefox 55 on Windows 10, and he told me a while ago that YouTube clips embedded in Facebook pages had stopped working, just producing an error message that no codecs could be found to play them. Why this should happen was a bit of a mystery for a while, on what should have been a state of the art system. He was also getting errors shown on two of the items here, the H.264 one and the WebM VP8 one. To cut a long story short, it tuned out that he had several add-ons installed relating to YouTube. Running Firefox with add-ons disabled seemed to make no difference to the problem, but when they were all actually uninstalled, everything came good! Worth a try to see if this has any bearing on your problem, you can always re-install them again (make a note of what they're called before you uninstall!)