Lumetri color not updating changes in real time

On some PCs, the latest major Windows update has disabled the on-board iGPU. Severely affecting performance.

And the fix is users going into the motherboard BIOS settings to turn it back on. That nay be an issue for some.

I just want to update again. It's not fixed. I reverted back to version 25.0. It's incredebly slow when I use 25.1. When I use any slider it will take literally 5 to 10 seconds for it to update the change or it won't even change at all. Version 25.0 is instant when adjusting sliders. Guess I'll also be waiting for the update after 25.2 or whatever update they come up with next. I updated my graphic driver which I always do all the time and my regular computer updates still nothing with 25.1. 

Yes that's exactly what happens in my case but resetting the preferences didn't fix it.

I fixed it! Just had to reset preferences. Open up premiere pro again and hold shift+alt. 

It's on the Updates Page.

There's an option in the Creative Cloud desktop to auto-update or not, it must have been checked at one put. Uncheck it if you don't want that.

I've just noticed it now. My premiere pro auto updated today. Same thing is happening to me. I have to let go of the click before it updates the edit. Very strange.

When you say not 'starting at all' do you mean if you dbl-click a project, or from the actual icon?

Ryzen 3960x/128GB of RAM, 2080Ti, and no lag on using Lumetri controls with either the control panel (Tangent Elements) ... mouse ... or Wacom pen.

Can't replicate. In either the public 25.1 or the public beta.

Btw ... you can have the beta and shipping both installed, it's not one or the other like with Resolve.

I am talking about the exposure, highlights, shadows, whites, blacks sliders. This only happens if I update to version 25.1, I don't install the beta versions anymore since it happened to brake Premiere Pro from starting at all recently after an update (about a month ago I don't remember exactly). If it works as expected for you then it might be some bug taking into consideration how many hardware configurations there can be. I will wait for the next update and see if that fixes it.