Jump to content

LiquidTension

Honorary Members
  • Posts

    4,182
  • Joined

  • Last visited

Everything posted by LiquidTension

  1. For users able to reproduce this, could you try setting a couple of QT (the framework used to build the Malwarebytes UI) environment variables and check if the issue still occurs or not? To set the environment variables, ensure the Malwarebytes UI is closed and run the following batch file as administrator: https://malwarebytes.box.com/s/hbxc3vcb8spn2dv6qvnrrtumvrb8iv36 "SUCCESS: Specified value was saved." should be outputted twice. After running the batch file, check if the Malwarebytes UI will open normally. If it doesn't, reboot and check again.
  2. Hi @MorpheusUK, No updates on the issue at this time. We're attempting to work with Kaspersky on it. Ultimately, as the issue was introduced with Kaspersky's "patch e" and no new changes were made to Ransomware Protection in Malwarebytes, the fix for this issue may only be possible with a change from Kaspersky.
  3. Hi all, No logs are necessary for this issue. We're already working on a fix and hope to make it available in a future update.
  4. Hi @ima_blocker, Could you carry out the following instructions so we can take a closer look at the issue: https://support.malwarebytes.com/docs/DOC-2396 Is the C:\ProgramData\Malwarebytes\mbamservice\D3.tmp.exe file currently in BitDefender's quarantine? Would it be possible to provide us a sample of this file so we can investigate further?
  5. Hi @Samoreen, There's something on your system that is preventing Malwarebytes from unloading the temporary user hives that it uses for scanning. We would need to troubleshoot the issue further to determine the source. With that said, I do understand your concern. We strive to make the product as robust and reliable as possible, but unfortunately, issues do arises. If you would like to revisit using Malwarebytes and encounter the issue again, just let us know. 11/05/19 " 00:43:34.469" 47183359 13d8 17b8 ERROR FileSystemUtils mb::common::io::FileSystemUtils::Delete "filesystemutils.cpp" 184 "File access error: sharing violation: C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-18-11042019113723095-ntuser.dat" 11/05/19 " 00:43:34.469" 47183359 13d8 17b8 ERROR FileSystemUtils mb::common::io::FileSystemUtils::Delete "filesystemutils.cpp" 184 "File access error: sharing violation: C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-18-11042019113723095-ntuser.dat.LOG1" 11/05/19 " 00:43:34.469" 47183359 13d8 17b8 ERROR FileSystemUtils mb::common::io::FileSystemUtils::Delete "filesystemutils.cpp" 184 "File access error: sharing violation: C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-18-11042019113723095-ntuser.dat.LOG2" 11/05/19 " 00:43:34.469" 47183359 13d8 17b8 ERROR FileSystemUtils mb::common::io::FileSystemUtils::Delete "filesystemutils.cpp" 184 "File access error: sharing violation: C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-18-11042019113724298-ntuser.dat" 11/05/19 " 00:43:34.469" 47183359 13d8 17b8 ERROR FileSystemUtils mb::common::io::FileSystemUtils::Delete "filesystemutils.cpp" 184 "File access error: sharing violation: C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-18-11042019113724298-ntuser.dat.LOG1" 11/05/19 " 00:43:34.469" 47183359 13d8 17b8 ERROR FileSystemUtils mb::common::io::FileSystemUtils::Delete "filesystemutils.cpp" 184 "File access error: sharing violation: C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-18-11042019113724298-ntuser.dat.LOG2" 11/05/19 " 00:43:34.469" 47183359 13d8 17b8 ERROR FileSystemUtils mb::common::io::FileSystemUtils::Delete "filesystemutils.cpp" 184 "File access error: sharing violation: C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-19-11042019113723211-ntuser.dat" 11/05/19 " 00:43:34.469" 47183359 13d8 17b8 ERROR FileSystemUtils mb::common::io::FileSystemUtils::Delete "filesystemutils.cpp" 184 "File access error: sharing violation: C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-19-11042019113723211-ntuser.dat.LOG1" 11/05/19 " 00:43:34.469" 47183359 13d8 17b8 ERROR FileSystemUtils mb::common::io::FileSystemUtils::Delete "filesystemutils.cpp" 184 "File access error: sharing violation: C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-19-11042019113723211-ntuser.dat.LOG2" 11/05/19 " 00:43:34.469" 47183359 13d8 17b8 ERROR FileSystemUtils mb::common::io::FileSystemUtils::Delete "filesystemutils.cpp" 184 "File access error: sharing violation: C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-20-11042019113723264-ntuser.dat" 11/05/19 " 00:43:34.469" 47183359 13d8 17b8 ERROR FileSystemUtils mb::common::io::FileSystemUtils::Delete "filesystemutils.cpp" 184 "File access error: sharing violation: C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-20-11042019113723264-ntuser.dat.LOG1" 11/05/19 " 00:43:34.469" 47183359 13d8 17b8 ERROR FileSystemUtils mb::common::io::FileSystemUtils::Delete "filesystemutils.cpp" 184 "File access error: sharing violation: C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-20-11042019113723264-ntuser.dat.LOG2"
  6. Hello, Please carry out the steps below to provide additional information on the issue. DxDiag Press the Windows Key + R on your keyboard at the same time. Type dxdiag and click OK. Wait for the window the open. It may take ~30 seconds. Once opened, click Save all information. Save the file to your Desktop and attach it in your next reply. Export System Information Press the Windows Key + R on your keyboard at the same time. Type msinfo32 and click OK. A new window will open. Click File followed by Save. Give the file a name, select your Desktop as the location and click Save. Right-click the .nfo file on your Desktop and click Send to followed by Compressed (zipped) folder. Please attach the Zip file in your next reply.
  7. Hi @siliconman01, Thanks for the report. Does this consistently occur for you? Could you open Internet Explorer, browse to www.malwarebytes.com, close Internet Explorer and then check if you still encounter this issue? If the above point has no impact, can you try launching the Support Tool whilst disconnected from the Internet. Do you still see the issue in this scenario? I've also sent you a PM with an additional steps to try.
  8. For the purpose of other readers, the cause of this issue was running the Malwarebytes installer from a network share. The installer must be run locally on the machine that Malwarebytes is being installed on.
  9. Thanks everyone. We'll continuing to work on this issue and hope to have a permanent fix available soon.
  10. Thanks for the file. As part of the scanning process, Malwarebytes temporarily mounts user registry hives . The 'LOWRISKFILETYPES' value was present in one of the temp user hives - hence the detection. The issue with this still being detected after the value was deleted from your actual user hive is due to a problem with unmounting the temp user hives. Something on the system is keeping an open handle to the temp hives, which is preventing them from being unmounted. We've seen this issue in the past and made changes to address some of the known causes. Can you reboot the computer (ensure the Restart option is used; not Shut down), open Regedit afterwards and take a screenshot of the HKU hive expanded?
  11. Thanks @Phxflyer. As Porthos mentioned, we have a defect for this issue and hope to have it addressed in a future update. For others reading this topic, the issue does not impact when the scheduled scan actually takes. It only impacts what is displayed on the Scanner card.
  12. Thanks for the file, @sendhelppls. The issue is being caused by a combination of 电脑管家系统防护/电脑管家12.13. Could you uninstall, reboot the machine and try the Malwarebytes installation again.
  13. Hi @Darthraider, Please start by carrying out the instructions in the above post and responding back with the generated mbst-grab-results.zip. Depending on the nature of the issue, exclusions may not viable. We'll need to troubleshoot the issue further to determine what corrective action is required. For reference, "Exclusions" has been renamed to "Allow List" in Malwarebytes version 4. It can be found by opening Malwarebytes, clicking the Detection History card and selecting the Allow List tab.
  14. Thanks for the report, @Gagome. We're looking into how best to convey this information to the user when the license is automatically reverted.
  15. It can be done locally or remote - whichever is preferable. The steps will produce a log containing information on the machine's display setup.
  16. Hello, We have a defect filed for this issue and hope to have a fix available in a future update.
  17. Hi @Samoreen, Thanks for the report. Could you carry out the instructions in post #2 and reply back with the generated mbst-grab-results.zip file.
  18. Thanks for the information. We haven't been able to reproduce this issue yet. What are some of the full file paths for files you're attempting to add to Play Mode? Unfortunately, there's no dump file for mbam.exe in the upload. Could you try the following please: Open Malwarebytes and go to Settings -> Security. Under Windows Startup, click Advanced and disable the Self-Protection module. Download the following Procdump.zip file: Procdump.zip Right click on Procdump.zip and click properties. Uncheck Unblock and click OK. Extract the Procdump.zip file. Open the folder where the files were extracted. Right click 1 - mbam_crash.bat and select Run as administrator. Reproduce the UI crash. Once the crash happens, the black window should disappear and a new DMP file should be found in the folder. Right-click the DMP file and click Send to -> Compressed (Zipped) folder. Reply with the dump file. ----- Also, please carry out the steps below: Please download FRST64: https://support.malwarebytes.com/docs/DOC-1318 Please download the attached Fixlist.txt file from this post. Ensure the file is saved in the same location as FRST64.exe. Right-click FRST64.exe and select Run as administrator to run the program. Click the Fix button (not the Scan button). A log named Fixlog.txt will be saved in the same location as the other files. Please attach the log in your next reply. Fixlist.txt
  19. Hi @Denis, Thanks for reporting these issues. To assist with resolving the first issue, could you carry out the following instructions please: Press the Windows Key + R on your keyboard at the same time. Type dxdiag and click OK. Wait for the window the open. It may take ~30 seconds. Once opened, click Save all information. Save the file to your Desktop and attach it in your next reply.
  20. Thanks for the information. Unfortunately, there's not enough information in the dump to determine the cause of the issue. We'll need to determine if this is a consistent issue for you or not. Please enable event log data (Settings -> General -> Event log data), run a scan in the same manner as before and let us know if you encounter the issue again or not.
  21. Hi @Oops, When you had the issue with Malwarebytes version 4, were you accessing the machine remotely (e.g. with Remote Desktop Protocol)?
  22. Hello, Please carry out the "technical issue" instructions in the post above and provide the generated mbst-grab-results.zip file.
  23. Hi all, Could you provide us with the information below please to help us resolving this issue. Press the Windows Key + R on your keyboard at the same time. Type dxdiag and click OK. Wait for the window the open. It may take ~30 seconds. Once opened, click Save all information. Save the file to your Desktop and attach it in your next reply. Thank you!
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.