Microsoft Update Excel 2013 (KB3085502) 32-Bit Edition causing issues in Excel

We are seeing strange results in Excel after the Sept 8, 2015 "Security Update for Microsoft Excel 2013 (KB3085502) 32-Bit Edition" update.  When a vba macro changes the sheet, the formula bar does not change to the cell on the new sheet and it gets locked up.  Then changing something in the formula bar changes the cell on a different sheet.  There is a disconnect between the formula bar and cells.  Uninstalling the update fixes every computer that we use. 

This Microsoft update is causing problems that Microsoft needs to address.

 

Question Info


Last updated September 24, 2018 Views 781 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

We have similar issues with VSTO code after this update. When we navigate to a worksheet by calling the VSTO code Globals.Sheet1.Activate(); ,it Locks the cell which we had set as unlocked originally and worksheet protection method does not allow to edit those cells in the workbook.

 

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

We have an additional issue with reports that have freeze panes on it.  The view of the report gets messed up.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

We are also experiencing strange issues with our Excel models after installation of KB3085502.  

This appears to occur on any worksheet that has been selected by VBA code.

  • Certain cells appear locked and prevent data entry although they've been marked as unlocked.
  • Certain cells will allow data entry, but when these cells lose focus, the original value persists.
  • Certain sheets that utilize freeze panes are not scrolling properly.  Part of the frozen region is not painted correctly and is getting overwritten by content below.

If I manually select the affected worksheet, I do not experience the issues indicated above.  It seems like the UI and the underlying data structures are not synchronized.

Uninstalling KB3085502 seems to cure these issues.

Any other users reporting these types of issues?  Is Microsoft aware of this issue and is a fix being prepared?

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

KB3085502 causes the workbooks opened by my Excel add-in to not be really "active". E.g. if I close the workbook right after my add-in opened it, Excel will close the workbook behind it. Once I uninstall KB3085502 the correct workbook closes.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

We are having the same issue with Excel 2013 after installing KB3085502.  Our situation is a sheet with frozen rows, conditional formatting and a VBA macro that unhides another sheet once a cell is changed.  In this situation, the frozen rows become out of alignment, certain cells appear locked and prevent data entry although they've been marked as unlocked, and certain cells will allow data entry, but when these cells lose focus, the original value persists.  It seems in some cases, the keystrokes are being captured on the sheet which was unhidden via the macro described above, even though that sheet does not have the focus.  Manually changing to a different sheet, then back to the original sheet will fix the problem for a while, at least until certain cells are changed.

Application.ScreenUpdating = True, forcing full recalculation/rebuild of the dependency tree, recompiling the VBA code and a host of other programmatic workarounds do not seem to help.

Uninstalling KB3085502 is the only way we've found to fix the problem.  But this is only a short term solution, we need Microsoft to fix the problem.  What is the process for raising a support issue with Microsoft?

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Did you try enabling that registry key ReplaceCFOnPaste in HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Excel\Options   ?

https://support.microsoft.com/en-us/kb/3085502#bookmark-reg

When you copy and paste cells that have conditional formatting set in Excel 2013, the conditional formatting rules are duplicated even though the rules already exist in the cells.

Note After you apply the update, you need to follow the instructions in the "Registry information" section to fix this issue.

Registry information Important Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it,back up the registry for restoration in case problems occur.

  1. Exit all Microsoft Office applications.
  2. Start Registry Editor:
    • In Windows 10, go to Start, enter regedit in the Search Windowsbox, and then select regedit.exe in the search results.
    • In Windows 8 or Windows 8.1, move your mouse to the upper-right corner, go to Search, enter regedit in the search text box, and then select regedit.exe in the search results.
    • In Windows 7, go to Start, enter regedit in the Search programs and files text box, and then select regedit.exe in the search results.
  3. Locate and then select the following registry entry:
    HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Excel\Options
  4. On the Edit menu, point to New, and then select DWORD Value.
  5. Enter ReplaceCFOnPaste, and then press the Enter key.
  6. In the Details pane, right-click ReplaceCFOnPaste, and then select Modify.
  7. In the Value data box, enter 1, and then select OK.
  8. Exit Registry Editor.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Yes I tried that.  Then rebooted, confirmed the registry setting was still there and the problem persisted.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

We have discovered, subsequent to my original post, that all reported issues stem from the use of the Range.NumberFormat method.

If number formatting is applied (via VBA) in our model, then issues begin to arise.  If number formatting is never called, the model seems to behave as expected.

KB3085502 notes indicate, "Some object model calls (Range::HasArray, Range:HasFormula and Range::NumberFormat) are slower in Excel 2013 compared to earlier versions of Excel."

I hope that Microsoft can take another look at their code and provide a resolution as quickly as possible.  This same KB seems to have been released with Office 365 and is more challenging to roll back from an administrative standpoint.

I also see this topic being discussed here.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I am not calling Range.NumberFormat, HasArray or HasFormula via the cell change event code, but I do have UDFs (on the sheet with problems) that use the HasFormula property.  Given that there was specific mention of these properties, I suspect you are right, that it has something to do with these.  Then again, I also have conditional formatting which seems to have been part of the "fix" also.  Regardless, we badly need Microsoft to weigh in with a solution or at least acknowledge that somebody is seeing this/working on it.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thanks to TW881 for letting me know about this thread.

I've facing issues too, as described in another thread:

http://answers.microsoft.com/en-us/office/forum/office_2013_release-excel/copy-and-paste-bug-after-update-kb3085502/d135aec8-d702-4f94-90e1-0f635fc04856

Apparently, getting the range.NumberFormat causes this issue. My add-in code has an if statement which checks the NumberFormat of some range, if it is not General, then set it to General.

If I comment out the if statement, the copy and paste operation works fine again!

And the KB3085502 includes the following fix:

  • Some object model calls (Range::HasArray, Range:HasFormula and Range::NumberFormat) are slower in Excel 2013 compared to earlier versions of Excel.

This means that a simple line like "var numFormat = range.NumberFormat;" will cause the issues that I'm seeing. I've also tested for HasArray and HasFormula, and I'm also able to reproduce the issues.

Is there any way we can escalate this to Microsoft?

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.