I seem to remember at least one case where a manufacturer attempted to patch an issue like this and managed to actually introduce another one in its place.