The workaround to manually mount using the command line specifying the type was indeed the solution of one of the forum topics i linked at the beginning. 
I think i have seen a screenshot of a gui solutionā¦but i just didnāt find it. 
The solution was provided many times. But it got messier.
Even linux-aarhus in post #2 was sooo close to fixing the problem. It was the very module causing the issues. (I would have thought it would fallback too.)
Quite a few times information was requested. It was never provided, but sometimes a vague answer was provided basically saying, āI checked that!ā
As this became dozens of posts, nowhere I could find that they were trying to mount this outside VeraCrypt.
As this thread became more and more scattered. I even said:
But the information was there long before that comment.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.