I fixed this problem on my side by deleting the following folder: C:\ProgramData\Adobe\OperatingConfigs
I found this after coming here and finding that only shared packages caused this. On my side, we had a few technicians install shared package on computers needing named packages, but even after unsintalling shared and installing named, the error still showed. However, when installing named correctly when starting, the error wasn't there.
It had to be files added by shared and not by named that caused the issue, so I parsed the system for any Adobe related files, manually deleting them bit by bit until I found the culprit. I now remove that folder on my deployments, shared and named, and both work perfectly after.
Registered just to leave the answer on the web for other people to find.
Cheers
