MobaXterm Local Terminal Doesn't work - Closes immediately
Solution 1
Update: I just now helped someone with this and the solution that worked was uninstalling the "installation" version and then downloading and using the "portable" version.
For my installation, there are files in C:\Users\username\Documents\MobaXterm
.
Perhaps back them up (especially if you have SSH keys or other important files or configuration in them) and then delete that directory before another clean install of MobaXterm.
If you've tried all of the solutions on this page that make sense, you can also try contacting Mobatek to file a bug report.
Solution 2
You must enable Enable Windows Subsystem for Linux feature on Windows 10 and then it works. Here is a link how you can enable this: How to Enable Windows Subsystem for Linux
Solution 3
I had the same issue in the portable version. I fixed the problem in 3 steps :
- I downloaded the CygUtils.plugin (http://mobaxterm.mobatek.net/CygUtils.plugin),
- Put the file above in the directory where MobaXterm exe file is
- I removed MobaXterm .log, .ini and backup files in the same directory
Solution 4
Like others I openen C:\Users\username\Documents\MobaXterm, but deletion of the MobaXterm.ini did not help. I also had to delete the .log file before MobaXterm woke up again.
Tip: do not delete the .ini file but rename it to MobaXterm.bak.ini. This way you still can copy some of the old configuration data out of it to use in the new one. I saved my bookmarks this way.
Solution 5
Same problem form me, solved by backup and then delete the config file:
C:\Users\Your_Name\Documents\MobaXterm\MobaXterm.ini
if you have changed you document home directory, then find the file MobaXterm.ini
in MobaXterm of that directory.
You can use the tools everything
to find it easily.
Related videos on Youtube
Comments
-
Aditya Vikas Devarapalli over 1 year
I'm able to SSH to into other machines using MobaXterm, but when I try to run the Local terminal, the Tab just opens and closes all by its own. Am I missing something like a config file ? I tried running it as an Admin as well, but no luck.
I am on Windows 7 Enterprise Edition 64bit and started with MobaXterm v9.0. I tried totally uninstalling MobaXterm v9.0 (including deleting the CygUtils plugin) and then installing the latest MobaXterm v9.1 and CygUtils plugin. However, the same problem persists.
-
Aditya Vikas Devarapalli almost 8 yearsWindows 7 Enterprise Edition 64bit and MobaXterm v9.0 @ChristopherBottoms
-
Aditya Vikas Devarapalli almost 8 yearsI tried upgrading, but that didnt help @ChristopherBottoms
-
Aditya Vikas Devarapalli almost 8 yearsTried it... Doesnt work ! :(
-
Aditya Vikas Devarapalli almost 8 yearshaha... Yeah... that's the first thing I did
-
Mohy Eldeen over 7 yearsAditya, were you able to fix this? I started having the same issue!
-
Aditya Vikas Devarapalli over 7 years@Mohy Eldeen... Unfortunately no
-
Ankit Patel over 2 yearsOkay. I had the same issue in installed verion. Fixed by Resetting the configuration. Settings->Reset configuration -> Reset the entire MobaXterm configuration
-
-
Aditya Vikas Devarapalli about 6 yearsplease note that I specifically mentioned that this error occurs on a Windows 7 machine, NOT A WINDOWS 10 machine.
-
Jamie Carl about 6 yearsPlease note, that this actually fixed my problem. Thanks Stefan.
-
THESorcerer almost 4 yearsREALLY ?!? you honestly instruct us to remove .ini and LOSE ALL SAVED SESSIONS ?!? thank you very much, FOR NOTHING !!!!
-
THESorcerer almost 4 yearsTURN THE POWER ON DUDE ... not only that I have the same problem, and WSL is on, but cygwin HAS NOTHING TO DO with WSL, and MobaXTerm is based on cygwin, otherwise it will NOT work on older windows
-
рüффп almost 4 yearsNote that I have the same issue as the OP but I am under WSL (v1) and Windows 10. It lacks documentation on how to configure the automatically created WSL session. It returns immediately when I connect to WSL.