Complete un-install of KM?

KM is misbehaving badly. I did an uninstall. Downloaded and installed the new version. The problem is still there.

That was because the uninstall was not complete, obvious because I did not need to tell it who I was after the new install.

How can I achieve a complete uninstall?

In theory, all that you need to do is detailed in the manual/Wiki.

There are ways to check for any related files that might be left behind by any uninstalled application (perhaps including the registered user information that you mention) but you should not have to worry about that if you just want to install the latest version of KM.

When I first started using Computers back in 1972, standard advice to any query was RTFM!

I guess I will have to get it into my 80-year-old brain that the first step in any Keyboard Maestro query is RTFW!

Thanks for your help.

Jim

1 Like

Someday the acronym may change to CWAI because that could stand for "Check With AI" and that might even work if there is no manual.

2 Likes

A pleasure. Do get back to us all if you still have problems. I have always found KM to be very well behaved but of course macros can be naughty sometimes!

If something is behaving oddly, that typically means you have a misconfigured macro.

Use the Interactive Help, Something unexpected is happening, and follow the instructions to resolve the issue. No need to uninstall anything.

Uninstalling and reinstalling Keyboard Maestro will virtually never accomplish anything that can’t be better accomplished in other ways.

If a macro is misbehaving, adjusting the macro is the solution, not deleting all your macros.

On odd occasions (usually related to Apple’s buggy security systems), reinstalling the Keyboard Maestro application may be useful.

But since Keyboard Maestro does not “install” anything, uninstalling and reinstalling Keyboard Maestro is not generally the right way to go.

2 Likes

Something like this happened to me when I opened Keyboard Maestro. It froze and slowed down, so the only way to fix it was to right-click and delete the offending macro. After closing and reopening the app, the problem was solved.

Unlikely – it’s well established now that LLMs don’t ( and can’t ) form knowledge.

“Do you remember LLMs” may well be more frequently heard.