TotalCommander crashes on win7x64
Moderators: Hacker, petermad, Stefan2, white
TotalCommander crashes on win7x64
Ever since installation of the latest Microsoft updates this week my Total Commander 7.56a crashes. I have tried on 2 computers; pack or open files, or copying files to a networked drive or deleting a file on a networked drive.
Having used Totalcommander for many years, I now realize how many tasks I use it for each day !!
From eventviewer:
Faulting application name: TOTALCMD.EXE, version: 7.5.6.1, time stamp: 0x2a425e19
Faulting module name: ntdll.dll, version: 6.1.7600.16695, time stamp: 0x4cc7ab86
Exception code: 0xc0000005
Fault offset: 0x00058e0f
Faulting process id: 0x298
Faulting application start time: 0x01cbcaaa50543bf4
Faulting application path: C:\totalcmd\TOTALCMD.EXE
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: c94efb0a-369d-11e0-9b92-005056c00008
Having used Totalcommander for many years, I now realize how many tasks I use it for each day !!
From eventviewer:
Faulting application name: TOTALCMD.EXE, version: 7.5.6.1, time stamp: 0x2a425e19
Faulting module name: ntdll.dll, version: 6.1.7600.16695, time stamp: 0x4cc7ab86
Exception code: 0xc0000005
Fault offset: 0x00058e0f
Faulting process id: 0x298
Faulting application start time: 0x01cbcaaa50543bf4
Faulting application path: C:\totalcmd\TOTALCMD.EXE
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: c94efb0a-369d-11e0-9b92-005056c00008
- ghisler(Author)
- Site Admin
- Posts: 49100
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Other programs seem to have problems with the patch too (although I cannot reproduce it here with TC). Just make a search for
KB2393802 crash
Maybe you can find out what is interfering with TC and the patch.
KB2393802 crash
Maybe you can find out what is interfering with TC and the patch.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
- Balderstrom
- Power Member
- Posts: 2148
- Joined: 2005-10-11, 10:10 UTC
Just uninstall that patch, it is a paranoid hotfix that appears to be wreaking havoc with systems.
To even cause the issue it is trying to prevent someone has to have login credentials for your machine, or you yourself running a specially crafted "application".
To even cause the issue it is trying to prevent someone has to have login credentials for your machine, or you yourself running a specially crafted "application".
Note: there is an interesting password feature of WinXP (maybe Win2K as well, I'm not sure, but), if you make your logon with a blank password, it completely disables remote access (login) to the machine.Microsoft Security Bulletin MS11-011 wrote:The vulnerabilities could allow elevation of privilege if an attacker logged on locally and ran a specially crafted application. An attacker must have valid logon credentials and be able to log on locally to exploit these vulnerabilities. The vulnerabilities could not be exploited remotely or by anonymous users.
Windows XP Baseline Security Checklists wrote:@MS Technet
Use Account Passwords
To protect users who do not password-protect their accounts, Windows XP Professional accounts without passwords can be used only to log on at the physical computer console. By default, accounts with blank passwords can no longer be used to log on to the computer remotely over the network or for any other logon activity except at the main physical console logon screen. For example, you cannot use the secondary logon service (RunAs) to start a program as a local user with a blank password.
Assigning a password to a local account removes the restriction that prevents logging on over a network. It also permits that account to access any resources it is authorized to access, even over a network connection. As a result, it is better to leave a blank password assigned to an account rather than assigning a weak, easily guessed password. When assigning account passwords, make sure the password is at least nine characters long and that it includes at least one punctuation mark or non-printing ASCII character within the first seven characters.
Work around found.
It took some time, but here is what I found.
I have located the problem to the following line in wincmd.ini
x64DisableRedirection=1
changing the value to 0 solves the crash problem.
This is also necessary after installation of servicepack1
which, I think, have KB2393802 and most other existing updates incorporated. (Tested on my laptop).
A simple test was just to open a pdf-file from TC.
1~ crash
0 ~no crash
It took some time, but here is what I found.
I have located the problem to the following line in wincmd.ini
x64DisableRedirection=1
changing the value to 0 solves the crash problem.
This is also necessary after installation of servicepack1
which, I think, have KB2393802 and most other existing updates incorporated. (Tested on my laptop).
A simple test was just to open a pdf-file from TC.
1~ crash
0 ~no crash