Malwarebytes

[Wererommel]

Has anyone else had trouble with Mawarebytes? It keeps blocking Vortex as an "exploit" and ignores the exceptions on the exclusion list. No one at the company seems to know anything about it.

 

https://forums.malwarebytes.com/topic/277068-doesnt-recognize-execeptions/

 

[Guest deleted34304850]

i run malwarebytes and have done for years - never seen that before. not even once.

[Wererommel]

The only thing I notice is that the boot program

 

C:\User\[name]\AppData\Local\Vortex\pending\temp-vortex-setup-1.4.15.exe

 

is marked Administrator for some reason. Is that normal?

[HadToRegister]

The only thing I notice is that the boot program

 

C:\User\[name]\AppData\Local\Vortex\pending\temp-vortex-setup-1.4.15.exe

 

is marked Administrator for some reason. Is that normal?

 

 

Yes, you're supposed to run the Install program as an Admin

[Wererommel]

But even though it's marked Administrator, it still gets blocked. Maybe what is actually being treated as an exploit is

 

SE stack dump checker.bat

 

which is in the Skyrim Special Edition. Kind of puzzling. It's not there now. Apparently, this is a temporary file that is deleted shortly after it is created.

 

[Later] No that's not it. I don't know why it wasn't in the Skyrim folder, but I found a BU copy and ran it. It produced a message that said

 

FINSTR: C:\Users\[name]\My Games\Skyrim Special Edition\Logs\Script\Papyrus.*.log

 

could not not be opened. I guess that's what I should look at next.

 

[Later] It could not be opened because it wasn't there. In fact, the whole Logs folder was missing. Thanks to my extensive BUs, I had an old copy. But it only contained one file

 

More Informative Console.log

 

Which is apparently not what

 

SE stack dump checker.bat

 

was looking for. No sign of

 

Script\Papyrus.*.log

 

so I'll have to find that, I suppose.

 

[Later] Getting kind of desperate here. I couldn't find the Papyrus logs anywhere, so I duplicated the logs from Fallout 4, but I got the same exploit notice as before. Must be barking up the wrong tree.

[HadToRegister]

I have no file called SE stack dump checker.bat

This is unique to your system

[Wererommel]

I guess I should get rid of it then. I still don't know what it does, other than look for Papyrus logs that aren't there.

 

Steam says my local data is OK.

[HadToRegister]

I guess I should get rid of it then. I still don't know what it does, other than look for Papyrus logs that aren't there.

 

Steam says my local data is OK.

 

 

Steam only will say your local STEAM data is OK

It has no clue what else you have in your game folder(s)

[Wererommel]

I had a look inside

 

SE stack dump checker.bat

 

and all it says is

 

@echo off
findstr /m /C:"Dumping stack" "C:\Users\%USERNAME%\Documents\My Games\Skyrim Special Edition\Logs\Script\papyrus.*.log"
if %errorlevel%==0 (>NUL powershell "(new-object -COM WScript.Shell).popup('You Had a STACK DUMP, the line in the cmd window tells you which log.')") else (>NUL powershell "(new-object -COM WScript.Shell).popup('all ok!')")

 

I don't know why it's there or where it came from, but I'm pretty sure it's not the problem.

 

[Later] Malwarebytes identified

 

SE stack dump checker.bat

 

and

 

temp-vortex-setup-1.4.15.exe

 

so I have to wonder if they have something in common. The only thing I see is that they both use PowerShell.

 

 

 

[Guest deleted34304850]

My Vortex runs from here: "C:\Program Files\Black Tree Gaming Ltd\Vortex\Vortex.exe"

My Malwarebytes runs from here ""C:\Program Files\Malwarebytes\Anti-Malware\mbam.exe"

 

My Vortex install program ran as admin from here: "C:\Users\BigBallsMcDuff\AppData\Local\Vortex\pending\vortex-setup-1.4.15.exe"

 

Now the Vortex setup program is run on my system, only when Vortex detects that an update is available, so I never run this manually, rather it is run indirectly by Vortex, and once it has updated, it's never run again, until the next time an update is available, when I assume the installer is overwritten by the new version.

 

I'm not sure running any process from appdata is a good thing to do, and I wonder if that is why your Malwarebytes is throwing up an exception?

 

I suggest you try to run Vortex from within program files and see what occurs.