I had previously installed msys2 on Win7. After installing latest updates on Win7, the bash that comes with msys2 did not work any more. I removed msys2 and tried reinstalling it (the latest 64bit version form msys2.org).
The installation process stops at 66%. On details, it shows installing C:\msys64\usr\share\terminfo\6e\nansi.sys and it won't move forward.
In the task manager it shows several bash.exe processes. If I kill these processe, the installation ask if I want to try again? If I agree, a new bash.exe process appears and nothing happens. The installation won't move forward.
Can anyone tell me where the problem might be?
Related
I want to install Python 2.7.12 but It shows following error.
There is a problem with this window installer package. A program required for this install to complete could not be run.
I saw one youtube video (https://www.youtube.com/watch?v=KikshWVWhzg) and so I provide full access to system and User. Even then, the same problem occurs.
How to solve this problem?
I solved this problem by my own.
Actually what happens is: In past, I installed Python 2.7.10 and by mistake, I deleted python27 file from C drive. But python remains installed in computer and when I tried to uninstall it, It shows the same error as above. So to uninstall this,
first I download similar python file (python2.7.10ci) version and try to install it. And you see it got installed. Due to this a file get generated in C drive with name python27 and now I can uninstalled python which I installed a long time back.
After uninstalling old python2.7.10, I right click on python 2.7.10ci (in control panel ) and choose repair. Due to this again a file generated with python27 and now I uninstalled this too easily.
After doing all this, I downloaded python 2.7.12 and try to install. And I able to install this without any error.
I have recently moved my android development environment on OS X, using El Capitan. Everything is working as expected. The only problem i find is that after every time I restart my PC the HAXM gets disappeared from '/dev' and Android Studio Reports it while starting an emulator using the HAXM.
When I go to extras in Android SDK folder and try to install, it says that the same is already installed and if continue, it will be reinstalled. I continue to install. After which every thing works fine, till next reboot of the system.
Can anyone please tell me, how to resolve the issue. It is not a big task to reinstall HAXM, but it is really annoying.
Figured this one out: when upgrading from HAXM 1.1.4 to 1.1.5 on El Capitan, the installation path moves from /System/Library to /Library. However, the in-place upgrade script shipped by the HAXM installer doesn't handle this perfectly, which leaves things in a funky state. It is for this reason that the HAXM page says:
Before installing HAXM 1.1.5, the previous version (1.1.4 and below) must be uninstalled using:
sudo /System/Library/Extensions/intelhaxm.kext/Contents/Resources/uninstall.sh
If your installation is already broken because you didn't uninstall 1.1.4 before installing 1.1.5, the following steps worked for me:
Uninstall 1.1.5 from its new path by running /Library/Extensions/intelhaxm.kext/Contents/Resources/uninstall.sh with sudo
Remove left-over 1.1.4 files (specifically for me the key was to remove /System/Library/LaunchDaemons/com.intel.haxm.plist although there may be more files left over in /System/Library for other people)
Reinstall 1.1.5 the normal way
I installed Trac on Windows 7 using Trac-1.0.1.win32.exe.
How do I cleanly uninstall this? My reason for uninstalling is that I installed it with Python 3.4, and then discovered that it actually requires Python 2.7. So I would like to remove the existing install, and re-install it for Python 2.7 .
Nothing appears for Trac in the Windows 7 "Add/Remove Programs" area. There is a program RemoveTrac.exe that was created under the Python34 directory, however when I run that it pops up a MessageBox with title Runtime Error and text This program is normally started by windows, and it does not uninstall.
I'm not sure but to me it seems that installer just checks your environment, detects some pathes and sets them in the installed Trac environment. Trac should be on top of Python and SVN. So likely, you can just remove the installed Trac directory.
I'm trying to update node on my Windows 7 box but I'm not seeing the latest version after I re-install/update node.
I'm just going out to http://nodejs.org/download/ and getting the latest Windows installer, v0.10.28. I then just run that installer where it defaults to installing everything on my local hard drive, including npm, which is cool because I wanted to upgrade that as well.
Install runs/finishes with no apparent problem, but when I do a:
node --version
I'm still seeing my "old" version, v0.10.15, not the latest I supposedly just installed, v0.10.28. My npm version still reports my "old" version as well.
I've tried rebooting as well.
How the heck does one update node/npm?
I had a similar problem but on MacOS and the reason was I had nvm installed. So running the commands found on most websites:
sudo npm cache clean -f
sudo npm install -g n
sudo n stable
didn't work, node -v still displayed the old version.
What I did was to install node from nvm:
nvm install v0.12.6
This will build node from scratch on your machine, and then node -v will display the correct version. I think I could have still used the previous commands by using n and then do nvm use v0.12.6, but this is something to test. If you have nvm installed, just check the commands for nvm to upgrade node.
Answer given by Johan Dettmar about using n will work here as well.
For Windows : open command prompt as administrator
For Linux/Mac : sudo -s on terminal
npm cache clean -f (force) clear you npm cache
npm install -g n install "n" (this might take a while)
n stable upgrade to lastest version
Windows Users
Node is most likely installed in 2 locations.
C:\Program Files\nodejs
C:\Program Files (x86)\nodejs
Rename the folder of the (x86) version to "nodejsOLD", restart command prompt, and try again.
node -v
The installer works just fine, things you do NOT need to do:
You do NOT need to uninstall
You do NOT need to reboot
There is a good discussion for Windows and node on stack overflow here:
How do I update npm on Windows?
I had this exact same problem, and one thing to be careful about is to make sure you are downloading the correct architecture version (e.g. 32-bit or 64-bit). When upgrading, I had downloaded the 32-bit version and didn't realize it. But the previous version I had installed was 64-bit. So I actually ended up with a 32-bit and 64-bit version installed. But when you go to do an uninstall, it only lists one version of node.js, so even after I uninstalled, it uninstalled the latest version, but kept the earlier version on there. That's why I kept getting the old version when I did "node -v".
Once I downloaded the correct version (64 bit in my case), the problem was resolved.
A tip that might be useful for others, I found it helpful to known for Windows platforms.
Enter the command in cmd.exe:
where node
This outputted for me that node.exe was in a subdir of Chocolatey.
Problem was that this version was v8.11.1 and it did not work with newer version of the Angular-CLI. So I removed the exe and then ran the installer of the LTS version of Node on Nodejs website to get a working version of Node for Angular. Tested out on Windows 10.
So if you are on Windows, test out the where command in cmd.exe
Linuxers and Mac-ers can use other commands, such as which command.
Screen shot below. I deleted the node.exe file before running the node.exe command.
To fix this problem you can modify your "Environment Variables".
From "System Properties" open the "Environment Variables".
In the system variables section select the path variable and click on the edit button.
In this list you must have the latest folder of installed Node.js(delete other Node.js folders from the list).
That's it
To update Node, download the latest http://nodejs.org/dist/latest/node.exe (or http://nodejs.org/dist/latest/x64/node.exe for 64bit systems) and replace your old node.exe with it.
To update npm, run the npm update npm -g command.
Even though it might sound stupid, make sure you did not previously have node version managers installed which you no longer use, such as Nodist. These will allow the machine to only have their internal node version as the usable version and not the one you install yourself manually.
Uninstalling these package managers, if you want to manually update your Node/NPM versions, will solve the issue.
I had the same problem - but it was caused due too duplicated versions of nodejs being set in my environmental variables.
You can easily check that in Windows using where node in cmd. If more than one path is being output that might be the reason for this error. You can fix it by removing the other environmental variables.
I had the same problem in Windows 10 and none of the above recommendations worked. Then I closed the terminal window, restarted it and the correct version now showed, and the subsequent version errors running other commands also went away. Seems that the version loaded by Windows PowerShell is stuck until the terminal is relaunched. Clearing the cache via command line was futile.
Seems simple and dumb, but that resolved it for me (in the sense that it probably was resolved in the background but I couldn't see the resolution take effect until the terminal was reloaded). Hope this helps someone else.
Using where node, worked for me. That showed me that I had node in the heroku directory as well and since I won't be using that CLI anytime soon, I just removed that dir from the 'path' 'system variable'.
You can fix this on Windows by following these steps if you have already installed nodejs latest version but that is not showing/working.
Open Cmd type where node it will give you a path (like in the
attachment)
Go to that location and delete the node application
exe file
and then come back and try to check that's all you are done , that was the issue of path, your system was using the old reference
I have recently tried to install Python 3.4 as an alternative installation on my system in an attempt to familiarise myself before migrating code. My main Python installation is 2.7.6.
I tried the 64 bit installer for Windows, but it came up with an error message
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.
After this the install is rolled back (from the point shown below):
I have eventually found a solution to this posted below and decided to share in case anyone else was having the same issue.
After some looking online I found (here) that the issue was related to conflicting pip installs (I have a version already installed for Python 2.7 and apparently this is not compatible with the version that ships with Python 3.4.
To get around this issue I simply de-selected pip from the install options shown below and the install went ahead smoothly:
Run installer again and select PIP installation.
If the PIP fails to install with the same error, you may want to check environmental variables using a tool like http://eveditor.com/ which enables to check whether they are valid. If you had another version installed before, you most likely have wrong PYTHONHOME and PYTHONPATH variables. Fix them by setting them to relevant paths. e.g. PYTHONHOME=C:\python27 and PYTHONPATH=c:\python27\Lib
You will then be able to run and install PIP.
My issue was that I had a PYTHON_HOME or PYTHON_SOMETHING environment variable set. After removing the environment variable, the installation worked perfectly.
What worked for me, strangely enough, was the "Microsoft Program Install and Uninstall troubleshooter"
The "deselect pip" solution did not work for me.
My Python 3.4.1 install was failing with the same "A program run as part of the setup did not finish as expected" error. I tried both installing it on top of Python 3.4.0 and installing it in a new folder, but got the same error. I tried uninstalling Python 3.4.0 first, but got the error during the uninstall, as well.
I ran that Microsoft utility, which helped me uninstall 3.4.0, and was then able to install 3.4.1 cleanly. The utility has options for both problematic installs and uninstalls, so it may help even if you're doing a new install, not an upgrade.
I'm running 64-bit Windows 7, but was working with 32-bit Python versions.
I had similar issues with Python 3.4x on Windows 8.1. Even after a successful install, the uninstaller would fail in the same way. Ultimately, "Method 1" at the MS forum solved this for me when I ran Microsoft's (Un)installer Fix It.
I also had the problem that pip couldn't be installed like #ChrisPosser.
So I deselected pip and the installation went fine. afterwards I restarted the setup, chose "change python" and installed pip. now everything worked like expected.
If you have any problems with windows installers I recommend activating the verbose log like this:
msiexec /i python-2.7.10-1.609.2.msi /lv install-python.log
From the logs I could see that it was the pip install, which was not working.
Yes, I faced the same issue, and was working on this for the past one hour. Was trying to uninstall the Python 3.4.1 from the control panel -> uinstall program -> add/remove program, but was facing issues.
This trick worked for me:
Manually deleted the 3.4.1 folder, which was present in my C folders after I installed the 3.4.1
Then I followed these steps:
-> Went to Regedit.exe, checked in both HKEY_CURRENT_USER, HKEY_LOCAL SOFTWARE Folder, and deleted the Python folders there.
-> windows 8 -> Downloads -> 3.4.1 msi setup (Glad I never deleted it)
-> Right clicked on the msi setup and choose the repair option
-> The repair would re install the Python 3.4.1
-> After this, I un-installed the Python 3.4.1
-> Then I deleted the 3.4.1 msi setup.
Rebooted the system, and now, there is no instance of Python 3.4.1 in my system.
According to me when environment variables containing name 'Python' are created they somehow becomes related with python. I was unable to open idle (GUI PUTHON) and to uninstall it . Deleting a variable named 'PYTHON PATH' solved my all python related problems.
I had 3.7.4 and wanted to move to 2.7.13.
I uninstalled 3.7.4
Tried to install 2.7.13 but got the same error.
There was a 2.7.10 installer(not msi) also present, uninstalling which gave the same error.
So I downloaded 2.7.10 msi, installed it, and then just installed 2.7.13 from the downloaded msi and it worked fine. This overwriting worked because the major version i.e. 2.7 was same for both.
I don't know if this is helpful but after the hours I spent on this, I wanted to write out what worked for me.
Yup, I have already installed another version of python. I have uninstalled them using Program features. But still the same issue persisted because of the folder which was present in my C: drive. After deleting them manually, the installation got completed without errors
I faced this issue because of 2 conflicting versions of 7zip. Removing them both and installing just one fixed this issue.
I had python3.4 installed, then added 3.5, and deleted 3.4. That was a mistake. In trying to get a library to work, I had to go back to 3.4. I uninstalled 3.5, but couldn't uninstall 3.4 (folder deleted).
I ended up searching the registry in rededt32 for "python". There was a Guid folder with a number of entries that had c:\python34 and one more related to the same folder that I deleted. After this, the install worked correctly.
Windows 10.
Mine was linked to having installed an older version in the past, only for my own user account. I got around it by telling the installer to install Python for all users.
For me none of the suggested fixes worked for me. However checking the option "Install just for me" instead of "Install for all users" (Windows 10) worked for me. So this might be another option to try.