Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Dave-H

Platinum Sponsor
  • Content count

    1,809
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

124 Excellent

About Dave-H

  • Birthday 03/31/1953

Profile Information

  • OS
    XP Pro x86
  • Country

Recent Profile Visitors

4,493 profile views
  1. Thanks again Rudolph, yes I'll certainly give that a try if I'm still getting problems. I got a notification for your posts OK.
  2. Thanks, I haven't knowingly changed my notifications for years, but I thought it was possible that the outage a few months ago might have scrambled things, so i checked, and it looks correct. Those are my settings, and they look like what I want, with a separate e-mail for every added post.
  3. I got a notification for your post as well, but nothing for the previous eight before mine, but that may have been because I didn't visit the forum again until I next posted. Are the certificate errors you're seeing just about a name mis-match? If so, you can just switch those warnings off in the internet settings.
  4. I've now set up a scheduled task to run @heinoganda's certificate updater automatically on Patch Tuesday every month. I'll leave the automatic updates turned off unless and until someone reports that it's fixed. I hadn't realised that they were doing the same thing anyway! When updates happen, is the old certificate information replaced with the new information, or will any old certificates that aren't in the new update remain on the system? Is anyone else getting e-mail notification from this thread BTW, as I don't seem to be, although I am getting them from other threads?
  5. Dave-H

    No E-Mail Notifications?

    You've got me wondering now whether the notifications from MSFN do actually work that way! I know they do on some forums I subscribe to, but thinking about it I may well have had multiple notifications from the same thread in the past without having visited the thread.
  6. I have both those entries in my Add/Remove Programs. Searching for the winusb.dll file brings up the same version (6.1.7600.16385) in system32, but there are copies of the file in two other folders relating to connectivity software for mobile phones, both my old Nokia phone and my current Samsung phone. The copy in the Samsung folder is older (6.0.6000.16386), the one in the Nokia folder is the same as the one in system32. If you have similar software installed that may well be where it came from.
  7. Dave-H

    No E-Mail Notifications?

    It seems to be very erratic for me. I've had quite a few e-mail notifications during the last few days, but before that it seems I wasn't getting them as I checked to see if there were any responses to a post I'd made, and there were several which I hadn't been notified about! You don't get a notification for every post anyway, only for the first one since you last visited, but even that did not seem to have happened. Touch wood it's OK at the moment though, at least for me.
  8. Thanks, so I guess switching off the automatic updating system and just using the manual updater when prompted (or on a regular schedule) is the answer. I'm actually quite relieved that this does not seem to be a problem just on my systems, and is actually yet another problem caused by Microsoft's flaky updates! Actually I've always been surprised that we're getting the automatic updates at all, but I assume this is for the benefit of "real" POSReady systems, which are still supported. If enough people with them complain about the endlessly logged errors, perhaps it will get fixed, but I'm not holding my breath!
  9. Bizarrely, when I download authrootstl.cab now, its contents are dated 21st August 2018, which I don't understand at all! Still doesn't work though. Well if, as you say, the automatic crypt32 updates do exactly the same thing as @heinoganda's manual updater does, there is no point in using both. I guess as you say that what MS is serving through the automatic system is now just very out of date, and therefore throwing errors. Strange though that the automatic update system is still trying to do updates when the manual updater has been run, so the latest certificates should already be there! Were it not that this is presumably happening on "genuine" POSReady systems as well as hacked XP systems, I would say that it was something that won't be fixed, but if it's happening on supported system, it should be fixed! Mind you, look at how long it took them to fix the forever scanning Windows Update issue..........
  10. Thanks, yes I was aware of the option to disable the function, although it probably hadn't been specifically mentioned in the thread. I was hoping to fix the problem though of course, rather than just working around it by disabling the function! If it proves to be a function that fundamentally no longer works on XP, I will switch it off of course, but I haven't quite yet given up on finding a fix!
  11. Thanks, I'll look into that!
  12. Thanks as always @heinoganda! I have run your batch file before, and done manual cleaning too, but clearing the certificate caches and deleting the certificates themselves only seems to work for a short time, and then the errors just come back again. I really don't want to get into effectively creating a new XP system to test whether this occurs again with that, it's a lot of trouble with no guarantee that it would reveal the source of the problem. It's happening on two completely independent XP installations on two machines, which would seem to indicate to me that it's pretty ubiquitous, even if not everyone seems to be seeing the errors. Fundamentally, it looks as if Windows Update is serving an out of date file to the system, which is throwing error messages because there are a lot of expired certificates in it. Deleting the expired certificates will not do any good of course, as they will just be downloaded again! Presumably there is an up to date version of the file being served to later versions of Windows, but I don't know what address it's coming from. If it was possible to find that out, it might be possible to change the Windows Update download address so XP and POSReady systems get the current version.
  13. Well I've just manually downloaded authrootstl.cab and extracted the authroot.stl file from it. Looking at its contents, it dates from 22nd September 2017, so it's nearly a year old, and it contains a lot of long expired certificates! Why is Windows Update serving such an old version, and is it possible to change it to download the current version, even if it's not intended for XP systems? Presumably this problem must be happening on genuine POSReady systems?
  14. Good, well that's three of us at least with the same issue! I'm sure he will correct me if I'm wrong, but I don't think running or not running Heinoganda's certificate updater has anything to do with these errors, as I think that updates something different to what the crypt32 updates are. As those crypt32 automatic updates are still happening, and were for ages after XP EOL before the errors started, they must be something different to what the certificate updater is designed to update, which is presumably something now no longer updated automatically by the OS. As I said, I've never run the certificate updater on my netbook, or done any other manual updates or alterations to any of the certificates system on that machine, and the errors have started there too, although they did take a lot longer to start appearing there than they did on my main machine for some reason.
  15. A good thought, but I don't have Eudora installed on my netbook, so it can't be that!
×