Flashing Screen KB3097877

[rojinkm]

the update was for security issue on fonts, Microsoft did recommend unplug all the touch devices before you un install the update. of-course we cant remove digitizer touchscreen

 

[glricht]

Problems with Outlook, Flashing screens on touchscreens, and unable to login to domains are the primary issues with the clusterfuck patch. Stuff like this is why I'm reluctant to upgrade my business clients to Windows 10.

The problems caused by KB3097877 weren't limited to Win 10. We had a number of customers call regarding Outlook failures (including my own personal machine) using Outlook 2010 on Windows 7. Installing the re-issued update fixed every the problem.

 

[nlinecomputers]

You miss read that. KB3097877 is only for Windows 7. I was just harping on the fact that Microsoft can roll out a killer patch and if that happens on Windows 10 you are screwed because it is much harder to block patches on Windows 10.

 

[NYJimbo]

What worked for me:

Could not get into safe mode or any other mode so:

1) Boot off Windows 7 64 bit recovery disk
2) cd to windows root, in this case D:\
3) mkdir x:\temp
4) then enter this code:

dism /image:d:\ /remove-package /packagename:package_for_KB3097877~31bf3856ad364e35~amd64~~6.1.1.1 /scratchdir:X:\temp

where the "image" is the windows installed drive letter, in this case D: when booting from the recovery disk

5) after a minute or two it said it was complete then I rebooted.
6) After windows came up it immediately started some windows update, then got different login profiles to
use as expected. Picked the main one, logged in and everything looked normal.
7) about 3 minutes later windows said updates were done and it wanted to reboot so I did.
8) Windows booted up normal and everything looks fine.

Such a quick fix, I hope I get more of these.

edit: fixed line with code tags

 

[nlinecomputers]

Might need to use the CODE tags. The editor mangled your command there with a damn emoji.

 

[HCHTech]

it is much harder to block patches on Windows 10.

Yes, this is a concern. I would like to think that the pre-release testing would be ramped up to lessen the odds of a killer Win10 update, but somehow I doubt it. Some equivalent of slow-ring / fast-ring rollout would be necessary for self-preservation, I'd think.

 

[nlinecomputers]

You can delay updates on Win 10 Pro. Don't buy home buy Pro and set it to delay and then take care of the updates yourself.

 

[PaulTech]

How did this solve the blinking screen problem? Did it just go away once you had auto login setup? I've yet to try this so it's on the schedule for tomorrow. But so far I've not been able to get a cli on the native install. Only via the repair using the Dell recovery disk. One thought I had was to delete hiberfil.sys since the OS touches that file as long as it is enabled. Figured that if it's deleted then the OS will start with a tabula rasa in respect to those features. Another thing is this customer's machine is W7 Home Premium so that may be why I'm not having any luck with the commands you are using.

I apologize for the late reply. Here's what worked for me:
1. utilman trick.
2. Reboot F8 to Safemode Command Line.
3. Create new user with admin using netuser and netuser localpolicy commands.
4. Set new user to auto logon with the registry changes.
5. Reboot right into the new user. Run the wusa kb removal command and good to go.