Fix context menu crashing

Fix context menu crashing.txt

Some Windows shell extensions will prevent OneCommander from opening the file/folder context menu. 

Incompatible context menu extensions that might cause crashing:
- Fast Explorer
- File Renamer Turbo
- Tim by QQ
- AcdSee Pica View or 
- HoneyView
- GeoSetter
- Cairo

These have to be uninstalled or disabled.

If you don't have any of those extensions:

Download ShellExView 
https://www.nirsoft.net/utils/shexview.html 
(scroll to "Download ShellExView for x64" near bottom of the page)

Run it and then check
Options>Hide All Microsoft Extensions, 
Sort by Type by clicking "Type" column header, and look for "Context Menu" in Type column, 
Disable one-by-one (or several at once) of "Context Menu" type, and each time check if OC can open context menu.

Once you find which context menu extension causes the crash, please report to support at onecommander.com

Note:
- Context menu extension might be handling one file type only, so make sure to test by right-clicking the same file
- Tip: If you have many context menu extensions (example 20), you can click first, shift+click 10th, and then disable all 10 at once, check if OC crashes, if yes, disable the same way 11-15; if not, enable 5-10, and so on, halving the results so it doesn't take many OneCommander restarts and to find the faulty extension faster

@Gurrrra I replied on GGroups but for others who might be seeing this one possible solution:
Reinstall Microsoft Photos app

Open Windows PowerShell (as Admin).
Copy/paste this command
Get-AppxPackage Microsoft.Windows.Photos | Remove-AppxPackage
Then install the latest version by searching Microsoft Store for "Microsoft Photos"

I removed a great many things and One Commander only started working when I rebooted Windows entirely.

Unfortunately I cannot report what the culprit was, but definitely reboot Windows from time to time while debugging this.

@AeliusSaionji

I removed a great many things and One Commander only started working when I rebooted Windows entirely.

Unfortunately I cannot report what the culprit was, but definitely reboot Windows from time to time while debugging this.

No worries, I am glad it worked out. Some programs require reboot to be completely removed from the system, so that was the reason most likely.

Just started happening in the last week and a half with Google's DriveFS ContextMenuHandler

DriveFS ContextMenu Handler Yes Context Menu Google Drive Extensions 89.0.2.0 Google Drive Google, Inc. No No No No No No C:\Program Files\Google\Drive File Stream\89.0.2.0\drivefsext.dll {EE15C2BD-CECB-49F8-A113-CA1BFC528F5B} 4/04/2024 7:29:10 AM 22/02/2023 8:54:22 AM No Directory\Background, *, .lnk, Directory, lnkfile A 24,873,248 No No

I 'd like to leave a note that I disabled YunShellExtContextMenu and the issue fixed. YunShellExtContextMenu is from baiduyunguanjia application.

I'd like to also add a note on a (possibly niche) possibility which turned to be true in my case. It turned out that the context menu in the Windows File Explorer was also causing a crash. This turned out due to a recent change I made in the Search and indexing settings. Something that's worth a look.

Here is what worked or me. This is cloud related problem. Downloading all cloud files did the trick, as follows:
OneDrive > Settings > Sync and Backup > Advanced Settings > Download all files

I downloaded and installed alldup today, got the crash and error message telling me to uninstall the program and install the newer version since that one doesn't have Fast Explorer. However, it was the latest version as that one doesn't use fast explorer, I did install it with the context menu option. But reinstalling the program even without that option enabled still caused the crashes (though this time onecommander didn't give me the specific message about alldup).
Indeed, I opened shellexview and Fast Explorer was there.
correction: it seems that you can install alldup then disable fast explorer, and have both programs work fine. I swapped for the portable version of alldup just to be safe though.