Phantom Drop down boxes in excel 2016

I've identified what the user is doing to trigger this bug. It occurs when there are multiple data validation list cells selected when the workbook is saved. For example: two sheets and cells with drop down lists are selected on both sheets. The combobox will not appear on the first sheet. It will appear in the selected cells in the subsequent sheets of the workbook (whether that is one sheet or several). And yes, it is a combobox, but it has no name so you cannot delete it programmatically or select it as an object.

Preventive measures: My preferred solution is to use a workbook closing (and before save event) procedure to programmatically select cells that do not contain data validation lists. This is a sustainable solution. No corrective procedures are needed.

Corrective measures: To eliminate the combobox after it appears, you can select the cell, copy it, select a new worksheet, paste the copied cell anywhere in the new sheet, then activate the original sheet, and press delete. Select the cell with the phantom combobox then run the following vba code:

Sub removeArrow()

Application.ScreenUpdating = False

ActiveWorkbook.Unprotect

Dim wsForm As Worksheet

Set wsForm = ActiveWorkbook.ActiveSheet

wsForm.Unprotect

ActiveWorkbook.Worksheets.Add

Dim wsTemp As Worksheet

Set wsTemp = ActiveWorkbook.ActiveSheet

wsForm.Select Selection.Copy

wsTemp.Select

ActiveSheet.Paste

wsForm.Select

Application.CutCopyMode = False

SendKeys "{DELETE}"

Application.DisplayAlerts = False

wsTemp.Delete

Application.DisplayAlerts = True

ActiveWorkbook.Protect Structure:=True, Windows:=False

Application.ScreenUpdating = True

End Sub

AMAZING!  I had tried everything else, and yes, this worked first time.  Thanks so much, I would have never thought of this trick on my own!

This corrects the problem. To prevent it, make sure to not have multiple validation list cells selected when saving/closing the workbook.

To be clear, are you discussing the mobile app which is the original post I created, or are you discussing a brand new thread and an error in the desktop app?

Your fix has nothing to do with the mobile app issue. The mobile app issue was repaired by Microsoft in 2016. And the mobile app does not run VBasic or macros. Also the error in the Mobile app was not caused the way you mentioned it was caused. I ought to know, I reported the error in the first place.