TheHam

much appreciated, I guess I didn't scroll down in that forum post. thanks for the clarification

my MalwareBytes finally updated from Version 4.6.7, and I looked at the Version History website, which lists Version 4.6.9 as the latest update when my MalwareBytes restarted for the update, the version was 4.6.10, but this isn't listed on the Version History page from what I'm seeing? is 4.6.10 the true 'latest' update for v4? I have the Free edition but afaik that does not matter in this case. I can't find any information about 4.6.10 other than an announcement that it released as a Beta version on March 1st, but a post on Windows ElevenForums says it was also released on March 7th? I'm just a little confused as to when 4.6.10 was released, due to the Version History page on the MalwareBytes website only listing up to 4.6.9

I did a scan with MalwareBytes and usually I don't look at Task Manager during a scan but I wanted to check something else and saw this process "ig-32" briefly show up and disappear I decided to go into the MalwareBytes folder and I did see an exe file called "ig" which is all digitally signed and from MalwareBytes and everything; I kind of got the idea of what 'ig' is but why did it say "ig-32" in Task Manager, when the file is just called ig, and has no other numbers. there's no more ig files in the folder, so that's the only one I did another MalwareBytes scan immediately after the current one ended and watched the same area in Task Manager, but it didn't appear again. it didn't appear after restarting the app and doing a scan either again, I understand that ig is part of MalwareBytes but what's with the "ig-32", is that a random number or does it refer tk 32-bit. also why did it appear once during my first scan, but never popped up again, even after restarting MalwareBytes? does it only appear on your first scan of the Windows session? just confused about all this; the number and why it only showed up once for a brief second. this "ig-32" process was the same thing as the "ig" exe in the MalwareBytes folder right?

hi, I opened MalwareBytes Free with Admin perms for the first time in a few days which has been running on Version 4.6.5 for a while and the Version History on the website displays that as the latest version I clicked Check for Update and it said "Downloading" and then "Installing"; however, it did not prompt for a restart and even after restarting MB, it was still on Version 4.6.5 so I assumed it was a sort of minor bug fix I kept Checking for Updates in case, and eventually after running a scan and clicking it some more, it said "Downloading.." then "Installing.." again, and actually prompted for a restart after restarting MalwareBytes, it now states that I am on Version 4.6.6; how recent is this update? I can't seem to find any notes, news, announcements, or anything about 4.6.6 for Free version

hello, disregard this. I don't think I need help with it anymore; Discord triggering these PowerShell events when logging out > logging in > restarting was confusing me greatly, especially since my friend wasn't seeing it happen on his end unless signing in with my account however, when he got Discord Nitro, he retested it and these PowerShell events were logged with the command line from the other user's post, that was getting flagged by MalwareBytes RTP I do have Discord Nitro, so this would appear to be causing it at least on my end. although it doesn't happen when simply opening and closing the app if the other user's issue about RTP flagging Discord when logging in with this 'powershell.exe -NoLogo TextInput' command line isn't resolved, perhaps they have Discord Nitro, and this could be causing it on their end as well

this is a strange issue because I have a similar problem, yet slightly these events are logged in Windows PowerShell if I logout > log back in > close Discord > and reopen Discord. if I simply open and close Discord at will, these events won't trigger but if I logout at any point then it seems like PowerShell will trigger upon my next startup of the app wondering if you can see that happen on your device too? I know you fixed your issue but wondering if this occurs to you as well. the thing is that this is specific to my account, but it's universal on any device I've tried to sign into, not just my PC tried deleting the cache folders, uninstalling and reinstalling on all devices, removing account connections. nothing changes the behaviour. noticed your case was a little similar, albeit a bit different as mine doesn't trigger on every instance of Discord