Solved Login screen flickers after W7 updates - tablet

[AleksPink]

I am trying this

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.

Same issue, but I cannot get into any of the safe mode options (maybe I am just not PC smart enough to do it) as it won't let me. So, hhoanganh, I will try what you did and see if it works for me too.

UPDATE: No luck with waiting for PC to download the new update. Tried 3x. I did however figure out how to get into the system recovery options and am now running a system restore (didn't even know that existed until I was forced to play around with it). Time will tell if this will fix the issue.

UPDATE 11/19/2015: Arrrrggghhh, the system restore didn't work either. It set for 5 hours, after which I had to do another force shutdown. I found Microsoft's instruction for a command prompt fix here https://support.microsoft.com/en-us/kb/3097877, but to no luck again. In command boot options, I went to 'repair my computer', chose the command prompt recovery tool, entered: dism /image:C:\ /get-packages and received ERROR: 2 (Unable to access the image. Make sure that the image path and the Windows directory for the image exists and you have Read persmission on the folder. The DISM log file can be found at X;\windows\Logs\DISM\dism.log)

I am at the end of my sanity. Can some of you smart guys and gals help me, pretty please?

 

[Fujo]

Scriptless option

If anyone is uneasy with using script, or as I was, unable to boot into safe mode with command prompt (including using a repair disk), an option that has worked on all customer's PCs so far.

Burn a Hirens Boot CD or USB and boot from that into Windows XP. There is a program called NTPWEdit, in that select the partition System 32 is on, and navigate as such. (note: with the all in ones, drive D: seems to be the most commonly used one for this)

D: -> Windows -> System32 -> config -> SAM

After selecting the SAM file and pressing OK, NTPWEdit will list all user profiles, and will allow you to select one. Select your user profile and click 'change password', but do not type anything, leave both spaces blank. Click OK, click 'save changes' and then close the program once they are saved. You may then restart your PC and bot into normal Windows.

The problem with the update seems to effect the on-screen keyboard, which is automatically called when trying to access the login screen. By not having a password any more, you bypass this.

You can then uninstall the update through the usual (non-script) GUI way, and hide it.

Unfortunately now the damage appears to be done - if you put a new password on the problem comes back! I am pretty confident this will be fixed in a later update from Windows, but for the time being, if you are that worried about your PC privacy (eg. business) you could always opt for a BIOS password instead.

 

[panjlaprateek]

Thanks, worked for me Hp touchsmart tm2

Registered a new account just to say thanks.

Key Points

• 
  Couldn't download the (repair?) iso from Microsoft's website since the product key was no longer legible on the sticker.

• The repair ISO I had created long back using Windows itself(around 220MB in size) didn't work when booted off of USB. No GUI came up. Was useless

• 
  Had lying around a USB version of "Windows 7 generic Install Disk" created back they used to be available. Got to the System Repair menu via that and then on to the command prompt. Followed the rest of the steps after that

• 
  Had a system restore point but due to some file corruption it had been aborting midway
  

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!