Solved issue with context menu not displaying

Aperta
#792 0 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 9 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
30/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
csharp
Ambito
desktop

Direzione di ricerca

This is a user-reported diagnosis rather than an actionable task: a bad %LOCALAPPDATA%\FileConverter\Settings.user.xml apparently suppresses the Explorer context menu even though COM registration is fine. Start by reproducing with the attached Settings.user.xml, then read the shell extension initialization code (FileConverterExtension) to find how user settings are parsed and what happens on malformed values. Done means identifying the corrupting field and adding validation or a safe fallback.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

I ran into what appears to be the same or a closely related issue to #554 on Windows 10 with File Converter 2.2.0.

The File Converter context menu disappeared completely.

Troubleshooting performed

I initially suspected the shell extension registration, but after troubleshooting:

  • FileConverterExtension was enabled in ShellExView (Disabled = No)
  • CLSID {AF9B72B5-F4E4-44B0-A3D9-B55B748EFE90} was correctly registered in the 64-bit registry
  • HKCR\*\shellex\ContextMenuHandlers\FileConverterExtension correctly referenced that CLSID
  • The extension was not present in either Shell Extensions\Blocked location
  • EnforceShellExtensionSecurity was not enabled
  • The COM class could successfully be instantiated from 64-bit PowerShell
  • FileConverter.exe version was 2.2.0.0
  • FileConverterExtension.dll version was 1.2.1.0

What fixed it

Renaming:

%LOCALAPPDATA%\FileConverter\Settings.user.xml

to:

Settings.user.xml.BACKUP

and then restarting Windows Explorer immediately restored the File Converter context menu.

So in my case, the shell extension and registry registration were fine. Something in Settings.user.xml was causing the extension not to expose the context menu.

Misleading ShellExView path

One potentially confusing symptom was that ShellExView displayed the extension path as:

C:\WINDOWS\system32\C:/Program Files/File Converter/FileConverterExtension.DLL

However, the actual registry CodeBase value was:

file:///C:/Program Files/File Converter/FileConverterExtension.DLL

which appears to be a valid .NET/RegAsm file URI.

So the malformed-looking ShellExView path turned out to be a red herring.

Possible implication

A repair or reinstall may not solve this issue if the existing:

%LOCALAPPDATA%\FileConverter\Settings.user.xml

is preserved.

Removing or renaming that file caused the context menu to return immediately.

I still have the old Settings.user.xml.BACKUP file and can provide it if that would help reproduce the issue.

Settings.user.xml

Lingua principale
C#
Stelle
15.7k
Fork
947
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Tichau/FileConverter

Tutte le issue di Tichau/FileConverter

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.