PC stuck at a blurry login screen

Anonymous

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?

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

***FIX***

Initial Steps (Enter Recovery Environment):

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").
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):

Click "Command Prompt".
Change directory to your boot drive if necessary (for example, type c: and press <ENTER>)
Type "CD %windir%\system32\config\systemprofile\appdata\local\microsoft\windows\caches <ENTER>
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.
Type "DEL *.* <ENTER>"
Reboot and test

Method #2 (Via Safe Mode and File Explorer - may require adjusting permissions):

Click "Start-up Settings" and "Restart" to reboot the system and get the option to enter Safe Mode.)
At the Startup Settings screen press "4" to boot in Safe Mode.
Log into your administrator-level account.
Open File Explorer and browse to**%windir%\system32\config** (example: c:\windows\system32\config)
Gain access to systemprofile (you may be able to just double-click it to gain access)
Drill down to**%windir%\system32\config\systemprofile\appdata\local\microsoft\windows\caches**
Delete all files inside caches
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

0 comments

158 additional answers

Anonymous

2019-08-31T13:18:44+00:00

Has someone tried using the diagnostic boot option you can set up in msconfig.exe? If you can get into normal Windows with only the Microsoft utilities running then you could do updates possibly.. or troubleshoot for a problematic component..

Msconfig.exe also has an option for using basic video..

I haven't noticed anything that might be in common with the machines. Such as the folks having problems with IIS during build upgrades all seemed to be Legacy systems. Folks having problems with WinMount were systems running Macrium Reflect and that only showed up during Build upgrades.

When I tried to run a downloaded update from Safe Mode, I did get an error message that the installer would not run in Safe Mode.
Was this answer helpful?

0 comments No comments
Anonymous

2019-08-31T05:42:44+00:00

You can do an in-place upgrade; if by that you mean reinstalling Windows (what I call an overlay). The new terminology work Windows 10 still loses me.That's how I fixed three machines with this problem so far. You just have to start it from the windows recovery environment.

I tried creating another user profile and disabling the password requirement. It was no help.

I'm also still suspicious of whatever logonUI.exe is interacting with because that's the actual process that hangs until we get kicked back to the user select screen.
Was this answer helpful?

0 comments No comments
Anonymous

2019-08-31T02:30:08+00:00

FYI - creating a new user doesn't work either. In fact, the new user doesn't even fully function -- Start doesn't work for example.

-Forjo
Was this answer helpful?

0 comments No comments
Anonymous

2019-08-30T23:28:11+00:00

Microsoft has been releasing CUs for quite a while on Thursdays and Friday, as today. Sometimes they are the seeker version where you have to manually check for updates before you see them. The one today had a message that it was an optional update and asked if you wanted to download and install.

I thought you could install updates while in Safe Mode, but I will test shortly. You cannot do an in-place upgrade because it has to be started from Windows.

The comment about the LongoUI.exe got my attention and I saw a YouTube video where the lock screen just blinked on and off but the Logon prompt never came up.

I suppose a profile problem might be involved. Possibly adding a new user. What if the problem is not actually related to the burred lock screen.. I think folks said they turned that off and still had the problem.

I am going to get my XPS 13 9365 out and start reinstalling the Dell utilities to see if I can make the problem appear. Just in case, I have never run any of the Command type Dell utilities that are optional, just in case the problem systems are running those.
Was this answer helpful?

0 comments No comments