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
    2019-09-02T04:40:16+00:00

    THIS IS NOT ONLY HAPPENING TO DELL NOTEBOOKS!

    This happened twice on my new rig (specs below). First on Friday. All I did was restart and the login promt came up as normal so I ignored the whole thing. Then it happened again last night around midnight, but this time I was stuck. Did everything I could to get the login prompt to show but nothing worked. I could only boot to safe mode by holding shift and clicking restart. Eventually did a hard shutdown from safe mode and when it restarted the login prompt suddenly showed up again... Not sure what's going on but Dell notebooks aren't the only devices affected.

    Asus Prime Z370-A II (BIOS 1201)

    Core i7-8700k 3.7 GHz

    Duke GeForce RTX 2080

    Samsung 970 EVO M.2 NVMe 1TB

    G.Skill TridentZ DDR4 3200 MHz 4 x 8GB

    Windows 10 Pro 1903 10.0.18362.295

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2019-09-01T20:42:43+00:00

    That sounds similar but it's a different issue. First of all, everyone in this thread that has this problem is on a Dell notebook. But it certainly conceivable that other machines could be affected. More importantly, the fact that these machines are able to log in successfully sounds like it's the group policy settings.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2019-09-01T04:53:44+00:00

    I have used MSCONFIG extensively, no combination works besides on of the "Safe Boot" options -- which is the same a selecting Safe Mode at boot time.

    The problem has nothing to do with hardware. I copied a hard drive from a machine with this issue into a Hyper-V virtual machine and the problem remains. I did this specifically so I could get aggressive with testing and be able to fall back to snapshots if I break something permanently (and to be able to directly edit files and protected OS files without Windows File Protection blocking me.

    NOTHING has worked so far.  I'm considering replacing LOGONUI.EXE with an older version, but all of the machines I have here have the current version. I might have one, but I am not hopeful.

    -Forjo

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-08-31T15:42:10+00:00

    We have this problem, or an extremely similar one on close to a hundred Lenovo laptops, E, L, T and X1 series. It hasn't occured on boot-up that I know of, but we have a policy that locks computers after 10 minutes of idle for security, and a lot of the time the logon prompt won't appear when they try to get back in. if they physically power down the computer they get to log-in afterwards though, started around 1903 release.

    Was this answer helpful?

    0 comments