Jump to content

MWBAM_Customer

Members
  • Content Count

    31
  • Joined

  • Last visited

About MWBAM_Customer

  • Rank
    New Member

Recent Profile Visitors

572 profile views
  1. MWBAM_Customer

    Can't get Beta Component Package Update 1.0.39x

    Although my installation functions correctly and I've had no issues since, it is installed in the wrong location, so when the issue is fixed, I want to uninstall MWB from the default location and reinstall it where it was originally.
  2. MWBAM_Customer

    Can't get Beta Component Package Update 1.0.39x

    So should I stay with my current install as it is? I don't want to change the location if it will cause the Web Protection issue again, or prevent further component updates from installing.
  3. MWBAM_Customer

    Can't get Beta Component Package Update 1.0.39x

    I see that the release of MWB 3.51 has been updated to include CP 1.0.391. Does a clean install of the latest release have issues with installation location, or is that just when the CP is updated from previous versions? The issue isn't mentioned in the announcement.
  4. MWBAM_Customer

    Can't get Beta Component Package Update 1.0.39x

    That would be very welcome. Would a manual install then detect those, to account for custom install locations, or just an install through the support tool? One further suggestion, if I may, in the blue ribbon at the top of the MWB window, if there was an "i" icon, or similar, that linked to the about tab, it would be a handy shortcut.
  5. MWBAM_Customer

    Can't get Beta Component Package Update 1.0.39x

    You're welcome, happy to help. When a beta/release is made available which fixes the issue, will this be mentioned? I'd rather not uninstall and reinstall to change the location until the issue has been addressed, otherwise there'll be another uninstall and reinstall after those to change the location back again. Does my suggestion of a text file for the changed settings sound possible/of interest?
  6. MWBAM_Customer

    Can't get Beta Component Package Update 1.0.39x

    Well the issue, here at least, was repeatable. If I can help further, just ask. I appreciate it's a balancing act between ease of use and features. I played it safe and went with the clean install as I knew there was an issue somewhere. Actually the support tool was a bit hit and miss. I think it crashed a couple of times, didn't restart after boot a few times, so it got some use with repeated running. Perhaps if the post reboot response offered two options - to reinstall, or just download the latest version, that might be a workable compromise. Then the custom installers have the latest version downloaded and ready to run, and those that just want a default install have no further clicks. If I might make a suggestion, it would be helpful if MWB 3 created a text file of all the non-default settings. Sometimes it can be hard to remember back to what you changed when, but having a list of all the changes a user made would greatly assist with the post-install configuration. That way, the clean installation is maintained, and the user has a reference of what settings they changed, and can go straight to them, rather than having to check every setting and try to remember if they changed it and how. Typing this has reminded me that I haven't customised the scans, for example.
  7. MWBAM_Customer

    Can't get Beta Component Package Update 1.0.39x

    Thanks Devin. Do the logs provide all the information you need? Could a prompt be added before the reinstall procedure starts, stating that it will install to the default location? It would have saved me some time and hassle, and may well again, if I forget in the future. The advantage of the tool, is that it ensures users reinstall the latest version, rather than one lying around, or from the wrong site, which could happen with a manual install. Perhaps if the tool downloads it, and then lets the user run it themselves for a custom install?
  8. MWBAM_Customer

    Can't get Beta Component Package Update 1.0.39x

    Hi Devin, That was it, I ran the support tool to clean, rebooted. It prompted to reinstall, I toggled the beta setting, checked for updates and it worked. I'd repeated the procedure numerous times, so I believe it was the install location causing the issue. When I previously allowed the support tool to reinstall, I immediately ran the clean function when I saw that it hadn't respected my install location and didn't offer me a choice, so I didn't try the beta update at that time. So, an interim fix for the issue. I hope it will be properly fixed - as I said, it hasn't occurred with previous betas. I hope future testing covers a non-default install location before releases are made available as it's hardly an advanced level tweak. Will the support tool be modified to prompt for install location in the future? I'll PM you the new logs for your information. Many thanks for the help. Edit: Forgot to mention, when this is fixed, if you could let me know, so I can remove MWB and install it in my location of choice, I'd be most appreciative.
  9. MWBAM_Customer

    Can't get Beta Component Package Update 1.0.39x

    Hi Devin, Thank you for your swift reply. I've always used a custom folder. An annoyance of the support tool is that it doesn't ask where to install, so that that added an extra uninstall and reboot. I'll run the clean tool again and let it reinstall, if it asks.
  10. Hi, I'm having an odd problem with MWB 3.5.1. When I saw 1.0.390 was available, I activated beta updates (the release version was working fine). The new Component Package (CP) didn't automatically download. I left it several hours and selected "Install Application Updates". It downloaded and installed something, but the CP remained at 1.0.374. After a reboot, I checked again, it downloaded and installed something, without updating the CP. After each reboot, a manual update check finds and installs something. Also, periodically I received a toast notification of inactive protection, which would disappear shortly afterwards without my intervention. I have done a number of clean installs, but the same behaviour remains. I have noticed that the Protection that is toggling is Web Protection, and that it stays off for around 5-10 seconds. This protection issue only occurs when on the beta stream and applies to 1.0.390 and 1.0.391. I have used the betas before, but never experienced these issues. Any suggestions are welcome. As I say, reboots and clean installs are not fixing the issue, hence my post. Many thanks.
  11. MWBAM_Customer

    Testing new Beta opt in setting

    Hi, Received an update available notification whilst running as a standard user, the installer ran fine, without issue, or needing a reboot. My custom scans were retained, the only setting I needed to revert was the language, back to UK English. This does beg the question, should the user be logged in as an admin to upgrade, (after the previous issues experienced as a standard user)? Thanks for all the team's hard work.
  12. MWBAM_Customer

    Malwarebytes 3.2.0 Beta Premium Install Issues

    Hi Becky, That's quite alright, I'm happy to help, I prefer to find issues on my system, than for friends and family to have them. I read that you wanted feedback on the installer before I used it, so I knew an issue was a possibility. As it was so unusual, I thought the feedback might prove useful. Yes, I'd seen before that some of the settings transfer issues had been reported, e.g. language and scans. Having these transferred as well would reduce the hassle of upgrading Malwarebytes. Auto Updates and Early Self-protect being disabled would certainly be good to be fixed, as less technical users will just update the software and won't check every single setting in the software has been reinstated. I'm afraid I can't remember, but is being logged in as an admin a published requirement for installing? Does the software state that when the installer is run? If this is a requirement, what happens when the update is auto rolled out later, and the user is logged in as a standard user? I have used other software that blocks being run through a standard user's elevated prompt, so it is certainly technically possible to discern between the two cases. New version feedback The ability to check for application updates in the settings, even if they are being throttled is a nice, sensible edition. One suggestion I do have, is I always password protect all the Malwarebytes settings, apart from viewing logs, to increase security and users accidentally changing settings. As the About tab is located in the settings tabs, it means that when you want to check the version, component update etc, the password is required, which is a pain, and unnecessary. If the About tab was brought out of settings, or maybe if settings defaulted to opening on the About tab, this niggle would be removed. As the about tab contains no sensitive information, it doesn't need to be protected, and wasn't in the 2.x versions.
  13. MWBAM_Customer

    Malwarebytes 3.2.0 Beta Premium Install Issues

    Thanks Porthos, I wasn't aware of that, I thought elevated admin permissions from a standard user were sufficient. I can't remember how I've done it previously, but I'll make a mental note to log in as admin in future. As it's a requirement, I'm surprised the installer doesn't check for it when run and prompt the user accordingly.
  14. Hi Becky, I'm afraid my over-install did not run smoothly. I have attached setup log files and mb-check files run from standard and admin user accounts. The system is running Windows 10 Pro 64 bit 1703 15063.483 with Fast start-up disabled. The beta installer was run as a standard user, installing over 3.1.2.1733-1.0.160. The installer ran MB Clean and requested a reboot, which was done. The installer did not recommence, and no Malwarebytes programs were running. The installer left the following files behind in the user selected install folder Name Size Type Modified Attr 7z.dll 1.53 MB Application extension 20/01/2017 07:55 -a---- Actions.dll 3.83 MB Application extension 19/07/2017 22:39 -a---- MBAMCore.dll 4.40 MB Application extension Wednesday 16:42 -a---- The installer was ran again, and before the install folder was confirmed, the above files were deleted. Again, the installer ran MB Clean and requested a reboot, which was done. The installer did not recommence, and no Malwarebytes programs were running. The user selected install folder was empty this time. The installer was run for a third time. This time, the Malwarebytes files were installed. Malwarebytes indicated it was out of date (I can't remember the exact wording). A check for updates was successful. Malwarebytes then indicated Malware protection was turned off. Attempting to turn it on in the UI resulted in Malware protection status of starting and the UI freezing with MBAMService showing <1% CPU usage and MBAM showing a constant 2% (i7-4790K). MBAM.exe was shut down using the "Terminate tree" function of Process Hacker. Malwarebytes was then started from the Windows menu, initially Malware protection was shown as on, shortly after, it was shown as off. Reviewing the changes that were lost in the install ... The Language was reset to English from English UK Auto Updates were now off Enable Early Self-protect was now off Scheduled scans were wiped The Malware protection setting was left off and Malwarebytes was exited through the app and then started again from the Windows menu. The MBAMService service had not been started (Process Hacker options for start and stop were greyed out). Malwarebytes displayed a message saying it was unable to connect to the service, however the process, MBAMService was still running. The process MBAMService was terminated, which allowed Malwarebytes to restart itself. Malwarebytes issued a tray toast warning layers were off, however the UI showed they were all on. Shortly after, the UI indicated the Malware and Ransomware modules were off. The option to turn protection on through the tray toast was selected. The UI then showed Ransomware off, and the UI was responsive. Attempting to activate the Ransomware module through the UI showed the module as starting and the UI was responsive. The tray toast appeared afterwards indicating protection was off. The machine was then rebooted and logged in as an admin. Two instances of the Malwarebytes installer the appeared requesting admin access. The Malwarebytes install was checked for correct functioning, and the installs were aborted. The install seems okay now, with Malwarebytes operating normally. I hope this helps. Kind regards. mb-check-results Admin User.zip mb-check-results Standard User.zip MB Setup Logs.7z
  15. Hi TempLost, Thanks for the update, glad you've got your install settled for the most part. Your post saved me a lot of head scratching, so thank you. I've also linked this thread in my support request to FoolishIT and will update it when I hear back. Take it easy.
×

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.