Macbook Pro stuck after I enter my password For last 2 days I am not able to login to my MacBook Pro. It was working fine and suddenly for no reason after I last shutdown my mac I am not able to login.
The mac starts up fine and goes to the login screen. After I enter my password the progress bar is stuck in 70%-80% and sometimes at 100%.

I tried resetting NVRAM and SCM but it didn't help.
I also tried following the steps mentioned in Justin Silver’s blog post but it also didn't help.

As mentioned in the post, I moved all the 3rd Party items from /Volumes/Macintosh\ HD/Library/Extensions to /Volumes/Macintosh\ HD/Library/ExtensionsDisabled. Since I was not able to find any *.kext in /System/Library/Extensions older than 2016, I didn't moved any *.kext from /System/Library/Extensions location.

My MBP is mid 2012 and have the latest OS X, also I have 1TB HDD and 8GB RAM.

I am not able to login using SafeMode as FileVault is enabled. I even tried login in Single User or Verbose mode but I am not able to do so.

Can anyone help me to fix this.
I found a solution for this problem by robertk1 and he writes the following:


  I would enter my password correctly and then the cursor would change to the spinning pinwheel and just sit there forever. The only way out was a power off reboot.


This is exactly what happend with my machine and it looks like it's same with yours. I hope this also works with FileVault enabled. There are two ways to solve this. With and without a guest account.

In case you do have access to the guest account follow these steps by hijoncon:


  
  Login as guest
  Open Terminal (cmd + space then search terminal)
  Enter su your_account
  Enter your password
  sudo find /private/var/folders | grep com.apple.LaunchServices | grep csstore
  Remove every .csstore your find like this sudo rm /private/var/folders/cd/someLongRandomNameHere/someFolderNumberHere/com.apple.LaunchService-whatever.csstore
  


If you don't have access to the guest account you can try different ways to get into the machine (like SSH) robertk1 suggests:


  To do this, you'll either need to be in a recovery console, or ssh
  into the machine, or boot from an external drive, or otherwise somehow
  get to a command prompt.


Once you are in the machine you can delete the files like described above in the last steps.