Solved issue with context menu not displaying

Abierto
#792 0 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 9 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
csharp
Área
desktop

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
C#
Estrellas
15.7k
Forks
947
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Tichau/FileConverter

Todos los issues de Tichau/FileConverter

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.