-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Console uninstall does not remove everything #225
Comments
In my previous bug report, I was told that I had a mixture of old and new installs. So I ran MikTeX console uninstall (again), deleted the MikTeX folders, (again). ran the install (again) and got the same error. So how does one remove all traces of previous installations? Windows API error 127: The specified procedure could not be found. dllName="C:\Program Files (x86)\MiKTeX 2.9\miktex/bin\MiKTeX209-core.dll" MiKTeX: 2.9 There is no C:\Program Files (x86)\MiKTeX 2.9 folder. Root3 should be C:\Program Files\MiKTeX 2.9 but I don't know how to fix it. |
You have to remove MiKTeX by hand:
You also have to delete the registry keys:
|
I ran uninstall first to see what was being removed automatically. All the folders except "C:\Program Files\MiKTeX 2.9" were already gone, and (using regedit) I couldn't find the registry keys to be deleted (or anything involving MikTeX). I got as far as HKEY_LOCAL_MACHINE\SOFTWARE\ and HKEY_CURRENT_USER\Software\. |
Using the "Find..." facility of regedit I did find three registry keys using MikTeX (under Classes). Going to try to reinstall now. |
Nope. Same error. |
I searched the registry for every pathname including MikTeX and found nothing involving Program Files (x86). |
I searched again for MiKTeX this time and found it. It still doesn't work, but is looking in the right folder now. |
I am having the same problem:
Windows API error 127: The specified procedure could not be found. dllName="C:\Program Files\MiKTeX 2.9\miktex/bin/x64\MiKTeX209-core.dll"
Diagnose-report: |
You can always just delete the " C:\Program Files\MiKTeX 2.9" folder and reinstall, but that is (probably) how I wound up with bad registry keys. BTW, I don't think they pay any attention to "Closed" reports. |
Good to know, elfsoft2000. I found some help and workarounds from issue 187: #187. For me, installing only for me and using some commands after error messages helped. |
Please note: we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide all the required information.
Checklist:
Please replace this section with the required information:
The text was updated successfully, but these errors were encountered: