Updated July 20, 2022:
We’re resuming the rollout of this change in Current Channel. Based on our review of customer feedback, we’ve made updates to both our end user and our IT admin documentation...
Updated Jul 20, 2022
Version 9.0
Blog Post
Hi,
Is there any progress on resolving the problems with Excel XLAM files reported several weeks ago?
We are getting uncomfortably close to the planned June Current Channel release.
Exact reproduction steps are available on request.
-------->
I created 2 XLAM files, both signed using my certificate.
The XLAM files are very simple – the only VBA they contain is a Workbook Open subroutine that contains a MSGBOX “Book1” or MSGBOX “Book2”. So when their VBA is enabled and they are opened the MsgBox fires.
Failure points include:
- No messages at all when opening a signed XLAM with MOTW – it silently disables
- A Trusted publisher does NOT allow a signed XLAM with MOTW to be loaded
- No view of either the yellow message bar or the red message bar
- Web page links do not mention MOTW at all
- There does not appear to be any benefit at all to signing code – the user just has to perform an extra step