Login screen flickers after W7 updates - tablet

As I said yesterday, the script worked perfectly... but then this morning, I tried to log in, and the same thing happened again... Am I going to have to do this EVERY DAY until they get this squared away?

In searching more about this issue, most system admins confirm that the logon problems mainly affect systems with touch screens enabled. If you can disable touchscreens via bios or unplug usb powered touchscreens, you may be able to log on and uninstall kb3097877. In our environment, 40 of our HP 9100 w7 x86 have touchscreens. All were affected. Our 45 or so misc. Dell boxes with win7 x64 were unaffected as far as we can tell. We run outlook 2007, which hasn't yet crashed, but I'll keep you updated if things change.

I suggest either disabling your touchscreen (if possible) or use system restore to go back to an earlier date. As for my environment, I modified the group policy of the affected machines using server 2008r2 group policy management, opened the required ports, tunneled to the pc using psexec.exe and uninstalled using the script described above. Don't try to call windows about the issue. I was on the phone for 20 minutes last night, pleading with them to pass along feedback that kb3097877 was buggy. All they kept repeating to me (in very broken english) was to restart the computer. Incompetent!

According to many news sources, kb3097877 has been re-issued with the bugs removed. I may test it on a few machines to confirm. Good luck!

Jared: Yes, your computers will try to re-install KB3097877 if your settings allow windows update to download and install updates everyday. To skirt this, we "hid" the update. You'll need administrator privileges to do this if UAC is active.

From Control Panel\System and Security\Windows Update, click on the "important update is available" link, right click on kb3097877 and hide it. Next day, problem solved.

Again, Microsoft re-issued kb3097877, so this may be a moot point.

jarednl3 said:

As I said yesterday, the script worked perfectly... but then this morning, I tried to log in, and the same thing happened again... Am I going to have to do this EVERY DAY until they get this squared away?

Thank you.

Interestingly, this is not a machine that has ever had a touch screen device. It is a 5 year old desktop.

I have tried the "wusa" command but am told it's not recognised as an internal or external command. I am in UK. Does the USA part of command imply only available in USA? I've also tried restoring to several previous restore points but in every case it teaches the "Restoring files " screen an didn't finish. Any suggestions great fully received

Hmm, perhaps I've jumped to conclusions. I heard chatter that touch screen PCs were affected, and all of ours were, but maybe it was a coincidence. If you learn anything else about this fiasco, please let me know! I'd love finish this little project and move on to the things that actually contribute to revenue today.

in command prompt as administrator, try to copy and paste this: %SYSTEMROOT%\system32\wusa.exe /uninstall /quiet /forcerestart /kb:3097877

Are you logging on through a terminal? I haven't tried to use the pre-boot cmd prompt.

jimthompson said:

I have tried the "wusa" command but am told it's not recognised as an internal or external command. I am in UK. Does the USA part of command imply only available in USA? I've also tried restoring to several previous restore points but in every case it teaches the "Restoring files " screen an didn't finish. Any suggestions great fully received

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.

I can confirm that the only 3 computers with touch screens, out of the 50 total in our offices, have all been affected by this update since yesterday.
Same result, flashing on the Win 7 log in screen, after update has been applied and OS is restarted. Booting in Safe Mode did not work.

It seems as though CLASSPNP.SYS was affected some how, because that is where the boot up seemed to hang, when debugging.



I took a different approach to fix the issue (this assumes you have system restore enabled):

1. Boot from Win 7 USB key.
2. Did a system restore and rolled back the OS, previous to the update.
3. Restart and let the restore roll back.
4. Blocked the update from re-installing.

All 3 machines are back in working condition.


Brad

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