-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
PSTREE error #878
Comments
Could you run vol with the -vvv option before the plugin name and share the log output as text and not an image. It really helps work out what's going on. |
A quick note, vol3 doesn't need you to choose a profile. It'll find it automatically. |
C:\Users\W0457579\Documents\volatility-master\volatility-master> 0xfffffa8006d26890: 0 0 0 ------ 1970-01-01 00:00:00 UTC+0000 C:\Users\W0457579\Documents\volatility-master\volatility-master>python vol.py -f "Clone of Clone of Windows 7 x64-a88debbd.vmem" --profile=Win7SP0x64 pstree 0xfffffa8006d26890: 0 0 0 ------ 1970-01-01 00:00:00 UTC+0000 C:\Users\W0457579\Documents\volatility-master\volatility-master>python vol.py -f "Clone of Clone of Windows 7 x64-a88debbd.vmem" --profile=Win2008R2SP0x64 pstree 0xfffffa8006d26890: 0 0 0 ------ 1970-01-01 00:00:00 UTC+0000 C:\Users\W0457579\Documents\volatility-master\volatility-master>python vol.py -f "Clone of Clone of Windows 7 x64-a88debbd.vmem" --profile=Win2008R2SP1x64_24000 pstree 0xfffffa8006d26890: 0 0 0 ------ 1970-01-01 00:00:00 UTC+0000 C:\Users\W0457579\Documents\volatility-master\volatility-master>python vol.py -f "Clone of Clone of Windows 7 x64-a88debbd.vmem" --profile=Win2008R2SP1x64_23418 pstree 0xfffffa8006d26890: 0 0 0 ------ 1970-01-01 00:00:00 UTC+0000 C:\Users\W0457579\Documents\volatility-master\volatility-master>python vol.py -f "Clone of Clone of Windows 7 x64-a88debbd.vmem" --profile=Win2008R2SP1x64 pstree 0xfffffa8006d26890: 0 0 0 ------ 1970-01-01 00:00:00 UTC+0000 C:\Users\W0457579\Documents\volatility-master\volatility-master>python vol.py -f "Clone of Clone of Windows 7 x64-a88debbd.vmem" --profile=Win7SP1x64_24000 pstree 0xfffffa8006d26890: 0 0 0 ------ 1970-01-01 00:00:00 UTC+0000 C:\Users\W0457579\Documents\volatility-master\volatility-master>python vol.py -f "Clone of Clone of Windows 7 x64-a88debbd.vmem" --profile=Win7SP1x64_23418 pstree 0xfffffa8006d26890: 0 0 0 ------ 1970-01-01 00:00:00 UTC+0000 C:\Users\W0457579\Documents\volatility-master\volatility-master>python vol.py -f "Clone of Clone of Windows 7 x64-a88debbd.vmem" --profile=Win7SP1x64 pslist 0xfffffa8006d26890 0 0 0 -------- ------ 0 C:\Users\W0457579\Documents\volatility-master\volatility-master> does this work better? |
and i understand but i simply wish to work out whats wrong with 2.6 |
Please use the -vvv option so that more logs are made and upload that. Vol3 has a 2.6.1 version, or do you mean you're trying to run the old python2 framework? If so you'll have more luck raising an issue there. Edit: yes sorry. I see you are using the old framework. You'll be better off raising an issue there. |
how do i use the -vvv option? |
To use -vvv with the newer framework you would do this.
I'm not sure about extra logging with the older framework, you're better off raising an issue there if yiu want help understanding that. I'd really encourage you to use the newer framework. |
C:\Users\W0457579\Documents\volatility-master\volatility-master>python vol.py -f "Clone of Clone of Windows 7 x64-a88debbd.vmem" --profile=Win7SP1x64 -vvv pslist 0xfffffa8006d26890 0 0 0 -------- ------ 0 C:\Users\W0457579\Documents\volatility-master\volatility-master> alright here's what i was able to find |
also where do you reccomend i ask this issue? |
Yes, that is the older Framework. I can't personally help you with that. You'll have more luck using the newer framework or raising an issue on the older frameworks page. This isn't an issue with vol3. |
where's the older frameworks page? |
how do i comment on the page since im not seeing the option to do so? |
In exactly the same way you created this issue, just on that project instead https://github.com/volatilityfoundation/volatility/issues GitHub guide: https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue I'd really recommend using the newer framework. |
Please keep in mind that volatility 2 is no longer supported and was last updated 4 years ago. You'd be better advised trying to get volatility 3's pslist to work on the memory image you have. |
I am attemtping to use pstree on volatility 2.6.1 and for whatever reason it does not appear to be working despite my using multiple profiles. and i require assistance in trying to find the cause of the error and correcting it?.
The text was updated successfully, but these errors were encountered: