mo832

Do all of these newer updates (1.7, 1.8, 1.9 etc.) include the "newer wget" version to eliminate the problem with certain old hardware (httpdl.exe fatal error)? Or is this something you must customize for those of us users who need the special version?

what is the difference between version 1.7 and 1.8?

@heinoganda I sent you a pm. I am having a relapse of the same issue from 2017 regarding the HTTPDL.exe error. We had a discussion on pm back then which it was fixed. There is also some comment about it in this forum on page 18. Please see what you can do.

@heinoganda Thank you for the info. I have not tried the RAVE function this time, but I did perform this in a previous event. If problem continues I will try it. Update: since running MSE updater again on Saturday 2/3/2018 and loading fresh definitions, I do not seem to be getting the error box anymore. I am still monitoring to see if problem reappears. I feel there may have been a bug in the last day's definitions, or else my installation for the defs was corrupted somehow. QUESTION: was your post for the German version software above intended for me and my issue, or for the general user audience?

after latest definitions update (2/1/18) using mse updater, I get windows error boxes from time to time that says "antimalware service executable has encountered a problem and needs to close". Then the Green icon turns red and a popup box says it has stopped and gives you a button to restart the service. When you click this button, the icon turns green again. This will continue until I run a new program, then the same sequence occurs. I tried to reboot and did not help anything. I never got this error before today. This seems to be a typical thing with MS on the first day of a new month, year, etc. Or, maybe just a coincidence. Any help or suggestions?

no posready on this machine and yes, xp sp3 and all critical patches up until they cut off support. I did use the avg remover, so normally there should not be remnants but there could be. I did a search on my system for httpdl.exe and all it could find was windows prefetch. Will attempt to run malware bytes and adwcleaner when have time. But do you have any other suggestions? Clearly the system does not like httpdl.exe. Also, this system still has IE 8, and although I never use it (always firefox), the IE8 is still set as default browser. Could this be causing problems? Again, the update worked when download mpam-fe and run it manually, but not with mse updater 1.5 auto.

Can I give you more info such that you might be able to help me pinpoint the source of the error? I support the idea that there may be a flawed installation on this XP machine, since this machine has never had MSE before, and previously it used AVG for many years. I had to uninstall AVG due to sluggish performance and a recent error message. But now, I am sure there could be a previously unknown flaw in my installation of XP, or the AVG removal process could have corrupted something. To answer your question, I am running MSE updater 1.5 simply by double clicking the icon for the program, and select (1) for update mse defs. Also tried "RAVE" for reset antivirus engine, then ran (1) again. The HTTPDL.exe error persists. It appears that it has a problem with starting or performing the download remotely...

Also, it looks like they updated the MpSigStub file again. The new one is dated 5/27/2017 . I did not try it, but I am sure it will fail like the previous update.

I just installed mse for the first time ever on another win XP machine. It installed fine, and automatically updated itself after the first install, before the first scan. I just tried to update the defs for the first time since the day I first installed it, using MSE updater v1.5. It gave me an error message during the first step (download the update defs). It said HTTPDL.exe encountered a problem with a dialog box. MSE updater came back and said no update available. I then went ahead and downloaded the update manually from the ms web link and did the update the old (long) way, by unpacking the files and running the old MpSigStub from my archive. It worked, but I wonder what is the deal with the HTTPDL.exe, and how can I fix it??

I do not have POSReady. Is there another way to patch my system? Or is there a way to get the update manually?

What about XP and Eternalblue exploit?

Question: does this comment directly address the worldwide ransomware attack that is happening today in the UK hospitals? They say MS has patched the vulnerability since March, but only in "supported versions". Otherwise, how can a current XP user protect the PC from this current threat?

yes, I have reinstalled MSE before. It has been a while since the last reinstall. I think when they broke the MSE with an "update" which basically just told it to shut down, I reinstalled 4.4.304.0. I have to go back in this thread to remember what I did, but I recall there had to be major tweaks to get 4.4 to install with old version and new install file or something like that. But MSE was working fine until last month when you made updater v1.5. Then it worked again fine until now. I needed the older MpSigStub to use mpam-fe, and I have used either updater 1.5 or mpam-fe unpacked manually since that time. Also like DrWho, sometimes the update happens with no action from me whatsoever, and I do not have POSready, and I am not signed up for any more XP updates with out of support version.

I do not have POSready on my machine. I only update mse defs manually every few days.

I performed those steps and it appeared to execute but mpsigstub.exe did not run as long as it usually does and then finished with no special message. I checked the MSE and it still showed "updated 7 days ago". Only upon shut down and a reboot, and then a delay of about 1 minute after restart the icon turned green and the MSE showed up to date. This happened once or twice in the last several weeks, where a reboot was required to make the update take hold.

Yes, I am having this trouble beginning today. First says update file corrupted, then on second try, says no update available. Is the update broken again? Mse updater 1.5 no longer works??

If you go about 2 pages back, I posted some weeks ago about this happening to me. I did absolutely nothing, and MSE updated all by itself, long after the updates had stopped and I was doing them manually every few days. This board was quiet for many days after that post.

I don't understand. The mse_def_upd 1.5 that I have does not show any taskman program, unless it is inside. Right now, there is nothing in my running processes related to updater. How does this relate to POSready?

I do not have POSready enabled to the best of my knowledge.

I did the reset the av and then the update using mse updater 1.5. Still it gave me the same message (no update available). Next I reboot and upon restart the mse went red and said (not turned on) and went green, but still version 603 from 2 days ago. Then I opened mse updater again and chose option 1 to update the av defs.... now it ran and reported updated to 797. I am happy it finally worked, but am concerned that the proven methods have not worked smoothly like they have for many months before +

I tried this method next. It did remove 1 or 2 files from the folder and left 3 files there. After about 15 mins, the files were still there and the MSE was not updated ("created 2 days ago"). Then I ran mse_updater 1.5, it ran and finished with the message "there is no update available". Still my mse shows 1.239.603.0

I have just downloaded the new mpam-fe.exe, unpacked it, and ran the "old" version of mpsigstub that I was sent to me. This time the mpsigstub started to run, and then finished after only about 30-45 seconds (it usually takes about 2 minutes). It did NOT update my defs files. I still have 1.239.603.0 . What is the problem now??

When you say "apparently gone under", do you mean it still works, or it stopped working?

Yes, I did try the top one. Thank you for all your help and advice. What I found is that at least for me, the top link does download a file called mpam-fe.exe. However, it is only about 2mb in size. I don't know if I again did something wrong, but this appears to be not the same file I was expecting. Also, given the link from Bersaglio, I think I have what I need to recover the old mpsigstub. I am interested in your further comments regarding the wayback machine method.

@Bersaglio, I did get your link in the pm. Thank you. This will help until the next time MS plays a new trick with MSE.