-
Notifications
You must be signed in to change notification settings - Fork 483
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on Windows 11 while using malfind #1519
Comments
Thanks for reporting your issue! It really helps. I'm no expert on windows but it seems like it might be related to this change that's in progress. Could you try the changes listed on this pull request and see if that works for you? |
Any luck? |
Not the original reporter, but I found this while searching for the same problem. I manually rolled in the fix from here: 4e2227e Then did a
Results from before the change and after the change should be attached, Literally no change on a diff, so I'm not sure if I actually added the patch correctly. |
Added some debug code, here's the results of
No CommitCharge there. self.u1 doesn't exist, neither does self.Core. However, I noticed there was a CommitCharge directly under self.
I have absolutely no idea if this is the "right" CommitCharge, but adding it after an if statement does start returning results and doesn't crash before the end.
|
Ok, so this is now crashing on line 269, which is part of the following:
Looks like the Core test was in the wrong place in the code. @eve-mem do you have a memory image where you can recreate this or at least test what happens if the |
I've spent all morning installing various different versions of windows I can get my hands on but I've not yet been able to recreate it so I can debug properly. These are the versions I've managed to get samples for, but they all work correctly unfortunately.
@BeanBagKing is there any chance you could share a broken sample? Even an iso I can use to build my own VM would work. |
Huzzah - I managed to make a VM with 15.26100 and can reproduce the issue. |
Hello Testing on this sample:
I was able to recreate the issue.
Then by making similar changes to @BeanBagKing I was able to get results.
I'd love a view from @atcuno to see if these changes are the right way to do things. I've updated the PR #1407 with these changes e9d1831 Hope this helps! |
Describe the bug
I am trying to analyze a .mem memory dump file on latest Windows 11, and I noticed windows.malfind not working
Context
Volatility Version: Volatility 3 Framework 2.8.0
Operating System: Windows 11 Pro
Python Version: 3.13.1
Suspected Operating System: Windows 11 Pro (same system)
Command: vol -f memdump.mem windows.malfind
To Reproduce
Steps to reproduce the behavior:
Expected behavior
To at least not crash
Example output
Text is preferred to screenshots for searching and to talk about specific parts of the output.
Additional information
I noticed that a lot of volatility3 windows 11 functionalities are not correctly working, like pslist not working in stable, only in dev.
The text was updated successfully, but these errors were encountered: