Jump to content

Recommended Posts

Posted
The answer is yes to 1 and appears to be yes to 2 (nobody has yet said that it isn't fixed!)

 

Thanks very much - you're a star! Will go and fix a couple of machines that this happened to overnight.

 

In case anyone else has the same issues - here's the symptoms I've seen today:

 

The blank logon screen after ctrl+alt+delete DOES NOT seem to have happened.

 

Outlook 2010 was crashing on certain emails. Before I knew about the borked update, I'd assumed it was just an email with dodgy formatting or something. So I logged onto user's email via webmail and deleted said email, which stopped the outlook crashes. However, since finding out about the update and checking the machine in question, it did have the borked update installed.

 

Time to go and apply the fix!...

Posted

I have a few broken outlooks and a few black screen PCs, I've declined the update in WSUS but what should I do now for fastest network fix? set a deadline re approve the update? does wsus have to be told of the new version and how do I check...

 

cheers!

Posted
Quick WSUS question on that KB, I did a search for the KB and said to not install to stop issue, now they have deployed a fix with same KB, if I search for it again, will it find the new one or will I risk setting the old one to install again?
Posted

Had similar issues yesterday too, unplugging the Promethean Whiteboards and then retrying login worked (which gets rid of the Security Button login prompt) for me.

 

Hopefully the patch will fix it properly now though.

Posted

Had a few more workstations with the dreaded flashing screen this morning.

 

Remoting in to the affected workstations using Remote Desktop Connection and installing the revised update cures it.

  • Thanks 3
Posted
Had a few outlook issues but going into outlook /safe mode and then reverting back to normal after - seems to have fixed it
Posted
Remoting in to the affected workstations using Remote Desktop Connection and installing the revised update cures it.

 

Thanks for this idea! Was having a problem with Bitlockered laptops and the other methods weren't available.

Posted
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)

 

 

 

 

I’m trying this but I’m getting the following errors (see image). How do I fix this?

 

20151117_112725.jpg

Posted (edited)

You typed,

dism  /image:X:/  /get-packages

Which is incorrect. The correct version would be,

dism  /image:X:\  /get-packages

Notice the 'backslash' after the X:

Also, it looks like you were not typing the command as detailed above.

Type it exactly as below and then report the results.

dism  /image:X:\  /remove-package   packagename:Package_for_KB3097877~31bf3856ad364e35~amd64~~6.1.1.1  /scratchdir:%TEMP%

 

REPLACE X:\ with the drive letter that corresponds to your Windows installation. For example, it may be C:\ or D:\

Edited by mrwoberts
Posted
REPLACE X:\ with the drive letter that corresponds to your Windows installation. For example, it may be C:\ or D:\

 

You need to change the X:\ part with the correct drive that has the windows folder on it.

 

If you're not sure, then you'll need to 'check' the first few drives like this...

if  exist  "C:\windows\."  echo FOUND windows folder!

if it doesn't find it, try the next letter

if  exist  "D:\windows\."  echo FOUND windows folder!

and so on...

  • Thanks 1
Posted

That got it

 

X: was the Windows PE recovery environment. My Windows install was on D:

 

as I have 32 bit Windows on this laptop I had to change amd64 to x86 in the command I entered

Posted
We ended up with dozens of schools with this problem. Sorted very quickly by adding a new group policy with a script to uninstall the KB in startup and shutdown. Any PCs that had the problem were just warm booted and the GP did the rest.
Posted
I spent virtually all day Friday remoting into machines to perform the upgrade. What a waste of a day! On the plus side, I did learn how to edit a registry remotely to allow RDP connections on two machines that were blocking my attempts to fix them.
Posted

Dealt with this on Monday after receiving several emails on Friday saying the screens were flashing, handily I had Friday off..!

 

Initial thought was 1-2 screens capacitors could have gone (old screens here tend to do this, used to repair them before we replaced an ICT suite, now we just recirculate screens from said suite), then suspected but couldn't know for definite at the time that it could be a joyful update.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...