PC stuck at a blurry login screen

***FIX***

Initial Steps (Enter Recovery Environment):

1. Enter Recovery Environment (If you are unable to get into the recovery environment via a menu, you can turn off your system during the initial boot when the Windows logo is on the screen and the dots are circling. Do this at least twice and you'll see the message "Starting Automatic Repair").
2. Once the recovery environment loads select "See advanced repair options", then "Troubleshoot", then "Advanced options".

Method #1 (Via Command prompt - assumes basic command prompt knowledge):

1. Click "Command Prompt".
   
2. Change directory to your boot drive if necessary (for example, type c: and press <ENTER>)
   
3. Type "CD %windir%\system32\config\systemprofile\appdata\local\microsoft\windows\caches <ENTER>
4. Type "DIR <ENTER>" and make sure you are in the right path. You should see one or more .db files -- usually just cversions.3.db. If there are no files in this directory see the addendum below.
5. Type "DEL *.* <ENTER>"
6. Reboot and test
   

Method #2 (Via Safe Mode and File Explorer - may require adjusting permissions):

1. Click "Start-up Settings" and "Restart" to reboot the system and get the option to enter Safe Mode.)
   
2. At the Startup Settings screen press "4" to boot in Safe Mode.
3. Log into your administrator-level account.
4. Open File Explorer and browse to %windir%\system32\config (example: c:\windows\system32\config)
5. Gain access to systemprofile (you may be able to just double-click it to gain access)
6. Drill down to %windir%\system32\config\systemprofile\appdata\local\microsoft\windows\caches
7. Delete all files inside caches
8. Reboot and test

Addendum

Some have reported that it is necessary to clear the caches folder of the local user account also or instead of the systemprofile account. If the above procedure does not work for you, delete the file(s) in the local user cache folder (located in %localappdata%\microsoft\windows\caches) using either Safe Mode or the recovery environment command prompt.

Good luck!

Special thanks to John_E_M for first suggesting the localappdata caches folder, and to Artaeos who also narrowed down the problem to the systemprofile caches folder at the same time I did. Great job guys!

**Edited 9/6/2019 to add command prompt method, local account provision, and acknowledgements**

-Forjo