Windows 10 occasionally stuck on login image

[crusadehs]

Once every 10 boot or so, my windows 10 would get stuck on the picture before you press enter and input the password to login to desktop. It just doesn't respond to the enter key. I can still click on the small icons at the bottom right to go to sleep mode/ restart/shutdown or check the internet status, etc. So I had to reboot to make the problem temporarily go away. It's annoying and I don't know how to solve it. If anyone can give me an idea what it might be then that would be great, thanks!

 

[mikeymikec]

I suggest:

Run 'eventvwr' (Windows Event Viewer), go into 'custom logs' then click on 'administrative events'. Categorise the warnings and errors according to source and post your results here. You may want to double-click on some of them to see what the main body of the entry is, especially for 'service control manager' errors.

 

[crusadehs]

License Activation (slui.exe) failed with the following error code:
hr=0x803F7001
Command-line arguments:
RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=UserLogon;SessionId=1

 

[Unico]

Give this a try:

http://www.tomshardware.com/faq/id-3127574/fix-windows-error-0x803f7001.html

 

[Ketchup]

So is Windows saying it's activated?

 

[mikeymikec]

License Activation (slui.exe) failed with the following error code:
hr=0x803F7001
Command-line arguments:
RuleId=3482d82e-ca2c-4e1f-8864-da0267b484b2;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=4de7cb65-cdf1-4de9-8ae8-e3cce27b9f2c;NotificationInterval=1440;Trigger=UserLogon;SessionId=1

That was the only error or warning?

 

[BonzaiDuck]

Just popping in. Correct me if I'm wrong, but what he describes is similar to a problem I also had.

It was due to a flaky boot-time USB hand-shake. It hasn't happened for some time. I had changed the port connecting the keyboard, and I have a KVM switch which also complicates things in terms of possible causes.

And this isn't a real recommendation for a "solution," but I've begun a habit of keeping two keyboards connected to the machine, keeping the other out of site and out of mind under my desk.

If I'm right in my basic assumptions, see what happens when you pull the USB connection for the keyboard and then reconnect it at that logon screen or the gawdy screen display that precedes it.

Also and almost forgot but obvious -- if this seems to be the problem, reinstall all of your USB drivers including USB 3 and USB 3.1.

What sort of motherboard is the OP using? OP?

 

[crusadehs]

That was the only error or warning?

Yeah, during the timeframe when the sympton happened.

Just popping in. Correct me if I'm wrong, but what he describes is similar to a problem I also had.

It was due to a flaky boot-time USB hand-shake. It hasn't happened for some time. I had changed the port connecting the keyboard, and I have a KVM switch which also complicates things in terms of possible causes.

And this isn't a real recommendation for a "solution," but I've begun a habit of keeping two keyboards connected to the machine, keeping the other out of site and out of mind under my desk.

If I'm right in my basic assumptions, see what happens when you pull the USB connection for the keyboard and then reconnect it at that logon screen or the gawdy screen display that precedes it.

Also and almost forgot but obvious -- if this seems to be the problem, reinstall all of your USB drivers including USB 3 and USB 3.1.

What sort of motherboard is the OP using? OP?

MSI Z97s SLI Krait