Open plumothy opened 4 years ago
Hi. It seems that this bug has been fixed in 0c5c844e1eb0e1de040ebc2646c461b5e9a5f981 . Have you tried using the latest version of Dependencies from CI?
I ever had the same issue and I solved it by adding keys below to regedit.
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\exefile\shell\View Dependencies]
[HKEY_CLASSES_ROOT\exefile\shell\View Dependencies\command]
@="D:\\Dependencies.Net\\DependenciesGui.exe \"%1\""
[HKEY_CLASSES_ROOT\exefile\shell\View Dependencies\ddeexec]
@="[open(\"%1\")]"
[HKEY_CLASSES_ROOT\dllfile\shell\View Dependencies]
[HKEY_CLASSES_ROOT\dllfile\shell\View Dependencies\command]
@="D:\\Dependencies.Net\\DependenciesGui.exe \"%1\""
[HKEY_CLASSES_ROOT\dllfile\shell\View Dependencies\ddeexec]
@="[open(\"%1\")]"
You save the excerpt to a file naming with "reg" extension and don't forget to correct the path of your DependenciesGui.exe before running the reg file. With this change, you can view dependencies of any dll or exe file from the File Explorer.
Using DependenciesGui.exe on Windows 10
In the module tree, right-click on any module with a space in the Path and select the command "View Module in separate application".
This will produce an "Invalid PE" message. For example, if the selected module Path begins with "C:\Program Files (x86)" then the error message will be "C:\Program is not present on the disk".