Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 05/09/2021 in Posts

  1. And why is this certificate expiry the death of Windows XP? (hint - it's not - almost nothing will change)
    5 points
  2. this update pack contains all the sha2 requirement updates for all windows versions to fix the sha1 issues in windows here is the download-----> [redacted] edit: just a note this update pack wont fix windows update not working these updates only add the sha2 support to windows it wont fix windows update on xp-vista sorry for the mislabeling this pack contains all the sha2 signed certificates needed to get drivers working in older versions of windows here is the download-----> [redacted]
    2 points
  3. You seem to think that Windows Update stopped working for Vista and earlier last year only because users did not install certain updates. What gave you that idea? Windows Update no longer works for Vista and earlier because Microsoft does not want it to work for them anymore. Dave-H and others in this thread have fully-updated XP systems, but Windows Update only gives them an error. If anyone reading this wants to update Vista, greenhillmaniac has a complete repository. As for Windows 7, the only update that has thus far been needed to get Windows Update working is SP1. Perhaps that will change today, but there is no immediate danger of Win7 updates being removed from the Catalog.
    2 points
  4. No. The driver sigs are timestamped. Check out your drivers with "valid" signatures, that don't complain about being unsigned... You'll be surprised to see many or even most have expired certificates. For these, it only matters if the certificate was good at the time of signing. Anyone besides M$ can still SHA-1 code sign executables if they want to.
    2 points
  5. 2000 - MSDOS y2k 2011 - Windows 9x and NT4 y2k 2020 and 2021 - Windows NT5 y2k
    2 points
  6. The staff is aware that there are currently spambots sending out private messages to random members here on the forum. We are actively dealing with the situation but if you happen to get one of those spam messages, please do not simply ignore or delete it but use the report system so that we can permaban every account responsible for these messages. Thank you for your patience!
    1 point
  7. Posts relating to the expiration of SHA-1 certificates moved here.
    1 point
  8. No. This certificate does not affect web browsing or internet connections as it is for completely unrelated things than that.
    1 point
  9. unless you use microsoft applications that needs internet connections (as far as know all those dropped xp support) there is no worry. Just use MyPal or Newmoon webbrowser and Mailnews email client and you will be fine
    1 point
  10. ^^ I'm feeling: Unsure (about corona)
    1 point
  11. Only issue I could see is possible driver errors (due signatures) on any newer drivers made after that date to xp but it will likely just trigger signature warning about not passing XP logo test (like some devs actually cared sign their drivers to XP after 2014). Second may be warning on starting application made after date that will happen anyway in 99% of sw but it wont kill XP. mine is still kicking strong. It did not explode, can still access web, install files
    1 point
  12. 1 point
  13. @legacyfan we hope you shall stay this time .
    1 point
  14. yeah, upstream messed up addon manager, it is fixed in my side, archives updated.
    1 point
  15. im back on here after a few months of nothingness im happy to be back!
    1 point
  16. From February 8th, Roy said:
    1 point
  17. Thanks for the reply. Not a problem at all, real life has been a bit hectic for me as well with a lot of medical stuff going on this last week so we have to prioritize. I appreciate everything everyone has done, so we'll wait and see then. I have this 'gut feeling' (though it could be indigestion .. hehe) that we're gonna be just fine come Sunday. As I've said, this was a learning experience for me, as I (fully) admit, this was (way) over my head, but better late than never to learn; so they say. Everyone in this thread was very helpful. I think @Gansangriff really 'took one for the team' and updated as this member (so i gather) also doesn't normally update. This doesn't prove we are (in some way) unwilling to let go, rather we are determined. I'll say it again, MSFN rocks!! ~OT~ Well, if they have to delete anything you wrote @Dixel, than practically everything I write here would deleted as I tend to go a tad (just a tad) off track now and again myself, so thank you for putting up with me
    1 point
  18. I have a pertinent question... Why create a thread, when this topic is already being discussed: https://msfn.org/board/topic/181739-windows-update-error-code-80072efd/ https://msfn.org/board/topic/178377-on-decommissioning-of-update-servers-for-2000-xp-and-vista-as-of-july-2019/ Furthermore, you're linking to the Server 2008 update repository that I created without any kind of credit. Honestly, this thread seems pointless...
    1 point
×
×
  • Create New...