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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-08-26T19:09:19+00:00

    Well I pulled my worksheets and the afflicted computer was last in the shop July 14th 2019. It had all windows updates installed before it went out. Whatever update it is that is causing this problem came out between July 14th and August 15th to help narrow things down. I've also had calls from two other customers with similar sounding issues but I cannot completely confirm since symptoms given over the phone are not the most reliable.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-08-26T18:58:52+00:00

    1903 is the Version number which was the version of the May 2019 update.

    18362.xxx is the OS Build number suffixed by the Cumulative Update number.

    The full build number is in Settings->System->About.

    I've done a System Restore and my OS Build is now 18362.239 (installed 29/07/2019) - but I'm still getting this problem. It would be good if we could figure out which Cumulative Update has caused the problem as my system worked ok after the initial upgrade but the problem seemed to occur sometime later.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-08-26T18:58:44+00:00

    I am surprised Doug Big company like microsoft and they can't do a quick fix . When they want to sell you something they get right back to you . Its been two weeks without my computer

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-08-26T18:43:29+00:00

    They know that. It was too convenient how this unfolded. First their tech support responses were all canned BS. Then they went dark for several hours I couldn't reach anyone. Then I was connected to this last guy who very quickly told me to download the tool etc (which is till unwinding, not sure it will work yet).  No question this is a response management, in my opinion.

    Was this answer helpful?

    0 comments