The profile_owner plugin does not exist causing update error

That Views plugin, I think, is in the contributed Profile module. Is that module's code missing?

@cilefen I had the Profile Module installed once, but I removed it a long time ago. Actually long before Drupal 10 even came out. If that's what it's looking for, why now?

It is a default_argument plugin, and the views update is processing default arguments. Could that be it? Was the module not uninstalled normally?

@cilefen I installed it, tried it for a short time, then realized it wasn't going to do what I needed. I uninstalled it using Composer like I always do. This was long before I upgraded to D10, so why would it only now be showing up? Is there a way I don't know of to check to see if the Profile Module has some "ghosts" hanging around? I can't seem to do any updates now because it won't let me get past this issue. My cron even keeps stopping.

Have you examined the database and the site’s codebase in-depth for “profile_owner”? This originates from one or the other.

Did you actually uninstall the module or did you just remove it?

No I completely uninstalled it the correct way. I just posted over in the Profile module issues to see if someone there recognizes it. It's really baffling me. I'm also going to try to run updates on a site I never used Profile in to see what happens. After I back everything up first.

@cilefen I did a db search and found "profile_owner" in these:

1 match in cache_config 	Browse 	Delete 		
2 matches in cache_data 	Browse 	Delete		
1 match in config 	Browse 	Delete
1 match in config_export 	Browse 	Delete
1 match in config_import 	Browse 	Delete
1 match in config_snapshot 	Browse 	Delete 

Export the entire site configuration and look there.

@cilefen well I just discovered that Windows 11 has a flaw. you can't search for text within files. So I guess for now I can't answer.

@cilefen I found them, in a round about way. Made a 777 folder on the server and extracted them there. Ran the grep again and found these

views.view.user_pages.yml:          default_argument_type: profile_owner
views.view.user_pages.yml:          default_argument_type: profile_owner
views.view.user_pages.yml:          default_argument_type: profile_owner

I think I fixed it. I manually deleted the DB entries that were showing, and removed the file in the /web/sites/default/files/config directory. I reran the updates, and the database updated normally. My manual cron still seems to be not working, but I'll put up with that for now. I still don't know how those entries could have been left over after all this time.