-
Notifications
You must be signed in to change notification settings - Fork 102
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
WinPmem produces empty RAW Dump #55
Comments
Can you please try the binary built in #53 I found it works a bit better than the release |
It's extracting under |
@wallrik Hey, a damn good observation, I didn't notice until you mentioned it. Odd. Hm. The print verbosity of the usermode app could really be better and ought to be worked over. |
Any fixes found on this? I am facing the same issue. |
I used the built mentioned by @scudette and that worked :) |
Yes, and for everybody else reading, I think we are planning to release a new version that addresses some issues of the past. For now the built mentioned or compiling self from current source addresses most issues. On an Azure machine or a high tech hardware server + very modern Windows server, please stick to physical memory method. It might be a level 5 paging system. The upcoming version will correctly recognize this. |
Can you also test the go user space app. This is likely to be the most supported going forward |
@vivianezw do let me know if I can contribute to this project on any issue, I would love to see this open source project expand. Although I don't have much experience, I would like to contribute in any way possible. |
Hello guys,
when using the 64-bit Executable from the releases on a device it loads and unloads the driver. Then straight away creates a RAW Dump with the Size of 0 Bytes and exits. The cmd.exe is running elevated. Is there a good reason for this or is this a bug?
This is the STDOUT:
The text was updated successfully, but these errors were encountered: