Login screen flickers after W7 updates - tablet

jarednl3 said:

Amazing that MSFT pushes an update like this that FUBARs select systems...

Yeah normally I only manually test updates to my servers. Hopefully this isnt a pre-cursor to have to do it for workstations as well...

BG

jimthompson said:

I've now tried %SYSTEMROOT suggestion but am told "X:\windows\system32\wusa.exe is not recognised as an internal or external command, operable program or batch file". I'm not terribly technical but am mystified by reference to an X drive. Any other ideas gratefully received. A side effect of the update which i didn't previously mention is that the icon for Ease of Access now appears on login screen. I have never seen this before & don't need its functionality. Could this be significant? Mine is a touch screen.

Hi Jim, I'm not expert, but I can offer one idea... While you're in the command prompt, where you see the X: drive, it usually means you're finding yourself in temporary so called RAM disk... The idea is, that Windows will load into RAM memory just the most basic components just to be able to execute programs from this command line.

so, while you're in CMD and see X:\ , try typing in word DISKPART. diskpart is actually a program that can do stuff with partitions on your harddrives. Then type in LIST VOLUME. If you can locate in list, that just popped out, partition marked as SYSTEM, that drive letter should be the one, you're looking for. Remember it and type in EXIT. This will terminate the DISKPART program and you'll be again in X:\ directory.

Now type in the letter you have remembered with semicolon behind it , for ex. just like this D:
This should throw you in disk D:, now type in DIR.

This should list all available directories on this drive.

Navigate into windows folder by typing in CD WINDOWS
Then navigate into system32 folder again by typing in CD SYSTEM32

Now type in the command from Martin:

Code:

wusa.exe /uninstall /quiet /forcerestart /kb:3097877

Fingers crossed ;-)
kr,

Thanks for the suggestion Torchman but it didn't work.

From LIST VOLUME I identified the SYSTEM drive as the C drive, but it was shown as "System Rese".

C: worked OK, but DIR resulted in the message "Drive is system reserved" and CD WINDOWS gave "Cannot find path specified".

The Xrompt was actually X: \windows\system 32 so did DIR but no WUSA there.

Any other suggestions gratefully received. I'm getting desperate.

jimthompson said:

Thanks for the suggestion Torchman but it didn't work.

From LIST VOLUME I identified the SYSTEM drive as the C drive, but it was shown as "System Rese".

C: worked OK, but DIR resulted in the message "Drive is system reserved" and CD WINDOWS gave "Cannot find path specified".

The Xrompt was actually X: \windows\system 32 so did DIR but no WUSA there.

Any other suggestions gratefully received. I'm getting desperate.

Could you try to get into BIOS and disable things such as touch pad, touch stick, finger print sensor, webcam and other similiar devices? Because I was able to surpress the flickering by unpluging my tablet, you could try similiar approach, to basically keep only keyboard alive.

Hi, when i type wusa.... it says command is not recognized .....
and i cannot move from X:\Windows\System32 to the system volume (C:\)
anyone can help please ?

Hi there, I'm experiencing the same issue. My HP laptop downloaded the update when I went to startup earlier and immediately after finishing the update it refuses to allow me to get past the CTRL + ALT + DEL login.

I've gone to the advanced boot options page, and I select the Repair my computer option however I do not have a Windows 7 installation disk. What should I do?

i fixed my problem with KB3097877 by just let my pc turned on, with Internet connection and wait for about 1-2 hours, then it will automatically download the new update to replace the KB3097877. Then i just click shutdown and wait for a few minutes until everything is ok.

Hi guy's

Just wanted to drop a message on here saying thanks for the help.

We came across this issue Wednesday morning after our morning updates had fired, we only had 3 machines with the issue out of around 600+ we have on site, thankfully we found this thread after some GoogleFU before any more issues cropped up and we've declined it from WSUS.

I think i shall be a member of this site for a long time to come haha.

Thanks!

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.