There's always potential problems with any general-purpose system, since not everything is well-written and completely tested, or has all reported bugs fixed (OS, hardware drivers, applications, etc). Since not all things are perfectly written, then not all combinations of things will work the same as each other, and a bug in one commonly used thing can cause problems within any or all of the things that use it...but since not all things use all functions of a thing, it's not always apparent which common thing to them is actually causing the problem.
Additionally, updates of any kind to any part of the system can cause cascades of problems.
Once I have a system that works and is usable for my purposes, I don't allow anything on my systems to update itself, ever, because any update could change it's behavior, and it's interactions with everything else.
One update to an otherwise perfectly working system can cause a problem that requires something else to be updated to fix that, which then causes problems with any other thing that uses it, so those have to be updated, and then all things that interact with all those things have to be updated...many things never get updates written by their creators, so then those things are just broken, and may be completely unusable. If they are required for system usefulness, then the entire thing has to be scrapped and restored back to the pre-first-update point, assuming a backup was made of that before the update happened. Rollbacks using the OS functions don't always work because it doesn't always track everything that changed, and then it's in a worse state than before.
I've wasted probably literal man-years of time fixing (or trying to, since sometimes there is NO working solution possible with available stuff) these kinds of things over my life, for myself and others.
So...no updates for me, for any working system.