Jump to content

Vistapocalypse

Member
  • Posts

    1,082
  • Joined

  • Last visited

  • Days Won

    14
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Vistapocalypse

  1. Obviously you were able to install new definitions, but are you hinting that an older engine must be used now because M$ introduced one that is incompatible with Vista?
  2. OK, VirtualBox support for Vista x64 is definitely still ONG! Now I notice the old Windows Defender icon on your system tray, and it looks like definitions need to be updated. If you are running build 6003 with SHA-2 support, then it should be possible to manually install definitions by downloading file mpas-fe from Microsoft. Does that still work for you in September 2020?
  3. Thanks for posting so promptly! If you have tried the very latest 6.1.14 released September 4, then case closed: False alarm. Documentation regarding supported host operating systems was reportedly updated with 6.1.0, so any support for Vista x64 is unofficial now. The poster has a Pentium T3200 that may not support virtualization.
  4. Under Virtualization Software, Oracle VM VirtualBox is listed as ONG; but a post at another forum strongly suggests that is no longer true for Vista (and perhaps not even for Windows 7). VB only supports 64-bit hosts now, so my old Vista rig isn’t suitable for testing. If anyone can identify the last version for vanilla Vista, please post.
  5. Hello @VistaLover. It looks like you were able to manually install definition version 1.321.787.0 created on August 6, 2020. Are you still able to manually install mpas-fe files? I only ask because of an AskWoody thread Defender updates no longer install on Vista, much of which sounds like baloney to me. If I may be allowed one more silly question, does your Vista laptop have an NVIDIA card? That thread contains a peculiar hypothesis that updating to build 6003 causes a black screen of death on Vista systems with NVIDIA cards.
  6. There will be one less working option beginning in early 2021, but it’s so unpopular among the XP diehards here, this news might be cheered instead of jeered: Norton Protection End-of-Support Announcement for Windows XP and Windows Vista
  7. You must be referring to https://forums.mydigitallife.net/threads/windows-vista-bypass-eol-with-windows-update.81026/page-2#post-1617010. It sounds like a Server 2008 license would be required. For mere mortals, it might be a lot easier to just switch to Server 2008.
  8. Norton Protection End-of-Support Announcement for Windows XP and Windows Vista: even definition updates for the Maintenance Mode version will cease early in 2021. Edit: Version 22.15.3 will most likely be the final version then.
  9. Since you are not actually using the Download Links that are the topic of this thread, I think @dencorso or another administrator should split your personal updating adventures into a separate thread. That is incorrect! If you aren’t bothered by Server 2008 updates as long as the build number is 6002, then March 2019 updates are the last. April 2019 updates are the first to change the build number.
  10. He obviously prefers the last version that does not contain a time bomb. For your purposes, Silverlight might be more significant. Edit: But probably not, since DRM support is “No.”
  11. I checked file starter-final.zip posted by SIW2 for post-EOL updates, but it does not contain any. I did not count the updates, but there are perhaps 200 or less. Build 6003 didn’t actually appear until April 2019, so it was possible to install a large number of Server 2008 updates without changing the build. Microsoft regarded KB4499180 (May 2019) as so critical, they even urged Vista users to install it; but it changed the build to 6003.
  12. Also greenhillmaniac’s Windows Vista Update Repository has Ultimate Extras folders in both the x86 and x64 folders.
  13. Welcome to MSFN. Windows Update is never going to work again and might as well be disabled, “Speedup” updates are no longer relevant: Windows Update SHA-1 based endpoints discontinued for older Windows devices.
  14. IDK what changes were made on Sep 1, but posted that link in decommissioning thread July 31 and believe it was already a month old then.
  15. WUMT has already been discussed at length in the “decommissioning” thread beginning here and rambling on for several pages. The version at your Major Geeks link reportedly isn’t old enough. Even with the right version and cab file, some say it works (at least following a clean install), while others say it doesn’t work... Edit: See this post regarding WUMT version that might work.
  16. That’s how it is for Vista now: Download Center links are broken but the catalog still has the updates.
  17. Looks like eM Client 7.2.36694.0 came from a long list of additions suggested by @Werewolf on December 14, 2019. I would speculate that the problem might be related to the Chromium rendering engine introduced one version earlier according to Release history, so maybe try two versions earlier. They actually fixed a Vista issue with 7.1.30508.0 in June 2017, so support was ONG then.
  18. @Monroe does your XP system have the correct date and time? Any significant changes since July 30?
  19. On W7, see if you can access the same page using Internet Explorer 11. I think you can, even though ED_Sin informed us on the previous page that W7 does not support TLS 1.3. I’m not really any authority on Chromium browsers, but suspect your issue is just Chrome policy.
  20. One person reports database updates still working: https://www.bleepingcomputer.com/forums/t/692669/malwarebytes-unable-to-access-update-server/?p=5051248
  21. Then upgrading IE8 (and therefore your system) to TLS 1.2 might help in some cases, depending on the cipher suite that is required.
  22. I don’t use 360 Extreme Explorer myself, but without much difficulty I found a post by @ED_Sln that seems to explain: https://msfn.org/board/topic/178380-extreme-explorer-360-chromium-78-general-discussion/?do=findComment&comment=1180393. Edit: I’m not running W7 either, but it must have systemwide support for TLS 1.3 now. (Too bad that can’t be done for XP or Vista: only TLS 1.2.)
  23. There’s an old thread Upgrading IE8 to TLS 1.2. Personally, I’ve only done that for IE9 on Vista. TLS 1.3 is not possible for your IE but is possible for Firefox 52.
×
×
  • Create New...