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. 


All Activity

This stream auto-updates     

  1. Past hour
  2. Today
  3. Hmm, before installing KB4474419 you are supposed to install the April 2019 servicing stack update KB4493730 (at least according to Microsoft), and the September 2019 SSU might not be a bad idea either. I have no idea what effect this might have regarding MSE definition updates however.
  4. What do you actually mean by that? Please download latest 64-bit mpam-fe.exe from the link below: https://go.microsoft.com/fwlink/?LinkID=121721&arch=x64 and save it in a location you have write access - please note down its actual file version; at the time of this writing, the latest file I can pull down is of v1.321.1115.0 (~ 107MB) Open then your MSE (x64) app and switch to the "Update" tab; note down the "Virus definition version" displayed (consult the screengrab uploaded by @SIW2 ). Then launch the previously downloaded mpam-fe.exe file (if you are under a limited User account, it may be necessary to run the file "as administrator"); it performs a SILENT install/update, do not expect a GUI to pop up... Give it 3 to 4 mins and revisit the "Update" tab of MSE; if the "Virus definition version" displayed now has been raised, compared to its previous value, then ALL IS FINE! You have successfully updated your MSE - repeat the process as needed...
  5. Yeah, I still haven't been able to get mpam-fe64.exe to do anything of late... this might be something weird going on actually, I don't know what, exactly, but it's possible others with MSE are also having similar issues. I don't actually have MSE installed on my W7, just Defender (native), and that updated its definitions fine when I told it to. Seems something Vista-related is going on.
  6. This is what it showed on 8th August. I didn't download the definitions myself, so mse must have. I installed mse. Then rebooted. Not more than a few mins later, I installed the kb4474419. Possibly it downloaded the mpam thing before I installed kb4474419. Then mse was able to install those updated defs it had already downloaded . I don't have any other theories. The os was freshly installed on 8th August, so there was only that one incident of mse downloading the defs.
  7. Yes. On 8th August, it downloaded and installed the definitions by itself. On 9th August, it refused. The only post 2017 update installed is kb4474419. Is it possible it downloaded the definitions, before I installed kb4474419, and only after installing kb4474419 it installed the definitions it had previously downloaded. Maybe, because I installed mse first. At some point, I will go and fetch from the link you posted and see if it will work that way.
  8. Yesterday
  9. ... You must've gotten the wrong file, then... "mpas-fe.exe", whether 32 or 64-bit, is the standalone offline installer for updated anti-spyware (as) definitions; this file should only be used to manually update Windows Defender, Vista's native anti-spyware solution! "mpam-fe.exe", whether 32 or 64-bit, is the standalone offline installer for updated anti-spyware (as) + anti-malware (am) definitions; this file should only be used to manually update MSE (NB that when MSE is first installed, WD is being de-activated, so as not to conflict with MSE, which is both an anti-spyware and anti-malware solution!) You should probably only download from the (revamped) Microsoft Security Intelligence portal: https://www.microsoft.com/en-us/wdsi/defenderupdates Definitions for MSE there get updated 3-5 times during the course of 24h, but probably once a day is a sane frequency to manually update... You can read the Release Notes below: https://www.microsoft.com/en-us/wdsi/definitions/antimalware-definition-release-notes ... for latest as well as the previous 19 releases...
  10. I just manually installed 2 days ago so unless something has changed since then, that works great.
  11. Yes, it does sound like SIW2 was talking about updating definitions from within the UI - something that wasn’t possible in July 2019 (at least not without SHA-2 support, which I did not have then). If manual installation is still possible, it’s worth mentioning that “do-it-yourself” methods of automation were discussed earlier in this thread. However, none of this changes my mind about the client’s lack of effectiveness.
  12. I manually install the definitions, though I don't do it everyday, only now and then. I installed definitions 2 days ago so my MSE right now is still happy about that. What's weird is Vista 64-bit definitions are now called mpas-fe.exe... typo on Microsoft's part?? It's also only half the size of the previous mpam-fe64 that I had. I do indeed get the same error described when trying to auto-update in MSE. I haven't tried auto-updating MSE at all recently on any OS except W7 where it still works AFAIK. This is the other link I had for definition updates, which is the one I used last time, which gives me a 107 MB mpam-feX64 for 64-bit: https://support.microsoft.com/en-us/help/971606/how-to-manually-download-the-latest-definition-updates-for-microsoft-s It is slightly larger (about 1 MB) than the one I installed 2 days ago, which was about 106MB. Having some difficulty trying to get it to run but I've been having trouble getting pretty much everything to run lately on there so I won't give up yet. Eventually, it might work.
  13. Hi @SIW2 When I first quickly read your post as an e-mai notification, I must have got it wrong , believing that the "is not working" bit meant that the whole app itself somehow stopped working ; this doesn't seem to be the case, most fortunately! The "it cannot install the definition update." bit I believed it to mean that the MANUALLY downloaded "offline" standalone defs updater, file mpam-fe.exe, ceased being able to be run/installed; that doesn't seem to be the case, either... By "It was fine yesterday" do you actually mean that before August 9th, 2020, MSE on your Vista SP2 install was able to (automatically/manually) fetch and install updated MSE definitions via Microsoft/Windows Update (that's what the big "Update" button does, it searches MU)? If affirmative, that would be the first such mention... On my own system, MS/WU quit fetching anything in mid-July of last year, and that included Windows Defender (WD) defs updates... Installing SHA-2 code-signing support to the system, alas, did not change things... You obviously have SHA-2 code-signing support installed, if you were able to get current (prior to Aug 9th) defs updates installed; but that support augments Vista's build number to 6.0.6003, and WU (when it worked) gave it the cold shoulder; that's why I'm quite sceptical of your report.. In any way, Error 0x80244019 when checking manually for defs updates in MSE is because dear M$ has shut down the WU infrastructure for Windows Vista ; this has been reported and detailed elsewhere in the MSFN forums... (EDIT: @Vistapocalypse posted while I was in the middle of composing this message...) The only solution is to download manually (e.g. once daily) the standalone updated definitions installer, mpam-fe.exe, from MS's security portal: https://www.microsoft.com/en-us/wdsi/defenderupdates and run that file to get you up to date... (Scroll down to the MSE section and select the bitness of installed MSE; download and run file mpam-fe.exe) Please report back, MSE on Vista SP2 shouldn't be dead yet! @Dylan Cruz , what is the situation there?
  14. Yeah, 80244019 is the same error code as updates for Vista itself (e.g. here). Oh well, at least M$ has spared me from arguing that AMTSO test results were shockingly bad (which often fell on deaf ears). Almost everyone understands the importance of definition updates, so this should settle the question: barring some sort of miracle, MSE is dead on Vista. Edit: But I may have spoken too soon.
  15. Hello to all! I have a laptop based on Haswell Core i3 4030u with integrated HD 4400 graphics. How to install drivers from vin7 and make the graphics work ??
  16. I will not open an account when a palemoon competent person is on msfn. I have never seen such an overgrown status bar. I am not happy, I will only throw away such an inventor. Shame!
  17. Any chance for an ATI Mobility Radeon 8790 w2k driver ?
  18. OK, I restored the SoftwareDistribution folder from my backup, and the error messages in the Event Log have gone away thank goodness! Something must have got corrupted in there. I guess I'll just leave things well alone now, although I'm still puzzled as to why the latest wsusscn2.cab will just not work for me, no matter how I try to deploy it. As I said, the earlier one I have from 2018 works fine, at least in MBSA and WUMT. Are there any versions between the 2018 one and the current one still available to download anywhere so I can try them? This is in the XML file in the 2018 cabinet, looks like it was issued in November 2018. <?xml version="1.0" encoding="utf-8"?><OfflineSyncPackage MinimumClientVersion="5.8.0.2678" ProtocolVersion="1.0" PackageId="22a18bc5-f805-4490-b510-4f1c71ba6261" SourceId="cc56dcba-9026-4399-8535-7a3c9bed7086" CreationDate="2018-11-18T01:19:21Z" PackageVersion="1.1" xmlns="http://schemas.microsoft.com/msus/2004/02/OfflineSync"><Updates><Update CreationDate="2018-11-13T18:00:08Z" DefaultLanguage="en" UpdateId="a3169b82-874b-4eb9-a790-88dbcf9f785d" RevisionNumber="201" RevisionId="27769579" IsLeaf="true" IsBundle="true"><Categories><Category Type="Company" Id="56309036-4c77-4dd9-951a-99ee9c246a94" /><Category Type="Product" Id="a3c2375d-0c8a-42f9-bce0-28333e198407" /><Category Type="ProductFamily" Id="6964aab4-c5b5-43bd-a17d-ffb4346a8e1d" /><Category Type="UpdateClassification" Id="0fa1201d-4330-4fa8-8ae9-b877473b6441" /></Categories><Prerequisites><UpdateId Id="37e61eda-4a37-4625-88c1-7af8c0b61979" /><UpdateId Id="4103af66-247a-4782-b970-8899394c27c3" /><UpdateId Id="0fa1201d-4330-4fa8-8ae9-b877473b6441" /><UpdateId Id="a3c2375d-0c8a-42f9-bce0-28333e198407" /></Prerequisites></Update><Update CreationDate="2018-11-16T19:28:22Z" DefaultLanguage="en" UpdateId="f0073aff-33ce-456d-9e9c-103a3472e417" RevisionNumber="201" RevisionId="27769578" DeploymentAction="Bundle" IsLeaf="true"> Any versions from 2019 still around to download? I wonder if those of us with Office 2010 installed will see a yellow shield in the system tray in a couple of days time? I'm not holding my breath for it!
  19. I am happy to report that on Dell Latitude e6540 the USB predicament has been overcome
  20. That’s interesting. Assuming there is no issue with the latest MSE version (“only” 4 years old) on Windows 7 (and a hasty search found no reports), then M$ is of course the logical suspect. I’m sure you have SHA-2 support installed, so that’s not the issue. I wonder if Server 2008 SP2 (which MSE did not officially support) is also affected. If someone had asked me in 2016 what antivirus to use for Vista, I would’ve recommended MSE without hesitation. (My first post as an MSFN member was on page 1 of this very thread.) It’s sad that subsequent developments forced me to become an MSE naysayer.
  21. Hi, I'm using Windows 10 with Aero Glass and Translucent TB. When certain apps are playing animations, I get a very strange artifacting/screen tearing problem. It tends to happen mostly with Windows Store apps and browsers playing YouTube videos. It also sometimes happens while watching a Discord screenshare. It's difficult to replicate because it doesn't happen consistently, and I also can't get a capture of it. [Doesn't appear on screen recordings or to those watching my screen.] Any help is appreciated, I'm at a loss for what to do. Thanks in advance!
  22. Official announcement: https://techcommunity.microsoft.com/t5/windows-it-pro-blog/sha-1-windows-content-to-be-retired-august-3-2020/ba-p/1544373 Opinion: https://virtuallyfun.com/wordpress/2020/08/04/microsoft-to-delete-legacy-updates-in-the-great-sha-1-purge What a sad day!
  23. This is so awesome!! I wish someone could create generic Bluetooth Low Energy/Bluetooth 4.0 drivers too for Windows 7 (and Vista).
  24. Oh gosh! I hope someone creates an unofficial SP3 for Windows XP x64!
  1. Load more activity
×
×
  • Create New...