Armitage black blank screen

[giskismet]

Hi guys,

I am running kali 2016.1 64 bit on a hp probook 6560b. I use it as my main os.

When I try using armitage, as soon as armitage starts up, I get a black blank screen with a blinking cursor and then I need to restart.
It also happened while I was watching a tuto on youtube at the same time and I could still hear the sound once it had crashed... if this can help...

Thanks in advance and thanks to offensive security and developers.

[ij0see]

..........

[NoahWL1]

I'm having the same problem. Opening Armitage results in a black screen with a blinking white cursor, and it won't go away until the computer is restarted.

[azzarin]

I have the same problem. Same with Cobalt Strike.

[Gn0m3]

Same Here!

Regards

Gn0m3

[corvus]

Same problem here. I even try to download armitage from the official website and replace the files under /usr/share/armitage but that did not work

[Gh0sT.sh]

Make sure that Metasploit or MSF pakages are downloaded and installed properly
if its onb windows i recomond you to install metasploit for windows first
in Linux or ubuntu
go to terminal
update metasploit pakages using #msfupdate
start mySQL or PostgreSql which ever you are suing with Metasploit

then start Armitage

Armitage is just a Graphical-User-Engine but the heart is MSF and Psql so without the dependencies it wont start
so start these services first


or try

#sudo apt-get install --reinstall Armitage

:0

[ij0see]

..........

[Gh0sT.sh]

for Armitage this is the install and starting process my friend
https://www.offensive-security.com/m...rmitage-setup/

for cobalt this is the install and starting process my friend
http://www.advancedpentest.com/help-install-kali-linux

do as recomonded step by step in the guide

[ij0see]

..........

[ij0see]

..........

[giskismet]

Thanks everyone.

Solved it reinstalling metasploit, reinitialising the database, reinstall armitage then updates and upgrades... but It might just be the upgrades that solved it as i Had quite a few

[mechgt]

I've run into this as well. My experience is when armitage is attached to a workspace *other* than the default. The solution was to set the workspace back to the default workspace and then scan/import hosts, etc.