Jump to content

heinoganda

Member
  • Posts

    848
  • Joined

  • Last visited

  • Days Won

    17
  • Donations

    0.00 USD 
  • Country

    Germany

Everything posted by heinoganda

  1. On the 2nd of May 2019 I sent you a PN where a suitable variant of the MSE Definition Updater Version 1.9 is offered, have a look at our conversation! By the way, at the moment you are the only user who needs this variant and this variant is made available after an update via PN. (Since I do not want to overflow my mailbox, very outdated conversations sometimes have to be deleted) This is not planned in the program, especially since the program is designed so that even after an update with an offline definition ("MSE_DEFINITION_DOWNLOAD") another attempt at a download is started to ensure that no more current definition is available. If there is no newer definition in the folder "MSE_DEFINITION_DOWNLOAD" to the one installed in MSE, then you get the appropriate screen output if there is no internet connection (in your 6th image). If an update has been carried out, you will see the screen output (in your 4th image), which after the version is displayed "Updated". First and foremost, the MSE Definitions Updater is designed for an existing Internet connection.
  2. @XP/Vista user If you have done RAUE, then there should be no problems updating the definition files with MSE Updater v1.9. If you are working with offline updates, you should first delete or rename the folder "MSE_DEFINITION_DOWNLOAD" if outdated definitions still exist. Above all, give the MSE Updater the time it needs to update (takes longer than at the time before the support end of MSE on Windows XP)!
  3. Because of .NET Framework 3.5 Assistant add-on for Firefox (KB963707) I have a suitable uninstaller where the update KB963707 is no longer available in WU / MU. Download: here
  4. Have you already tried the latest version of MSE Updater? https://msfn.org/board/topic/175514-microsoft-security-essentials-and-windows-xp/?do=findComment&comment=1163489
  5. In your case yes, any customizations will be made to the MSEDEFUPD.bat and MSEDEFUPD_INT.bat files. Actually, I do not use MSE at all, just to test in my VM to eliminate any errors in the Microsoft Security Essentials Definition Updater. If there are no further suspensions, it will stay with version 1.9.
  6. Microsoft Security Essentials Definition Updater update to version 1.9 Adjustment for support end of MSE
  7. Both updates for the kernel, KB446103 (ntfs.sys v5.1.2600.7581, ntkrnlmp.exe v5.1.2600.7581, ntkrnlpa.exe v5.1.2600.7581, ntkrpamp.exe v5.1.2600.7581, ntoskrnl v5.1.2600.7581), and KB4486463 (ntkrpamp.exe v5.1.2600.7649). The error 0x80072EE7 also occurs again on WU / MU in Internet Explorer (currently only temporary).
  8. Maybe in the key "FallbackOrder" it helps to delete the content "MicrosoftUpdateServer | MMPC" in the registry "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Antimalware\Signature Updates" (there is no permission to edit entries here!). For this I can provide you with a helper, unzip file (3 files in a folder) and run the file "no_UPD.bat" (with the file "UPD_Default.bat" the original entry can be restored). Download: here Hope that with you this problem is solved!
  9. Have in a test currently at WU / MU in IE8 only the error message 0x80072EE7! Update: Apparently it was just a temporary problem.
  10. @mo832 There are approvals to the current situation, since the last working engine (1.1.15800.1) of MSE under Windows XP would result in the queries during the download according to the current definition to an undesirable result or the comparison of the existing definition files in the folder MSE_DEFINITION_DOWNLOAD to the Installed Definition in MSE, otherwise they would be completely reinstalled during an update. Finally only adjustments so that the MSE Definition Updater does what the version 1.5 could do.
  11. Microsoft Security Essentials Definition Updater update to version 1.8 Adjustment for support end of MSE
  12. @GH0st Because of KB4494528 I have not been able to detect any problems (custom update, https://msfn.org/board/topic/171814-posready-2009-updates-ported-to-windows-xp-sp3-enu/?do=findComment&comment=1162245), can offer you my update rollup with which you after reinstalling WinXP Pro sp3 this installation and try if the error occurs here as well. Since I do not know what software for the printer is installed, I can not retrace that. If you are interested in a test send me a PM.
  13. It is up to you whether you create the suitable link manually for each download before. There are users who just want to keep the definition of MSE up-to-date and no complicated procedures. This is done by the MSE Updater, not only the complete definition is loaded, also different updates (delta updates). Here you should not delete any files, this file (offreg.3416.dll) will appear after scanning and will run as a service temporarily.
  14. @egrabrych The folder "MSE_DEFINITION_DOWNLOAD" is sometimes used to hold definition files offline (does not have to be used). I've made some adjustments in the meantime as the engine queries differ between the installed version (1.1.15800.1, last working in XP) and the current definition engine. Downloading from a delta definition requires the version value from the current engine, which requires customization. In a previous post I already pointed out the possibility that a definition update without MpSigStub.exe is possible (https://msfn.org/board/topic/175514-microsoft-security-essentials-and-windows-xp/?do=findComment&comment=1137429). The MpSigStub.exe file (where a copy is installed in "%windir%\system32", will be deleted after an update with the current MSE Updater v1.7) will check the existing definition, resulting in an error message or error propagation because of the engine version (1.1.15800.1, last working in XP) can not be refreshed. Only the definition files (.vdm) are updated. The definition updates still offered by AU/MU (if POSReady 2009 key is entered in registry) should not be installed anymore, unless a definition file is published again where the engine works under Windows XP again (which is unlikely to happen). Therefore, AU should be disabled and no definition updates should be installed when searching for updates (MU) in IE. The fact is that no newer features or security updates on the Engine for MSE are possible anymore.
  15. Between version 1.5 - 1.7 there is no difference in the parameters or functionality. You do not have to worry about it, especially since I create versions for experimental purposes in between. At the moment I hope with the MSE Updater Version 1.7 still a long time MSE on Windows XP x86 with definition updates can be supplied.
  16. RAUE In this case, pay attention to the uppercase and lowercase letters!
  17. Try it via download via webproxy. The censorship has meanwhile hit Germany as well. Unfortunately I can not write what I think, there is no free internet anymore, only censorship!
  18. Microsoft Security Essentials Definition Updater update to version 1.7 Adjustment for support end of MSE
  19. Will publish a customized MSE Updater, but this means that the mpengine.dll would remain at the state of version 1.1.15800.1. A test with the Eicar test virus has been positive with the most recent virus definition. In how far this will affect more recent virus definitions in the future, I can not foresee. The fact is that in future vulnerabilities or functional extensions in the file mpengine.dll no update is possible. There are still some tests needed in the next few hours and if they go well I will publish the updated MSE Updater.
  20. It was anticipated that the end of MSE definitions would come. Have myself made some tests, but unsuccessful. Thus, MSE has definitely become unusable without the possibility of updating the definition or engine.
  21. https://support.microsoft.com/en-us/help/4025687/microsoft-security-advisory-4025685-guidance-for-older-platforms KB958644 was replaced by KB2705219-v2 from October 2012. KB2347290 KB4012598 was replaced by KB4486465 from February 2019 KB4012583 KB4022747 KB4018271 IE8 was replaced by KB4493435 IE8 from April 2019 KB4018466 was replaced by KB4486465 from February 2019 KB3197835 KB4024323 KB4024402 was replaced by KB4047211 from November 2017 KB4025218 KB4019204 was replaced by KB4493927 from April 2019
  22. Another note: The updates listed in my update lists are sometimes not available via AU / WU / MU! The lists are cleaned up, where by updates which are no longer needed by more recent updates are not listed.
  23. It was to be expected that the MS will shut down the update system. So I've created my own update rollups (DEU and ENU) to circumvent this problem. Following a list of the updates that are included in my rollups.
  24. The patch Tuesday is again for MS a grip in the toilet! Many virus scanners have problems since the update under Windows 7, 8.1, 10. Hope that under Windows XP these problems do not occur. https://borncity.com/win/2019/04/11/april-2019-updates-freezes-windows-7-8-1-10-server/ https://www.bleepingcomputer.com/news/microsoft/microsofts-april-2019-updates-are-causing-windows-to-freeze/ @glnz Then it's time to unpack my old Commodore Amiga again!
×
×
  • Create New...