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-08-26T00:22:37+00:00

    John, had to buy a new computer today to replace the one taken down by 1903 update.  It was too critical of a machine and no longer stable as I described in my post.  How may I request reimbursement for the replacement since it was clearly the result of 1903 update?  I realize the week I lost in time trying to repair can't be reimbursed but hopefully Microsoft can find a way to reimburse for the new computer.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-08-26T00:31:31+00:00

    Sorry but I'm almost positive that the terms of service and/or license agreement for Windows means that they're not liable for any down time unless you have a regular service contract with them. 

    This is not the easiest problem to explain to a customer let me tell you. I just got off the phone with them and I can't even tell them if a clean install on a new drive is going to fix this in the long run until the patch comes out. You could clean install windows on your machine you just replaced and postpone windows updates until a fix comes out. The amount of people that found their way here to this thread with the exact same problem they're going to fix it It just might not be the highest thing on their priorities list.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-08-26T08:26:42+00:00

    Same problem - older Dell desktop. The question is, will MS release a fix, or have they bricked our systems?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-08-26T12:59:57+00:00

    Same problem you shadow You must have an Inspiron 3252 as well. The computer is less then 2 yrs old this should not happen. Their updates should have not created this and they should fix .

    Guess we will have to get another computer  I'm worried if we repair same thing is going to happen 

    Rob M

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments