You can read the error message, right? I mean, it's in English and everything, and what it says isn't random gibberish. The error message definitively originates from an extension for Morrowind. It just so happens that the base Vortex comes bundled with a Morrowind extension, just in case people might want to use it for handling Morrowind.
Yeah, and since I DO NOT HAVE MORROWIND INSTALLED (nor any mod for it) what are we going to make out of this error? More evidence that the Vortex client is incredibly awesome and I'm the one at fault?
Also, I'm not sure where did you get this delusional idea that I didn't manage to set up the Vortex correctly in the past, when I even told you that I used it in December.
I'm just telling you I never liked it.
The fact that my first attempt to launch it again after few months resulted in the software spazzing out and making up absurd error messages just goes to add to the hilarity.
I'm getting that "delusional idea" that your Vortex has somehow been mismanaged because you're complaining about a Vortex error that nobody else seems to be having. And I hesitate to ask, but why do you feel the error message is absurd? It's a pretty standard error message, as those things go. Rather more informative than your typical Windows error messages.
Vortex comes bundled with support for managing mods for quite a number of games. This support is created through extensions. The error tells you that an update for one of these failed. It isn't saying you have mods for Morrowind. It isn't saying you have plug-ins for Morrowind. It is saying that the extension used for handling Morrowind, which is a bundled default part of Vortex, failed to update. This is completely non-critical in and of itself, since you're not using that functionality anyway.
But the fact that you are getting that error is odd and should probably be investigated. It indicates something in the interaction between your system and this particular software application is off, and since it works everywhere else, the problem is likely a local one. And if something on your system is borking this update then it isn't inconceivable that it could bork other updates in other applications.