Bash command not found

Have looked all over but can’t find an appropriate solution that actually works for this astonishingly annoying “feature.”
In bash, if I type a command that doesn’t exist, I get the expected “command not found…” HOWEVER, if I type a command for something that exists but is not installed, the command can wait for as many as 20 seconds to search all the repositories (I’m guessing) before it comes back with “command not found, but do you want to install this one instead?”
Hell no! If the command fails, it should fail. I don’t need Linux behaving like Microsoft products who think they know better than me what I want.
How can this be disabled?

Remove package PackageKit-command-not-found

Many, many thanks. Nailed it.