Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by PostHEX

  1. Also by the looks of it you'd may need to connect a modern m.2 WNIC, but (almost) nothing that can't be found on the web.
  2. It looks more daunting than it really is though. If you can assemble a desktop PC, then this is similar. The only difficult things are patience, and remembering the order in which you disassembledm so that you can do it in reverse when reassembling. I do this with my new laptops all the time, because I hate that so many of them come with crappy Qualcomm, Broadcomm or Realtek ones (<3 Intel WNICs). Not to mention that some require DRAM upgrades anyway. Or the occasional battery replacement. But I recommend asking your IT professional friend. I'm sure he could, if he wants.
  3. Have you ran Windows's Troubleshooter? What did it tell you? Also re you sure that the WNIC can't be swapped? Searching your model lead me to this iFixit tutorial. If I'm wrong it would be very weird that being the case, as I know that the Yoga C920 that released in 2018 does allow for the exchanging of the WNIC. In any case find out your WNICs, and try to search & download the drivers on the WNIC's OEM's site instead. Chances are that their repository is more up to date than Lenovo's. If not, then again try to replace the WNIC (I believe yours is a Realtek, and Realtek's WNICs are universally sh*t; always prefer an Intel one if you care for stability and driver support longevity). If that's not possible, then just use a USB WNIC (there are plenty models that don't stick out too much... though just don't expect great performance... then again if your WNIC is still 802.11n and 2.4 Ghz only, then it might not be a significant difference).
  4. Doesn't Windows Defender do all of its stuff silently? And isn't your Android app completely silent as well (though your Android app obviously isn't as large and privileged)? I'm not being snarky, but genuinely asking for a points of reference. If a complete silent install is long ways away, then you could implement a semi-silent install instead. You could let users just push an accept or decline button for an upgrade, and that's it. I really don't see why we have to go through a wizard, as we're literally repeating steps that we've already gone through (language, install directory, etc) during initial installation, steps that haven't got any influence on the outcome of the upgrade.
  5. Thanks for your answers to both members of staff. I'm relieved to hear.
  6. I'm talking about application updates then. Why do you still need a wizard for that? People don't need a wizard to update Chrome from 56 to 57; just a restart of the application will do. Why do users at every application update need to reaffirm their GUI language, re-accept software license agreement, reaffirm in which directory to install, reaffirm start menu folder settings, reaffirm desktop shortcut settings? I get that it's done this way because it's always done this way, but it's stupid. Better would be a similar experience to the application updating of your Android app.
  7. I agree. Would be quite nice indeed. Especially for systems that are passively cooled, which haven't got a fan that starts to rev up, indicating users of 'something heavy in the background is in progress'. In addition to systray icon: some sort of notification while using full screen apps (such as video games) would be handy (of course the notification should be able to be disabled for users who wouldn't want).
  8. Running through a wizard for every software upgrade is not 2017. De-installing old versions and installing a new is not the way the servicing of software should work in 2017. With the current method of upgrading it befalls on people of my generation with parents and grandparents -- parents and grandparents who can't even finish a wizard without messing something up -- to handle the upgrades. I mean, haven't Malwarebytes staff got middle-aged and elderly relatives who use their company's product? Surely you must be getting feedback from them? Or are you all lucky that all of your employees' relatives have grown up with PCs and are PC literate? The way upgrades are done for your Malwarebytes app for Android would be extremely welcome to have for desktop Malwarebytes as well. Well at least similar in terms of how the end-user experiences it. I've requested a couple of times an overhaul of the method of upgrading, and I'll keep requesting until the upgrading of Malwarebytes receives a modern implementation. Overall I like your product -- that's why my family owns ~18 licenses combined -- but I'd like it so much more if it wasn't a pain in the butt to manage all the installs.
  9. Q: how to halt Malwarebytes for requesting to upgrade? I'm skipping a couple of versions until I upgrade to 3. Tip: Also, I want to suggest to convert Malwarebytes to a Windows Store app, so that version updates can be distributed through the Windows Store. Helps against future possible MitM, and more importantly: making the update experience less of a nuisance. It's really annoying to have to go through the language settings and what not after each major revision, because with the current update method there's no system in place that remembers the settings.
  10. In case staff is reading, just noticed that the feature is added (am not using Malwarebytes yet, still on MBAM, but just read the change log). Thank you very much. That's a good point. Any staff reading able to clarify?
  11. That's why I propose challenge/response authentication based on asymmetric cryptography based on U2F in conjunction with yubikey support. Yubikeys have a secure element, which safeguards the private key against theft. Which is to say that if a bad person wants to get access to your account, it has to physically steal your yubikey first.
  12. So I've got about 9 non-business MBAM licenses to manage. Currently I'm using notepad to keep an oversight which license is installed on which machine. If something changes, I have to remind myself that I have to look up the text file, and register the change. It's a hassle as you can imagine. In addition there's no way to deactivate a license remotely. Remote deactivation is useful in the case of device theft, or say a motherboard failure on someone's laptop, and you don't want to go through the trouble of opening up the device -> taking out system drive -> attaching system drive to another device -> boot up and deactivate license. The solution I'd like to suggest, is to set up a product account system (on say malwarebytes.com), so that users can create an account and bind/manage their licenses to/from. Managing in the sense of that each license shows if it is active or not, optionally on which machine said license is active via hardware-ID or of some sort, and having the power to disable a license remotely. Like similar to how Microsoft implemented such a licensing management system during the W10 anniversary update, allowing users to bind their W10 licenses to their accounts, and keep an overview. Also preferably the account access authentication to be U2F based, with Yubikey support, for solid user security.
  13. I missed that update prior to starting thread. Should frequent the forum more. Thank you very much for the link. Sounds like a very exciting route Malwarebytes is taking. I wonder what that means for perpetual licensees for MBAM. But I guess the license won't be moved over to the new product, but remain separate for MBAM.
  14. Edit: meant with the first reason, that install/reinstallation of two separate programs is annoying versus just one.
  15. Last year I raised the issue of the license details being uncomfortably constantly exposed. Iirc, the response was that the option to password protect the license details, so that one would need to enter the correct password before they can be viewed (unlike now where you can only configure Access Policy to required to enter password if license details are to be changed), was on the agenda, but that was the last I heard about it. Constantly exposed license details is a problem, because it aides theft and abuse. I recall that formerly part of the license details were by standard blocked out if you accessed the account page within MBAM. I assume Malwarebytes changed that to reduce the number of helpdesk calls by the people who had forgotten their license details. I understand that, but I'd appreciate it a lot if us users who know what we are doing, to have the option to add an Access Policy for the entire My Account section. Thank you.
  16. Whenever there's a MBAM version update (not referring to database update, to be clear), it's annoying that in this day and age you still have to manually update it through a wizard. For me manually updating is an annoyance, but for my parents it's an actual problem (which eventually falls back onto me, because I have to assist them). When a wizard pops up of a piece of software they're not familiar with, they don't know whether to assume it's some malicious program or not, let alone knowing what to do with it if they do were to trust it (yes, even wizards are not user friendly enough for a huge portion of the elderly; have seen it happen many times that they and other people of their generation just press whatever they can in wizards of any software, because they want to get it over with as quickly as possible of something they can't make sense of). So they pause until I, their sysadmin, is available to check. This costs them and me valuable time in more ways than one. Could the devs fully automate the update process for future MBAM iterations? Possibly by making it a Windows store app, so that MS' network can handle the updates? If updating via the Windows store isn't an option, than I'd genuinely appreciate it if the devs can figure out a way to make MBAM fully update itself, eliminating the need of any user interaction. The idealist in me says that any piece of maintenance/security/assistance (i.e. background) software should be installed once, configured once, and be forgotten about, all the while it does what it is supposed to, as well keep itself maintained. Thank you.
  17. Reasons: If to be deployed on multiple machines within say a household, costs more installation/reinstallation time. Just plain annoying to manage. Since they're both two separate programs, both have got a different start-up time (this is exacerbated if there are many other programs to be launched between MBAM and MBAE). It just looks cleaner/more professional having all your products in one place (like Surfright's HitmanPro.Alert is for example (P.S. hope mentioning a competitor is not a problem; if Malwarebytes has got a better product, this shouldn't matter, right?)). Thank you.
  18. Thanks for the link blackdovemobile. Interesting read.
  19. Very satisfied user here. Been using 2.1.8 for a while, and runs very stable in all regards. Only thorn in the eye is of course being unable to currently hide account details (stopping me from updating to any of the recent versions on the rest of my machines), but I'm very happy with all the new features added. Malwarebytes actually implemented all the features they said they were going to. Amazing that such companies still exist.
  20. I had upgraded to 2.1.8 succesfully, but my account details are still in the old format (ID + Key). Is it still recommendable to upgrade a number of licenses -- bought from unoffiicial vendors -- to the new format? Or just better leave them as is?
  21. Edit: meant by "except that the licenses will just have a different name?", if the licenses will just have different keys.
  22. For the sake of keeping the forum clean, I did not want to start a new thread, so... Should customers who in the past have bought directly from the Malwarebytes store be safe regardless of any future conflict with pirated generated and legitimate licenses? Given that one has securely stored and has got assured access to the reference number(s) and the bill(s) of purchase. There's no need for me to convert all of my and my relatives' licenses that I and they purchased 1.5 years ago through the Malwarebytes store, right? I assume that this is the case, but I just have to be absolutely certain, given that these licenses are for life, and as I'm basically responsible for my relatives' investment regarding these purchases as I convinced them to buy into MBAM. Second; would it be wise to convert some of my MBAM licenses that I've bought from an unofficial reseller? The licenses work perfectly at the moment, so I assume they're legit (am not using them actively, but just keeping them as back-up, so I can't constantly verify their status). But would I do good to convert regardless, since the reseller has got zero ties with Malwarebytes or Cleverbridge, and so there is zero guaranteed fallback when there is a license conflict? And this might be a silly question, but I have to ask anyway; if I convert, everything should function practically the same in using MBAM with those licenses discussed in the second point (e.g. that the lifetime status remains lifetime), except that the licenses will just have a different name? Is that correct? And lastly; how long is this license conversion offered by Malwarebytes on the table? I couldn't find any information on that. I assume it isn't forever as, to be honest, it would hurt sales given that it is fairly easy for illegal users to dupe the system into thinking they're sincere customers who've been fooled by scammers.
  23. Mine's too. I do it because I once wanted an easy layer of protection against unauthorized program changes/installs while I was AFK and forgot to lock my computer, or a user had gotten remote access to my system (it would only protect against scriptkiddies though -- but I digress). The issue I once had with MBAM while using a non-admin priviliged account, that I couldn't change the settings and the system didn't tell me why (normally you'd have to enter a password, but in this case it wasn't asked for). I had to specifically log onto my admin account to be able to make the necessary changes. So there you go.
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.