excel update KB3191907

Topic

New Reply

Anyone having issues with KB3191907?

I have encountered issues after installing excel update KB3191907 on 8/24/17.

It is causing Intel Graphics 530 to have display errors and event 7026 errors (The following boot-start or system-start driver(s) failed to load: cdrom)
At first I thought it was the display drivers and updated them.  No errors since the video driver update on the display issue.  However, the event 7026 started after installing the patch and has occurred 3 times now as of 09/04/17.

Edit to remove HTML.
Please convert to text (.txt) before copy/paste

Reply | Quote

Replies

Simplest solution is to use a restore point before your download.

I show two updates for this security update and others. Windows 7 64x and 32x, 2010 Office Professional 64x only. But interchange with 2013 & 2016 Office products.

You are stuck – just get out! Use the Restore Point, it is simple.

Reply | Quote

This KB3191907 displays as a Security update show it installed twice on 7/29/2017. VAIO laptop seems to run fine.

Windows 7 64x Home Edition, Office Professional and use OneDrive.

Reply | Quote

Does uninstalling KB3191907 solve the problem?

Reply | Quote

Woody, so far uninstalling KB3191907 has fixed the issues.  I will know for sure on the 9th since the DVD drive errors were occurring approx. 5 days apart. System has never had either of these errors prior to installation of KB3191907.  I will post back after the 9th to confirm.

My config is:

Asus Z170Pro, Intel 6100 3.7GHz CPU, 16GB Corsair Ram, Win7 Pro 64bit, Office Pro 2010 running in 32bit mode.

All Office 2010 updates except KB2956078 and Excel KB3191907 have been installed.

Reply | Quote

Woody, the issue with KB3191907 has not happened since uninstalling the update on 9/4/17.  There appears to be a definite problem with this update at least in my case.  My system was built in October 2016 and  has never had the 7026 event errors and the problem has cleared up after uninstalling the KB3191907 patch.  Also, this really does not show up unless you check the event log or use the CD/DVD drive when the issue occurs.  Hope this information will help someone.

Reply | Quote