For reasons unknown yet, my MobaXterm Local Terminal will not start any more on Windows 7 box. There is not even a single error prompt of why this may be happening. I am still able to ssh into remote hosts. Could someone please suggest how to turn on logging in MobaXterm of all its events etc. so that I can debug this break?
Alternatively any explanation on why only the MobaXterm Local Terminal may not start in the application would also be very much appreciated.
Thank you very much for your help.
So the workaround for now is to revert to a previous version of MobaXterm (agree.. not the best solution).
-- Uninstalled MobaXterm 9.1
-- Reinstalled MobaXterm 8.6
Not necessarily we need to move to an old revision. I hope we can take any latest stable branches (not installer) portable edition, and use it.
If this works, there was something goofed up in the installer folder.
This portable edition can be continued, for same configuration and other settings, copy and paste the MobaXterm.ini file from your old location and check if that restores all your settings or crashes.
If this crash, this is day clear of the reason, else we have the old favourite restored.
Related
I've been a happy user of MobaXterm for years, this is a great terminal and X-window manager on Windows to access Linux machine and others. Recently, possibly since I upgraded to Windows 11 or changed laptop, I sometimes get the following error window:
An error occurred while starting the following MobaXterm subprocess:
"%APPDATA%\MobaXterm\slash\bin\MobaSCPRinew.exe"
Access is denied
I could not figure out which action is triggering this error but it is pretty rare and seems to happen either when I switch from one tab to another or when I unlock my computer after a while but I can't reproduce it systematically. I'm using MobaXterm Personal Edition v22.0 Build 4858.
This executable exists on my system and the file properties mention that this is a "Command-line SCP/SFTP client". However, even after the error, the SSH Browser available in the side bar (provided you only show one tab) is still visible and working.
Does anybody know what could be causing this?
Thanks
[EDIT]
I contacted the support of MobaXterm:
they told me it is a known bug related to the "Remote Monitoring" feature, which can display stats about memory, disk usage, connected users,...
advised me to test the preview version 22.2 since the bug seems fixed in that release
I used it for a few days and the issue never happened. I will download the latest official release 22.1 and, if it happens also in that one, will wait for the official 22.2. I will close this issue once the bug is fixed in an official release.
Same issue here, with some slight differences:
Location seems to be the "Documents" folder of my "Onedrive":
E:\OneDrive - xyz\Documents\MobaXterm\slash\bin\MobaSCPRinew.exe"
I use the "professional edition" with the same license ID, so I suppose technically it is the same software.
Issue only popped up till now after a reboot of my system, launching the MobaXterm and subsequently starting an ssh session.
Restarting MobaXterm only (once) didn't produce the issue.
I now upgraded to 22.1. Since the release notes do not mention anything concerning this issue, I can't know for sure the problem will be solved. I'll report back when it reoccurs.
Johan
There is a hotfix version of Tortoise Git and my PC refuses to install it. It keeps saying Windows Explorer is running, even when it is not showing the Task Manager.
Is there any other way I can get this upgrade to install?
Update
I decided to start Windows 10 in Safe Mode so we can be sure that nothing is running. Yet it still would not perform the upgrade (with Administrator privileges):
I used Task Manager and I could not see gitdll.dll in the list of running processes.
1.download hotfixes
2.restart windows (don't open any apps after restart)
3.run Task Manager (from windows bar)
4.run hotfix from menu of Task Manager -- File -- Run new task
I have the same issue; I solved it by running:
listdlls64 -d "c:\Program Files\TortoiseGit\bin\gitdll.dll"
and used task manager to manually kill all processes that were using the dll, including explorer.exe. This seems entirely unnecessary but it's what worked for me.
Why so many processes (including LogonUI.exe, OpenWith.exe, splwow64.exe, etc.) attached to gitdll.dll, is unknown, and seems like an issue that can be solved. We know that explorer uses that dll, but you would think the installer/updater would expect that and be able to work around it.
In 2.10.x hotfixes there was a bug in the hotfix updater which was unable to offer a restart for replacing gitdll.dll during a restart cycle. A failure to replace this file caused lots of crashes (cf. https://tortoisegit.org/issue/3599).
Please download the full installer for TortoiseGit and install it (https://tortoisegit.org/download/; there might be a warning regarding a possible downgrade, this can be ignored).
Generally
The .MSI installer and newer hotfixes offer two options when installing:
Try to restart open processes - this might fail as described in https://stackoverflow.com/a/61026137/3906760 based on some third-party software.
Requiring no closing/restart of open programs but the replace the file on reboot. This should work in any case because the file is replaced before starting any programs using it.
I tried both types of installer:
Hotfix
Full
And both were refusing to work. I then occurred to me that all the icons were flashing on my desktop and it was stuck. This was consistent behaviour.
So I decided to switch of my Star Dock Fences:
Right-click Desktop and select Configure Fences:
Scroll-down to the bottom of the pop-up window and un-tick Enable Fences:
Close the window.
Now I was able to install the hot-fix. Interestingly the installer was only complaining about the Windows Explorer still running and did not list Fences.
I hope this helps any others who have struggles upgrading TortoiseGit.
I have successfully installed disabling AVIR and allowing the installer to close as much as it wants
I just recently upgraded to Windows 10 and ever since I have upgraded I can't get into VB6. I keep getting the System Registry error. I have googled and tried about everything and nothing seems to work. Running VB6 as Administrator is not an option, don't ask but we can't have admin to our computers we have to be logged in as users. The way we use to fix it was to trick Windows 7 log on as Admin run VB6 as Admin then switch me back to user and it worked, but this no longer works. Does anyone have any suggestions that currently have VB6 working as a user and not admin? I really don't want to resort to have to run it out of my virtual machine :( Thanks in advance!
Amanda,
I know it is 3 years later and I wonder what you did. and my solution may be late.
I moved VB6 Enterprise to a Windows10 machine, I did not upgrade the machine to Win10 with the IDE. However to make it work for some of my clients with Win10 machines I:
Back up all the VB6 files, folder and directories.
Using control panel in Win10, uninstall VB6 app. That's right, uninstall!
Using the original install disk, running it as an Administrator, install the program.
If the program has been updated to a later version, you need to get a copy of the latest version and copy over the one that was installed.
Or, Sweet Talk your IT guy into making you a new install disk with the latest version you are supposed to be running.
Go to the folder where the exe file is installed, Right Click on it and open the Properties, and go to the Compatibility tab.
Choose run as an administrator, and also click the Run this program in compatibility mode for Windows XP Service Pack3, or if it shows Latest version of Windows XP try that. You may need to check with your IT department.
Warning: if the VB6 program uses any non-Microsoft tools you may need to register them by hand.
I suspect this has already been worked out for you, but I put it here for anyone that may stumble across it, needing it.
The situation:
I reinstalled my PC and installed Windows 8. I also installed the latest version of TortoiseSVN. My files are on another (Ubuntu) PC on my network, so windows sees that drive as a network drive.
The problem:
TortoiseSVN sees the directory as an svn repository, no problem there. I can choose commit, enter a comment and choose which files to commit and such. Works all as expected. But once I click the commit button, nothing happens. I mean the commit screen appears, but that's it. Nothing happens after that.
This setup used to work perfectly when my PC was still running on Vista.
Does anybody has any ideas on what may cause this? Cheers!
Issue #1: Accessing a working copy across a network share is not supported, and is generally discouraged.
Issue #2: If your working copy was created/last used with a version of TortoiseSVN (or any other client) which is not 1.7.x, then it is not compatible with the latest release. You must manually upgrade each working copy with svn upgrade on the command line, or right-click -> Tortoise SVN -> Upgrade in Windows. But this will render the working copy unusable for older versions...so if you're using that WC from Ubuntu as well, you need to upgrade your client(s) there as well. Which goes back to issue #1 - sharing a WC can get messy.
I installed HP sound driver yesterday and it BSOD-ed my windows and crashed it. System repair didn't help. system restore is corrupted, and startup recovery just says ""patch is preventing windows from starting". when I try to boot, it loads up to certain amount of time and then in just BSOD-s to 0x0000007b.
I disabled the new driver in registry, but it didn't help.
I then installed another windows copy on a new partition, and tried copying over the registry and system32\drivers folder, still the same issue.
Any further ideas? if I could somehow just use the files from system restore that are not corrupted, and leave the rest out, that would help but I don't know how to do that.
Reinstallation was the only way to go unfortunately. I tried replacing windows files, reintegrating registry.. nothing gave stable results. This is not a solution, as I was trying to fix the computer, not reinstall OS.