PC stuck at a blurry login screen

Anonymous
2019-07-31T17:27:31+00:00

I recently updated my PC and now it is stuck at the login screen. It boots up normally to the lock screen, after pressing any button or using the mouse it goes to the next screen for the login but does not load the password box and the screen remains blurry. I can use the power, network and easy of access buttons but that is it.

Safe mode will not start, restarting 3 times does not take me to the repair screen, ctrl+alt+delete does nothing, I even tried using ctrl+F8 and nothing has worked. Anyone have any ideas on how to fix/bypass the login screen?

Windows for home | Windows 10 | Windows Hello, lock screen and sign-in

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2019-09-05T01:28:41+00:00

***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

Was this answer helpful?

100+ people found this answer helpful.
0 comments

158 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2019-09-06T12:59:47+00:00

    All of my systems have two files, the cversions.3.db and one with a {GUID No.}.3.ver0x0000000000000001.db.  There were both added the day of CU and servicing stack updates.

    KB4497932 or (servicing stack) KB4500109   cversions.3.db

    KB4505903 or (servicing stack) KB4508433  {GUID}

    I tend to discount just the blurring effect to be the problem since I have systems of all ages that had no problems and I assume your systems are no longer having the problem the blurring..

    Another observation, the {GUID} version is the same size and date as a file in the 1033 folder called StructuredQuerySchema.bin

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-09-06T16:55:16+00:00

    All of my systems have two files, the cversions.3.db and one with a {GUID No.}.3.ver0x0000000000000001.db.  There were both added the day of CU and servicing stack updates.

    KB4497932 or (servicing stack) KB4500109   cversions.3.db

    KB4505903 or (servicing stack) KB4508433  {GUID}

    I tend to discount just the blurring effect to be the problem since I have systems of all ages that had no problems and I assume your systems are no longer having the problem the blurring..

    Another observation, the {GUID} version is the same size and date as a file in the 1033 folder called StructuredQuerySchema.bin

    Note that the blurring is just a new "feature" of v1903 and can be disabled. Once disabled, the problem of the login screen not appearing remains.

    -Forjo

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2019-09-06T17:02:59+00:00

    I'm being told that the problem does have something to do with the local appdata even though I know that the systemprofile appdata is a factor. Has anyone tried this with multiple users?  I wonder if clearing the local appdata of multiple users may be required in some cases if the presence of a bad cache file in any of the locations can trigger the issue..

    Has anyone tested this or has anyone had to clear caches across multiple users in order to get the login screen to reappear? Can this issue be reproduced by deleting/moving the cache file with the GUID and leaving the cversions3.db file in the directory by itself?

    -Forjo

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-09-08T18:20:33+00:00

    This worked! I was unable to use the command prompt to correctly (I couldn't seem to navigate correctly starting from the recovery environment), but using safe mode and deleting the files worked great!

    Was this answer helpful?

    0 comments