Jump to content

giomach

Members
  • Content Count

    24
  • Joined

  • Last visited

Community Reputation

0 Neutral

About giomach

  • Rank
    New Member

Recent Profile Visitors

492 profile views
  1. My user had worked around the problem by putting the program on his allow list. He has now removed it from the allow list, and reports that all is well. Many thanks for your quick response.
  2. Thank you. All clear today. I'm puzzled by your advice to turn off "Use expert system algorithms to identify malicious files". I have never turned this setting on. All four of my scan settings are/were exactly as shown in your screenshot. Many thanks again.
  3. Hello, I attach a MWB log sent to me by a user of a program developed by me, "Tobar na Gaedhilge" (the program installer can be downloaded from http://www.smo.uhi.ac.uk/~oduibhin/tobar/index.htm ). I gather the user has only recently installed MWB. I have had MWB myself for years and it has never objected to this program. Apart from two mentions in the log of "Advanced System Care", about which I have never heard, all the other items objected to are generated by running the installer for my program. The installer was created using Inno Setup. It concerns me that MWB could hav
  4. I've been getting the vs_installershell.exe report, described above, in my overnight scan since August 23rd. I updated malwarebytes yesterday but it's still reporting this. Log details appended. Thanks for your comments. -Log Details- Scan Date: 25/08/2020 Scan Time: 03:40 Log File: 45488232-e67c-11ea-99d1-9829a63e4f93.json -Software Information- Version: 4.2.0.82 Components Version: 1.0.1025 Update Package Version: 1.0.29007 Licence: Premium -System Information- OS: Windows 10 (Build 18362.1016) CPU: x64 File System: NTFS User: System -Scan
  5. Thank you, that seems to have fixed it.
  6. The attached program, combine.exe, is one which I have written from scratch (for text processing) over the years and compiled on my own PCs. As of today, when I try to run it, it is automatically quarantined. Combine.zip
  7. I'm satisfied that my PC is now clean. Thank you for your help, nasdaq. I leave it to the MWB team to satisfy themselves that MWB is reporting correctly in the case of Nero-9.4.12.3_free-notoolbar.exe as downloaded from softfamous dot com (among other download sites). If it is true that this download contains bundled software (such as Seznam and/or App Explorer), and if such software is malware, then MWB is wrong in not reporting it. If either of those conditions is untrue, then MWB is behaving correctly.
  8. Thanks again, nasdaq. Fixlog.txt attached. Re Nero, I soon uninstalled Nero 9 Free, because the functionality of that free version was inadequate, and I have today deleted the empty directories left behind in Program Files. I purchased and installed Nero Burning ROM 20.0.2014, which may be the reason for Nero entries in my logs now. Fixlog.txt
  9. Thank you, nasdaq. App Explorer removed and fixlog.txt attached. Is the problem solved? I don't know. I have run a custom threat scan on the downloaded installer for Nero 9 Free, which I suspect installed Seznam (and App Explorer) when I ran it before. MWB found nothing wrong with the installer, just like before - and that was the problem. I could go on to install Nero 9 Free, and see whether Seznam and App Explorer reappear, but that is a risk I am not keen to take. Is there any reason to suppose that they might not reappear, as they did before? (It is something which could be
  10. Hi, I noticed two suspicious processes in Win 10 Task Manager today: szndesktop.exe and listicka-x64.exe. I discovered your webpage on these at https://forums.malwarebytes.com/topic/241466-removal-instructions-for-seznam/ This page says that malwarebytes will detect these, and should have prevented their installation. In fact it had not prevented their installation, and a custom scan of szndesktop.exe did not report any problems with it. I removed them (and other stuff) by uninstalling Seznam Software from the Win 10 Programs and Features control panel. I am fairly s
  11. Hi, I noticed two suspicious processes in Task Manager today: szndesktop.exe and listicka-x64.exe. I discovered your webpage on these at https://forums.malwarebytes.com/topic/241466-removal-instructions-for-seznam/ This page says that malwarebytes will detect these, and should have prevented their installation. In fact it had not prevented their installation, and a specific scan of szndesktop.exe did not report any problems with it. I removed them (and other stuff) by uninstalling Seznam Software from the Win 10 Programs and Features control panel. I am fairly sure they were
  12. Thanks again. My intermittent problem with getting stuck on updates is not happening at present. But it looks as if my hard disk is OK. WinDFT couldn't see my disk, and WD support advised using DLGDIAG instead ( https://support.wdc.com/knowledgebase/answer.aspx?ID=940 ). This scanned my disk and gave it a clean bill of health. (Just for general info, to minimize the risk of interfering with my internal drive, I cloned it to an external drive, and booted from that for the purposes of testing the internal one.) The problem could have something to do with my internet connection,
  13. Thank you. I did "chkdsk c:" which reported no problem. Then I did "chkdsk c: /r" on restarting Windows, it took 4–5 hours, and the results disappeared off-screen before I could read them, so I don't know what it fixed, if anything. Was this what you had in mind by "hard disk diagnostic", or is there a better one? After that, a new scan still got stuck on checking for updates, until I closed mbam.exe and reloaded it. Then a new scan succeeded in getting the updates. We'll see if the problem recurs. (While it wouldn't solve any problems, I think it would be good if MW
  14. Hi, my problem with scan getting stuck on "checking for updates" is back. A scan is scheduled to run every 24 hours. The two attached screen shots, made at the same time, show that a scan has now been running for 43 hours, and has not got past "checking for updates". (BTW, to say "Last scan: 1 day ago" implies to me that the scan completed, whereas it seems to be really referring to the scan which is stuck. It would be more useful to know when the last completed scan was made.) Zipped logs attached. Thanks for your attention. mbst-grab-results.zip
  15. Thanks dcollins. Things are working again today — this problem of sticking on checking for updates comes and goes. When it recurs, I'll apply your suggestions.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.