Blank screen after pressing CTRLALTDEL for login. No way of logging in across Domain.

[burgemaster]

It appears to only affecting machines with the on-screen keyboard enabled for us. the DISM command has worked a treat.

[Bev]

My problem isn't to do with Outlook, we don't use it, but we aren't getting that far anyway.

[Bev]

and actually my affected machines are all 32bit.

[caffrey]

It borked all the office apps here, couldn't open powerpoints / publisher files etc. uninstalling the update makes them work again

[Bev]

I think there has been more than one problem update as my problems are at login.

[hallb15]

I've just had another PC with this issue appear. This time its a fujitsu E400, Win 7 Pro 64-bit. I've just brought it back to my office to try and sort it out as I couldn't access it via AB Tutor or remote into it... I'll post back when I've got more info.

[sonofsanta]

I've always deployed updates to our office & lobby first, ~10 PCs, to test for a week and a half before I deploy sitewide. After the 2015 we've had though I might start waiting a week before I even do that; this is what, the 3rd Patch Tuesday this year where they've had to yank a patch?

[burgemaster]

I think there has been more than one problem update as my problems are at login.

 

Bev this update is crashing WinLogin.UI at logon as well as causing problems with Outlook and more.

Just remove the update from WSUS and manually remove it from any machines already affected with a startup script containing:

C:\windows\system32\DISM.exe /Online /Remove-Package /PackageName:Package_for_KB3097877~31bf3856ad364e35~amd64~~6.1.1.1 /quiet

Thanks to Rob_D

[TechSupp]

Is that script just for 64bit PC's? that could be my issue (if it is whats the change for 32bit?). At moment I have removed it from WSUS, then I am going into the PC as a repait PC option, restoring to a previous time (which for some reason it says eventually it has failed to do), then allowing it to restart, when it starts it says it had a problem starting, leave alone and it then comes back as normal.

[Bev]

I've created a batch file with this code in it, and put it in my group policy to run before login. I've only tested it on one PC but it's not fixing the problem.

 

I've also got nearly every PC in the school trying to install updates, even though I set all of yesterdays updates to either decline or remove.

 

 

[caffrey]

Did a manual update on WSUS and the new revision version is there, deployed it and tested it - seems to have fixed my issues

 

(new update revokes the old, however it's still the same KB number to be more confusing!)

Edited November 12, 2015 by caffrey

[Rob_D]

@TechSupp

Try running

[color=#333333]C:\windows\system32\DISM.exe /Online /get-packages > C:\packages.txt [/color]

 

Then search for 3097877 in the generated text file to find the right Package Id.

[Bev]

I am sure I sound really ignorant, but am I running that on the server or on the affected PC? Because I can't login to the affected PC to run it.

[RTay]

Our problem was that you could not log on to Windows (even in safe mode). Just got a black screen with a cursor.

 

I ran this using a Windows 7 OS install disc (Shift+F10 to open Command Prompt):

 

dism /image:X:\ /remove-package /packagename:Package_for_KB3097877~31bf3856ad364e35~amd64~~6.1.1.1 /scratchdir:X:\temp (Note: No space after 31bf3856ad364e35 and ~amd64)

 

X is directory of Windows. Mine was on D for example.

 

I will need to install the revised KB3097877 later if they have fixed the problem.

 

May need to adjust the code for x86/32 bit machines. I had an issue with the 'temp' folder so just leaving it as X:\ worked ok.

Edited November 12, 2015 by RTay

[uke]

Thanks for the fix for 64 bit.... I am offsite at the moment, if someone does find out the 32 bit fix can they please post it here. Thank you!

[Rob_D]

You'd need to run it on an affected computer, if you haven't got any remote command tools (like psexec) then drop it into a startup script and reboot one of the computers. Even with the error you should be able to brows to "\\computername\c$" to access the local hard drive.

[simonw]

All of my pc's have downloaded and installed the update last night/this morning, but we've had zero issues.

 

Server 2012 R2, Win 7 64 & 32 bit machines.

[Bev]

THANK YOU!!! I was stuck with having the wrong package name.

 

 

For those with 32 bit machines, the command I used was

 

C:\windows\system32\DISM.exe /Online /Remove-Package /PackageName:Package_for_KB3097877~31bf3856ad364e35~x86~~6.1.1.1 /quiet

 

 

and it does appear to have worked.

 

Interestingly, someone else mentioned the on-screen keyboard, and when I have managed to get onto the first affected computer the onscreen keyboard is displayed, so I wonder if there is a connection?

[ataylor]

RDP worked for me. fortunately only 2 casualties onsite for me.

[hallb15]

I can confirm that running the command below works on a 32-bit Windows 7 PC with intel Core i3 CPU.

 

 

dism /image:X:\ /remove-package /packagename:Package_for_KB3097877~31bf3856ad364e35~x86~~6.1.1.1 /scratchdir:X:\temp

Where X is your OS drive (mine was D)

 

Note the ~x86~ above for 32-bit Windows systems.

 

I had to get to the command prompt by pressing F8 at boot to get System Recovery Options then Advanced Boot Options, Repair your computer, Command Prompt.

Edited November 12, 2015 by hallb15

[mullet_man]

Had 3 staff laptops with the issue. So hopefully that's the worst of it.

[Domo]

Wish i'd have looked up this thread before re-imaging the PC that was having trouble :/

Luckily it was only one PC out of 350 that installed it that's having issues.

:l

[TechSupp]

Maybe I'm being dim today (stop shouting out at the back!) but when I try that command for 32bit it says it does not like the tilde?

'C:\windows\system32\DISM.exe /Online /Remove-Package /PackageName:Package_for_KB3097877~31bf3856ad364e35 ~x86~~6.1.1.1 /quiet

 

Error: 87

 

DISM doesn't recognize the command-line option "~x86~~6.1.1.1".

 

Don't seem to have had anymore issues since I fixed the ones affected and declined that update in WSUS.

Edited November 12, 2015 by TechSupp

[hallb15]

Maybe I'm being dim today (stop shouting out at the back!) but when I try that command for 32bit it says it does not like the tilde?

'C:\windows\system32\DISM.exe /Online /Remove-Package /PackageName:Package_for_KB3097877~31bf3856ad364e35 ~x86~~6.1.1.1 /quiet

 

Error: 87

 

DISM doesn't recognize the command-line option "~x86~~6.1.1.1".

 

Sorry - there shouldn't be a space between the 5 and the ~

[GuyJD]

I had one this morning, was about to re-image the machine when I got a phone call from my old boss saying they were experiencing the same thing, so a quick check on here and everything is sorted.

 

Where I'd be without this community I really don't know.