TC crashes when I click on this file (vim update)

[raytc]

TC crashes when I click on this file:

https://github.com/vim/vim-win32-installer/releases

gvim_7.4.2330_x86.exe

The same with all other previous Vim updates.

My OS: Windows 10 pro 64 bit
My TC = the last beta (9.0 Beta12 64 bit 2016-08-31)

I have GVIM 32 bit installed.

[ghisler(Author)]

No crash here! I have also tried with virustotal that the file isn't infected.

The program would be run with higher user rights. Apparently there is a problem on your PC when trying to do this.

What happens when you try to run tcmadm64.exe or tcmadmin.exe from Total Commander directory? It would need the same higher rights. Do you get a crash too?

[raytc]

Hi, Thanks for your answer.

No, no crash when I clicked on tcmadm64.exe and worse... no crash now when I clicked on gvim_7.4.2330_x86.exe

All my gvim updates TC crashed (I had to open them from the win explorer in my pc). Now the same file didn't crash. Don't know the reason.

[raytc]

Downloaded the last update:
https://github.com/vim/vim-win32-installer/releases

gvim_7.4.2334_x86.exe

(https://github.com/vim/vim-win32-installer/releases/download/v7.4.2334/gvim_7.4.2334_x86.exe)

TC crashed again.
Tried with higher user right: TC crashed again.
Stopped virusscan (avast): TC crashed again

The update from yesterday doesn't crash.

Can you please check the above file and see if it crashes also on your pc?

[wanderer]

TC crashed again.
Tried with higher user right: TC crashed again.
Stopped virusscan (avast): TC crashed again

Tried clicking on gvim_7.4.2334_x86.exe with b12 under Win7 (just for the fun of it - no Win10 here), no crash. Is there a chance of a plugin interference? Tried with a clean INI?

[ghisler(Author)]

Unfortunately I still cannot reproduce any crashes. What exactly happens? Do you get some kind of error message? Or does TC disappear? Or hang?

[Dalai]

2raytc
How do you "click on the file"? Do you mean double-click, i.e. launch/execute it, or do you right-click on it? If it's a right-click, a buggy shell extension immediately comes to my mind.

Regards
Dalai

[ghisler(Author)]

Unfortunately I still can't reproduce it.

I need some kind of stack trace. Could you use the tool Procdump to create
one for me, please:
https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx

1. Create new directory c:\dumps
2. Start it like this:
procdump -ma -i c:\dumps
3. Wait until the crash occurs.
4. Send me the dump from c:\dumps.

[ghisler(Author)]

Any news? I cannot help you without more details...