Brightness adjustment issues on MacBook Air M1 (13.7.4) after using a brightness control app

The real question is: why does this issue persist? I upgraded to Sequoia, and the problem was resolved. However, after switching back, the issue returned, which suggests that something on my system is retaining this behavior. Which system component stores this data, and why does the issue reappear? How can I be sure that the same thing won’t happen again on a new OS?

Why am I experiencing this on Ventura, and why should I be forced to switch to another operating system just because it seems like the only solution? I'm satisfied with Ventura and would prefer to stay on it. Let’s set the OS version aside for a moment especially since, as far as I know, Ventura is still officially supported.

I wouldn’t want to switch to a new system every time an error or issue arises. It’s strange that something like this happens at the firmware level and cannot be fixed, even after a full reset and reinstallation.

P.S. I'm honestly worried that the issue still persists and will remain in the future, especially since it didn’t exist before I used the brightness control app.

This was NOT the case before the upgrade, so it's clearly some bug that has been introduced in Ventura 13.7.4.

Hi, I see that Apple is quite indifferent to such errors. The scariest thing here is that, indeed, I didn’t have this issue until 13.7.3 or 13.7.4, however, after updating from scratch to version 13.0.0, I did not fix this error; it remained. This suggests a more serious issue that has persisted either in the driver or some firmware. I’m afraid it will happen again.

I have not upgraded to Sequoia out of worries with some older hardware I use, whose drivers might not work under Sequoia, but maybe this is the straw that will make me spend time to research the upgrade.

Since there were no responses, and I needed a solution urgently, I updated to Sonoma, and I was able to fix it. I’m not sure if this will help you. Thanks for sharing your problem, I’m glad to hear I’m not alone. Haha.

It's sad to see how silly bugs like this can always appear even when a huge company like Apple releases what should be a minor fix to other issues...

You are absolutely right, it’s sad to admit.

In fact, my problem is that after restarting the PC, this issue appears. However, after 20-30 minutes, everything works fine again. So yes, the problem can return after a restart, be careful.

But I'm glad it got resolved for you. You probably encountered this for the first time, which is why you came across this message. I've been dealing with it for about 3-4 months, maybe less, I don't remember. :))

I think there have been quite a few people like that, it's just that many updated or simply accepted it at some point. Haha.