[ms office - 2013] Office 2013 32-bit - Applications running slow

[CHiLL]

We had this issue with Excel 2013 32-bit on Windows 8.1 x64 machines. A user would be editing a workbook and all of a sudden it would lock up or take a second to switch between cells. Looking at Task Manager, Excel was taking up ~70% of the CPU whilst it was locking up.

 

I was able to replicate the issue and then we traced the problem back to a Windows Update (KB3114717 to be specific). Once KB3114717 was removed, the issue stopped and I was no longer able to replicate the issue.

 

We have now 'Approved the update for removal' on WSUS. Hopefully that will also remove the update from the client workstations it's already been installed on. 

 

Just thought I'd let you guys know!

 

There's a thread about it on Spiceworks too. https://community.spiceworks.com/topic/1437852-ms-word-2013-slowness-ms-update-issue

Edited February 12, 2016 by CHiLL

[Arthur]

We had the same issue with Word 2013 today. It was almost impossible to type anything since the program was so slow.

 

Apparently Office 2016 and 64-bit editions of Office 2013 are unaffected...

 

https://social.technet.microsoft.com/Forums/en-US/f7f85abf-aebf-4137-a429-13e3faf81635/word-2013-problems-with-kb3114717?forum=officeitpro

[3s-gtech]

This is why we hold all updates other than some security (Defender etc) for a month before deploying. I know that's not ideal, especially vs newly discovered flaws, but MS are our worst enemies at present. I have canned quite a few updates in the last year.

[castlesmith]

I had the problem today I had to delete the template doc out of appdata folder to get it working.

[m25man]

Another Botched Windows Update: KB3114717 Breaks Down Word 2013

 

I've had two users reporting that they are unable to print anything from Office 2013 and one reporting Outlook Crashing and locking up when trying to open a Word Attachment this morning.

I'm having to System Restore on one device and a manual uninstall on the others to see if its related.

[gshaw]

Yup we have the same, removing the update resolves the issue.

 

As per the above article it seems to have been pulled from WSUS; I can still search for it but shows up as Unapproved despite our auto-approval rules for Critical patches.

Edited February 18, 2016 by gshaw

[mullet_man]

This explains why I've had a few staff having big issues with Word 2013 over the last week or so. I couldn't put my finger on what the issue was. It was making Word totally unresponsive and using over 50% CPU.

 

Will remove the borked patch tomorrow and see if it helps for those who've complained.

 

Glad I found this now.

[Heisenberg]

wusa /uninstall /kb:3114717 /norestart /log

 

Put that in a batch file and add to shutdown script in GPO

Edited February 25, 2016 by Heisenberg

[Heisenberg]

Actually... what am I missing here! Trying to uninstall the KB with wusa and it's saying it's not installed! - It clearly is!

 

[bigjb]

Have a look at the script on here https://community.spiceworks.com/topic/1445459-how-do-we-remotely-mass-uninstall-kb3114717 - worked for us.

[Heisenberg]

Have a look at the script on here https://community.spiceworks.com/topic/1445459-how-do-we-remotely-mass-uninstall-kb3114717 - worked for us.

 

Thought I'd fixed this with a script too.. then turned out it was still on quite a few machines!

 

I'm running the script on startup from the machines OU - Should this be a user script instead?

[fiza]

Yup we have the same, removing the update resolves the issue.

 

As per the above article it seems to have been pulled from WSUS; I can still search for it but shows up as Unapproved despite our auto-approval rules for Critical patches.

 

We are experiencing the issues now. I have checked on WSUS and it is shown as unapproved now although it was previously installed as part of the critical updates auto-approval. I cant now approve for removal so how do you get it removed from 400 machines?

[CHiLL]

We are experiencing the issues now. I have checked on WSUS and it is shown as unapproved now although it was previously installed as part of the critical updates auto-approval. I cant now approve for removal so how do you get it removed from 400 machines?

When you select the update in WSUS, do you see 'Approve' in the right hand windows under 'Update'? Our update was pushed out the same way as yours, unapproved, but automatically approved as a critical update and we were able to do it this way.

[fiza]

Thanks. Just selected it for removal even though it appears as unapproved.