Is there a way to see the exact Office 365 updates that were installed successfully on your computer?

Two answers.

One, why does Windows do it then? It is perfectly clear specifically when Windows updates were installed on your specific computer.

Two, the important one. "Something is going wrong" and it started going wrong in the last few days, so i am wondering if it is the result of an Excel update installed.

Specifically this line in a VBA macro now gives an error.

If Selection.Value = Evaluate("na()") Then

Its a macro that runs once a day and has been run once a day for like a year or more. Suddenly a few days ago it starts giving an error. The problem is not due to "Selection.Value" but it is "Evaluate("na()")" that is causing the error. Why does that error now and never did in the past.

The Windows team is correct, this information should be available to users. The Office team is negligent in not making it available to us for our Office products.

Different update situations. Windows updates affect pieces of Windows and can be rolled back individually. Office updates update the whole Office suite at once.

As regards your code, Evaluate("na()") should always have returned an error value and should always have given a type mismatch unless the cell did have an #NA! error in it.

Hi Rory,

You are referring to Feature Updates of Office365. The monthly Security Updates are NOT cumulative and they do change the version build of Office. Currently there is no way to determine which previous monthly Security Updates have already been applied. Microsoft confirmed they do not yet have a tool available for users for this info. We are using Semi-Annual Feature Updates and do apply some of the monthly Security Updates. It would be helpful to know which ones have been installed aside from just the last one.

E.

OK, thank you. You have explained it, i think the cell did have #N/A in it for a long time while the macro was running, so when that cell stopped having #N/A in it, that seems to be why it then started throwing an error.

Though this was not an error, what if an update to Office did introduce an error such that i wanted to roll it back....wouldn't it be good to know the exact update history for my machine? Sometimes updates introduce some behavior that some people may find pernicious, i think. Better to have more information than less. But, definitely thank you for your explanation.

Different update situations. Windows updates affect pieces of Windows and can be rolled back individually. Office updates update the whole Office suite at once.

As regards your code, Evaluate("na()") should always have returned an error value and should always have given a type mismatch unless the cell did have an #NA! error in it.

As far as I know, no. What would be the point, as a matter of interest?