TC 11.02 crash using UNC

[rocketchickenrider]

We have a lot of crashes starting TC 11.02 with elevated privileges and the using an UNC path.
TC simply quits without error or warning. After several retries using the same UNC, it will work sometimes.

[ghisler(Author)]

Total Commander itself has no problems accessing UNC paths while elevated, so my guess is a shell extension or plugin. Total Commander catches exceptions occurring in its own code, a vanishing program usually means an exception in a third party thread which can't be caught.

You can use the tool Procdump from Microsoft to create a crash dump:
https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx

1. Create new directory c:\dumps
2. Create a lnk file of procdump.exe or procdump64.exe (for 64-bit Windows) in Total Commander with Ctrl+Shift+F5, e.g. procdump.lnk
3. Open the properties of the lnk file with Alt+Enter
4. Change the command from c:\path\procdump.exe to
"c:\path\procdump.exe" -ma -i c:\dumps
5. Important: Click on "Advanced" and check option "As administrator"
6. Run procdump with this link file
7. Wait until the crash occurs.
8. To stop creating dumps, execute in Command Prompt: procdump.exe -u
9. Send me the dump file from c:\dumps (zipped, just ONE!!!).

If you prefer, you can analyze the crash dump yourself:
1. Get Windbg from Microsoft:
https://developer.microsoft.com/en-us/windows/hardware/download-windbg

Usage:
1. Create new directory c:\Symbols
2. Run Windbg
3. Menu File - Symbol search path, add the following:
srv*C:\SYMBOLS*http://msdl.microsoft.com/download/symbols
4. File - Open crash dump - choose the dmp file
5. Enter the following in the command line:
!analyze -v
(including the exclamation mark!) and press ENTER.
6. Wait
7. When the result is there, select all, press Ctrl+C and paste the result to the forum.

[Dalai]

Does the UNC path require (separate) credentials when accessing it elevated? If so, does TC/Windows prompt for them or does it crash before that?

Regards
Dalai

[ghisler(Author)]

Any news? The beta test is slowly arriving at its end, so if you want to see anything fixed, please submit a crash report.

[ghisler(Author)]

Please provide more information, otherwise I will have to move this thread to "will not be changed".