Drive buttons don't properly detect changes

[gmolnar]

Version: TC 8.51a 64 bit

1. Run TC (2 drive button bars visible)
2. Mount a new TrueCrypt volume

Result:
Drive buttons do not show the changes (the new drive letter) until I click the drive selector dropdown below the drive button bar.

This used to work properly in earlier versions (before 8.5x)

[ghisler(Author)]

Total Commander reacts to WM_DEVICECHANGE messages to show added or removed drives. This is working fine here, I have just tested it with TrueCrypt. Either Truecrypt isn't sending WM_DEVICECHANGE on your computer, or you have disabled it in the configuration of Total Commander:
wincmd.ini
[Configuration]
DeviceChange=0

If this line is present, remove it.

[Horst.Epp]

Version: TC 8.51a 64 bit

1. Run TC (2 drive button bars visible)
2. Mount a new TrueCrypt volume

Result:
Drive buttons do not show the changes (the new drive letter) until I click the drive selector dropdown below the drive button bar.

This used to work properly in earlier versions (before 8.5x)

Works fine here.
TC 8.51a x64 under Windows 7 Ultimate x64 and Truecrypt 7.1a

[gmolnar]

I have just tested it with TC 8.01 x64 and it is working fine, however with 8.51a it is not.
I do not have DeviceChange=0 in my wincmd.ini file.

What else could be the problem?

OS is: Windows 7 Pro SP1 x64 ENG

If I run the versions 8.51a and 8.01 side by side, I can see the new drive button appearing in 8.01 but not in 8.51a.

[ghisler(Author)]

Are you running TC 8.51a with higher user rights (as administrator)? You can check this by looking at the title bar: If there is a ^ sign, TC is running with higher rights.

In this case, the notification isn't sent to the elevated program. Windows prevents messages from lower level to higher level programs, for security reasons.

[gmolnar]

Yes. That was the problem exactly.
If I run it as a normal user, it works.

Thank you very much!

[MVV]

gmolnar,
You can start TrueCrypt in elevated mode if you want it to work with elevated TC.

[nicolap]

I'm having the same problem on Win 7 X64 SP1.
Tryed to:
- insert the following settings in wincmd.ini file under [Configuration] section
HideRemovableNoMedia=7
DeviceChange=1
- restart Total Commander
- start with or without Elevated mode
- disconnect the drives with or without the Safe removal procedure
In the windows Explorer the list of drives is ever correct.
Only a reboot restore the correct list of drives.

This happens with USB drives, removable card readers, Truecrypt units.

[ghisler(Author)]

Maybe drive insert notifications have been disabled in device manager? Some optimization tools can cause this too.

[nicolap]

Maybe drive insert notifications have been disabled in device manager? Some optimization tools can cause this too.

Of course the absolutely @#§ç£$ "drive insert notification" is disabled!
- it's disabled in registry
- was disabled just after win7 installation, no change in the last 2 years!
The problem is only of Total Commander and only from lasts versions.

[Horst.Epp]

Maybe drive insert notifications have been disabled in device manager? Some optimization tools can cause this too.

Of course the absolutely @#§ç£$ "drive insert notification" is disabled!
- it's disabled in registry
- was disabled just after win7 installation, no change in the last 2 years!
The problem is only of Total Commander and only from lasts versions.

So you tell us that the necessary feature is disabled but you insist that TC should function regardless of this.
What a stupid idea

[Hacker]

[mod]Horst.Epp,

What a stupid idea

I would really really like you to be the polite helpful guy you have always been up until a few months ago. Could that be arranged?

Hacker (Moderator)[/mod]

[nicolap]

So you tell us that the necessary feature is disabled but you insist that TC should function regardless of this.

I (and a lot of people) think that it's not a necessary feature BUT a big security hole.

I must say that what here we are calling "drive insert notification" is also known as "Autorun" (or similar). This is reductive because there are some function correlated each other and it's not easy to understand correctly how it works between different windows versions.
Actually what I done is only to set
NoDriveTypeAutoRun=0xff
in the registry.

I use extensively VM's to run software, leaving near untouched the main host installation. And after the installation of TC 8.5 I have not installed any new software.
I'm here not to blame TC or others ideas', only to request help.
Thanks

[Dalai]

I must say that what here we are calling "drive insert notification" is also known as "Autorun" (or similar).

No, it's not! Auto-insert notification does what it says: it notifies the system (the programs) that a new medium/drive was inserted. It does nothing more! Autorun on the other hand also does what it says: it executes commands listed in autorun.inf on the newly inserted medium/drive (if there is any). Then there is AutoPlay - kind of a successor of AutoRun - which searches the whole new medium for relevant files (executables, audio & video files and so on) to be able to show a dialog the user can choose from what to do with the new medium/drive.

My systems have AutoRun/AutoPlay disabled since more than 10 years with this registry key:

Code: Select all

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer]
"NoDriveTypeAutoRun"=dword:000000ff

but "Auto-insert notification" has always been enabled on all of them and none of them has or had any problems with newly inserted drives.

EDIT
Do you have the "Shell Hardware Detection" service disabled?

Regards
Dalai

[ghisler(Author)]

Yes, they are in fact two different things - the insert notification causes the WM_DEVICECHANGE message to be sent to programs, so they can react to disk additions/removals. Autorun is disabled here too, it has nothing to do with it!