I'm still currently trying to figure out a solution to this problem but here are some more steps I took to try to resolve it:
I tried the "Backup Identity" email to gain access to my vault. I opened the link and it opened a new window in the Avast! User Interface. I tried to use my original vault password (I created this password yesterday so I know it's the correct one), but it kept just turning the password border red. I tried variations of my original password that I could have mistakenly used (which is extremely unlikely) but got the same result.
One thing I did notice, when I used the correct original password, the window would flash information on the screen for less than a second and go right back to the password page with a red border around the password field. I was able to capture a screenshot just as the screen changed pages and saved the image posted below. It seems to be a false? authorization.

Here's the red bordered password for reference:

I was not able to access my vault with this method. It looks like it's leaning more and more towards a bug in the program vs. a user error (Whether that be remembering the correct password or an action performed).
My guesses so far on what is happening would be:
- The Master Password is getting encrypted for authorization differently, for some reason. It could even have extra data added when getting encrypted due to a bug in the code. This means when it's checked against the Master Password that's stored, it isn't the same string anymore causing a fake authorization error.
- The information isn't even getting sent to the server or is being blocked (Firewall or similar program) causing an error that won't allow authorization.
Actually, I might check to see if the data is getting sent out. Wireshark should work on testing that, if anyone wants to check for themselves with this or any network issue.
I am still able to access the vault from my mobile device so corruption on the server side / any issue on the server side is pretty much excluded from being the issue.
Hopefully I'll be able to find a solution and post it for anyone else experiencing this issue. I have a few more ideas on how to fix it from a users end but I have to look into a few things, first.