Login screen flickers after W7 updates - tablet

jimthompson said:

I've just located wusa on my D drive. If I type just "wusa" I get a separate window showing parameters ( as distinct from getting this info in the command prompt window), but if i type in wusa followed by the recommended parameter list I immediately get a return to the command prompt D:\windows\syatem32 without any apparent effect. i.e. no interval at all and no forced restart. When I restart the problem is still there.

Hi Jim, then try to type in only

Code:

wusa.exe /uninstall /kb:3097877

Thanks Torchman and others for suggestions. My problem is now resolved. I left PC switched on and S/W update downloaded a fresh update. I simply rebooted and the correction was installed. Phew!

Hi,

Just been diagnosing a very similar problem for my mother. When you picked the user icon on the login screen, the screen would go blank for a couple of seconds, then return to the user icons, without giving her a chance to enter a password. My father's computer is an almost identical spec, but did not show the problem at all. Both are desktop computers and neither have touch-screens.

I was about to post asking for help, but while reading this thread, I got a call from her to say that it's started working again!

Presumably the fix downloaded itself while the computer was idle.

Thanks for the information on this thread!

James

TorchMan said:

Code:

wusa.exe /uninstall /kb:3097877

For various people who've been trying to locate this command, if you're starting from the X: drive, I suspect that means you've booted off a recovery CD, and your "system" drive is a RAM drive.

I could be mistaken, but as far as I know this command updates the registry. As the registry it updates will be the temporary one in the RAM drive, which will cease to exist once you shut down, I don't think it's possible to fix the problem this way. You would have to boot from the copy of Windows installed on the C: (which you can't do because you can't get past the login screen).

What might work is to insert the command into the autoexec.bat file on the C: drive so it will run when the computer boots up. However, I haven't tested this.

i believe this is to do with the tablets on screen keyboard because none of my computers are touch screen but use this feature on login.

One question i have is if i roll back and then it does the updates again have Microsoft fixed the issue so that it won't just happen again?

My Asus laptop has the same problem too which has a blinking screen during the place where I suppose to insert password. I had tried to boot in safe mode, safe mode with networking and even with prompt command but it does not work. What should I do???

I read some previous post which mentioned about RDC. May I know this method is applicable to laptop also?

And for some people who solved this problem by leaving the computer idle for 1-2 hours. Is that meant you just leave it at the blinking screen for 2 hours then it will automatically install an new update???

I'm not an expert about computer and I only know very little about it. I hope someone will help me. Thanks!

Hi Harry, Broomop,

if you can't restore the system to previous System Recovery point, I would suggest to try the method just let the computer run for one or two hours and let it download and install the new revision of the update. Then restart and the fixed update should be installed. If not, try connect from another computer seating on same LAN and HomeGroup via Remote Desktop function in Windows 7.

Remote Desktop Connection (RDC) - Network
or here
How To Connect Remotely To A Windows PC From Windows 7 & Windows 8.1

jimthompson said:

Thanks Torchman and others for suggestions. My problem is now resolved. I left PC switched on and S/W update downloaded a fresh update. I simply rebooted and the correction was installed. Phew!

lostcarpark said:

Hi,

Just been diagnosing a very similar problem for my mother. When you picked the user icon on the login screen, the screen would go blank for a couple of seconds, then return to the user icons, without giving her a chance to enter a password. My father's computer is an almost identical spec, but did not show the problem at all. Both are desktop computers and neither have touch-screens.

I was about to post asking for help, but while reading this thread, I got a call from her to say that it's started working again!

Presumably the fix downloaded itself while the computer was idle.

Thanks for the information on this thread!

James

Are you guys saying that it auto updates while the computer is on idle? For some reason the "Safe Mode with command prompt" option doesn't work. It auto reboots to normal after 3 seconds in the log in screen. I can't access the repair due to the administrator password that I "forgotten". I don't have the recovery disk either. I saw your post and thought there's still hope. How do I know if i'm connected to the internet while still on the log in screen?(I assume that I need to connect to the internet to get the auto update)

Quick post about what problem I was facing and how we eventually got around it...

Problem: After the Windows 7 update I was getting stuck at login screen, same as this thread, but for some reason the 'Repair your computer' option wasn't available - even when using an install disk. I couldn't find a way to bring up the cmd to type in the suggested fix... Then when I finally could get to the cmd through install disk, it wouldn't let me use the wusa command... so here's the workaround...

Fix: Instead, to get it to work, I had to:

1) on the first install disk window, press Shift+F10 to open cmd there
2) navigate to the sys 32 file on the primary hdd with the OS I needed on it
3) copied the file 'utilman.exe' and gave it a new name so that I could put it back later, say 'utilmanorig.exe'
4) copied 'cmd.exe' and gave the copy the name 'utilman.exe' and confirmed the overwrite
5) restart computer, try booting the windows os again
6) before selecting the user you want to login: press the button at the bottom left, the 'Ease of Access' button
7) that should have opened the cmd.exe
8) now try navigating to the sys 32 file and using the
wusa /uninstall /forcerestart /kb:3097877
command
9) let it do it's thing, then it will restart and you can give logging in another try.


If that doesn't work, other things I've seen that fix:

- unplugging the LAN cable
- unplugging peripherals like graphics tablets, printers, etc (leave mouse, keyboard, and monitor plugged in)
- just using the instructions as per first post.

It seems you'll only need to use this method if you can't access the cmd through the 'Repair your computer' option.


Let me know if this helps anyone! :)

I registered for an account just to say this to the members of this forum: THANK YOU. I have been scouring the internet for days ever since the offending Windows patch was released, hoping someone with more technical savvy than I had uncovered a solution to this problem, which disabled my art tablet and completely stopped my work on a large, time-sensitive project for a client who is depending on my work for the future of his game. System repair and restore both failed-- I even bought another tablet before I realized the issue was with windows!-- but the command prompt solution to remove the update shown in the first post has got me ship shape once more. Again, thank you.