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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-02-24T15:04:57+00:00

    Hi SamComputerGuy,

    If you can elaborate the process via RDP. All the affected systems in domain environment and using DHCP. I faced this issue in Win 7 and 10 systems. TIA :)

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-02-24T15:01:16+00:00

    Hi ForjoAtinxan,

    I am facing this issue in almost 8-9 systems which are in a domain environment. Does it related to AD as well somehow. Today, I have tried the steps but no luck :(

    Appreciate your help :) TIA

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-02-08T11:08:53+00:00

    Forjo, I removed all .db files from that location and similar local user accounts without success. It appears something is copying them back in on each boot.

    Any advice would be much appreciated. I'm pulling my hair out!

    Regards,

    Tim GJ

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-02-03T23:37:39+00:00

    I got what I consider a short-cut fix for those that know how to use RDP. Of course all credit goes to Forjo and the people he credited.

    I found if you can get into the computer by RDP the screen will look fine for you. Once in, all you need to do is skip the "Initial Steps" and jump right into Method #1, then Method #2 and then the Addendum. This allows you to work with the GUI quickly. I did all three steps and then rebooted. Worked great!

    And when I say great, I mean after 8 hours of working on this darn thing, then I read the fix by Forjo and got it finished in a few minutes.

    Thanks so much, Forjo!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments