-
Notifications
You must be signed in to change notification settings - Fork 886
Problem with installing veil frame work #241
Comments
Can you check the repos that you are using? I just verified Veil to be running and installing fine on the latest version of Kali that was release a day or two ago. |
Yes I have checked and here are the repositories **# deb cdrom:[Debian GNU/Linux 2018.1 Kali-rolling - Official Snapshot amd64 LIVE/INSTALL Binary 20180126-21:23]/ kali-last-snapshot contrib main non-free #deb cdrom:[Debian GNU/Linux 2018.1 Kali-rolling - Official Snapshot amd64 LIVE/INSTALL Binary 20180126-21:23]/ kali-last-snapshot contrib main non-free** |
Unfortunately, it must be something isolated with your system. I am running the latest Kali and I was able to successfully install Veil. If you can provide me steps to reproduce this, I will be happy to look into it. However at the moment I can not reproduce the error. |
@kallemAnvesh Edit your sources.list and remove everything then append the following lines and do
|
Did this work for you @kallemAnvesh? |
@kallemAnvesh are you running headless by any chance? If so, use |
Closing due to no response |
i fixed the probleme deb http://http.kali.org/kali kali-rolling main non-free contrib and save it after that , you go to terminal and write apt-get update after that write : ./setup.sh --silent --force and you will have no probleme inshaallah if you still have the probleme try this command apt-get install wine32 and apt-get install wine and |
@ChrisTruncer @achrafesodhso I have tried all the above mentioned lines like changing the source list and apt update , and then started the setup with slient and force still i see sames issues. I am unable to install wine wine32 and winetricks also as standalones. |
This workaround worked for me and fixed the problem. |
I have the same problem. Please I would be glad if someone can help |
tried this and all other suggestions and nothing worked. still having same issue. anyone have any other ideas? |
tried this, but nothing changed.. |
update your kali linux os 2020.3 to 2020.4 |
i have 2021.3 but Veil is not getting installed can you please help me ? |
|
Anyone has any idea of what can be? Tried installing from Github, after running: ./config/setup.sh --force The same issue as above was displayed. When running: /usr/share/veil/config/setup.sh --force --silent The same output is printed Im on Debian 12, above the specified Debian 8 in the error. Since nothing seemed to work I added the kali repo along the GPG key. The installation went smoothly, but when running Veil the same problem was faced Any tips on what can be done? |
Veil version
Veil 3.1.X
OS Used - all info (architecture, linux flavor, etc)
4.14.0-kali3-amd64 #1 SMP Debian 4.14.12-2kali1 x86_64 GNU/Linux
How did you install Veil? (Apt, Clone from Github, etc.)
Clone
Did you run the setup script?
yes i Did. The setup.sh file was in CONFIG folder
Pastebin link to error you are encountering (include console actions you took prior to error)
command before error: - /Downloads/Veil# ./config/setup.sh --force --silent
Error: - **[ERROR] There was issues installing the following:
Failed with installing dependencies (1): 0
Failed with installing dependencies (6): 0
Failed with installing dependencies (5): 0
Failed with installing wine (2): 0
Failed to run (wine) Python pip... Exit code: 193
Failed to run (wine) Python pip future... Exit code: 193
Failed to run (wine) Python pip pefile... Exit code: 193
Failed to install (Wine) Ruby.exe... Exit code: 193
Failed to run (wine) Ruby OCRA.. Exit code: 49
Failed to run (wine) AutoIT.. Exit code: 193
[I] If you have any errors running Veil, run: './Veil.py --setup' and select the nuke the wine folder option**
Expected behavior
Any additional info you want to tell me
I have tried ./Veil.py --setup command but the error after using this command is
[!] ERROR #2-3: Can't find the WINE profile for Ruby v1.8.7 (/var/lib/veil/wine//drive_c/Ruby187/bin/ruby.exe). Run: /root/Downloads/Veil/config/setup.sh --force --silent
The text was updated successfully, but these errors were encountered: