This section primarily describes problems resulting from Microsoft Office updates that introduce bugs or other changes that break Macabacus (or Macabacus Lite) functionality, and does not include problems with Macabacus add-ins themselves, which we fix promptly upon discovery when possible.
VSTO add-ins denied access to Office DLLs and will not load
This is an Office bug
This is a critical Microsoft Office bug; not a problem with Macabacus. This bug affects most or all VSTO add-ins, not just Macabacus. See interim solutions proposed below. If a workaround was possible and practical, we would have implemented it. Please contact Microsoft for assistance with this issue, as all guidance we have is provided below.
If you are experiencing this problem with a new computer, then the OEM preinstalled a buggy Office version contrary to Microsoft guidance. The OEM delivered a defective computer with a fatal flaw, and you should return the computer for a refund.
An Office or Windows bug introduced in or around March 2019 strips user permissions from Office DLLs used by VSTO add-ins like Macabacus. Consequently, when VSTO add-ins load and attempt to access these DLLs, access is denied and loading is aborted. The only way to detect this condition is by setting the environment variables as described in step 10 of this troubleshooting guide and observing the resulting error.
This problem affects only some computers / Office installations, and seems to occur most commonly in new computers running Windows 10 and Microsoft 365, Office 2016, and Office 2019. The impact is widespread, with add-ins from many vendors affected. There are posts in several online forums on this topic, including this Microsoft forum.
We reported this issue to Microsoft in April 2019 and have been working with them since to identify the root cause of the problem. This issue is a priority for Microsoft, which has several teams involved in researching this matter. The unique nature of this problem and inability to reproduce it on demand has made troubleshooting difficult and inconclusive.
Microsoft is currently working directly with Macabacus customers to troubleshoot and resolve this issue. If you observe an "access denied" error in step 10 of of the troubleshooting guide, we will arrange a troubleshooting session with Microsoft.
Update — On November 5, 2019 Microsoft informed us that they may have identified Office as the root cause of the problem, and they are now refocusing their efforts accordingly.
Update — On November 20, 2019 Microsoft confirmed that they have identified the root cause of the problem, and are working toward releasing a fix for Office. At this time, the fix is not expected earlier than the January 2020 Office update.
Update — On November 21, 2019 Microsoft asked that we direct customers affected by this problem to uninstall and reinstall Office as a temporary workaround to restore the DLL permissions until a permanent fix is released. Microsoft is no longer working directly with Macabacus customers to troubleshoot / fix this problem. We do not have any additional guidance to offer at this time.
Update — On January 7, 2020 Microsoft informed us that the Centennial version of Office that ships / shipped with new PCs is at the root of the problem. Microsoft guided PC manufacturers ("OEMs") to discontinue shipping Centennial Office with new PCs, but this practice nonetheless continued into 2019. Centennial Office updates automatically from the Windows Store, and when it does, permissions are corrupted as described above. While uninstalling and reinstalling Office will temporarily resolve the problem, uninstalling Office does not completely remove Centennial Office, and when the remaining Centennial Office files are again updated from the Windows Store, permissions will again become corrupted. Temporarily disabling automatic updates from the Windows Store—if that is even possible—until a permanent fix is released would theoretically offer a more permanent remedy, but potentially affect updates of other installed software was well.
Microsoft continues to work on developing a fix for this problem, but it no longer appears that this fix can be implemented via an Office / Windows update, instead requiring a more manual effort given the problem's complexity and scope. Fortunately, OEMs should no longer be shipping Centennial Office preinstalled, so this problem's frequency should decrease over time.
Update — On January 10, 2020 Microsoft indicated that it now believes it may be possible to ship a fix in an Office or Windows update. Additional internal approvals are required given the scope of such a solution.
Update — On March 6, 2020 Microsoft indicated that it expects to release a fix in April or May.
Update — On March 25, 2020 Microsoft said, "The updated code to enforce Centennial removal has already made it to DevMain in release 12723.2000. After the release hits the April monthly update, end users installing a new install of Office will have the appx package removed prior. For existing installs, the same detection and removal of Centennial and then the repair can be performed by running the Online repair function from Programs & Features."
Update — On April 28, 2020 Microsoft release a fix for this issue. See this Microsoft article for more information.
Cannot export some charts with linked data labels
You may be unable to export charts whose data labels are linked to a non-contiguous range of cells from Excel to PowerPoint/Word using Macabacus. You may also find that you cannot copy/paste these charts natively (either to PowerPoint/Word or even within the same worksheet), or perform other native operations on them (e.g., change chart type, move chart). This problem is described in a Microsoft forum post and corroborated by our testing.
We have concluded that this is an Excel bug for which there is currently no workaround other than restructuring the chart data so that the cells to which data labels are linked are contiguous.
Some Macabacus dialogs appear blank in Office 2016+
This problem is due to a Windows or Office bug. To resolve this issue, change your display setting to "Optimize for compatibility" under File > Options > General in all affected Office applications and restart those applications.
Microsoft would challenge the classification of this behavior as a bug, and argue that this behavior results from your chosen display setting. However, the average user lacks technical experience required to knowledgeably set this setting, and deferring to the uninformed user is not appropriate. This setting deflects responsibility for, conceals, and fails to address the underlying problem: Office incompatibilities with high-density displays that Microsoft has been unable to resolve.
Some Macabacus task panes not displaying properly in Excel 2016+
Content in some Macabacus task panes for Excel 365/2016, such as the Shortcut Manager and Explorer panes, may not display properly. This problem was first observed in May 2018, and does not appear to affect other Office versions (e.g., Excel 2013) or applications (e.g., PowerPoint 2016). This problem was observed in Microsoft Office 365 Business, but could not be reproduced in Microsoft Office Professional 2016.
We reported this issue to Microsoft engineers on May 15, 2018. Microsoft responded that, prior to Office build 9330, customers should set their Excel display setting to "Optimize for compatibility" under
File > Options > General . We confirmed that this recommendation resolves the issue, and additionally concluded that:
- This problem impacts only Office 365 at the time of this writing, not Office 2016, since this setting is not available in Office 2016 and could not be reproduced there.
- This problem is caused by a Microsoft bug introduced in a May 8 or May 14, 2018 Office 365 update, rather than an issue with Macabacus. We are calling this a "bug" because it (a) is an undocumented breaking change that (b) does not affect Office 365 applications and task pane controls uniformly.
Microsoft implied that this issue is resolved in build 9330, which is already available in some release channels, so any impact to users who reject the recommendation above should be temporary. For more information about this setting, see this Microsoft article.
Update — Build 9330 does not fix this bug. We notified Microsoft on May 30, 2018 and are awaiting further guidance.
Cannot export new Office 2016+ chart types
Microsoft introduced several new chart types in Office 2016 (e.g., waterfall, treemap). These new chart types are plagued by a number of widely documented bugs and limitations, including the inability to copy them programmatically. Macabacus copies charts programmatically when exporting from Excel to PowerPoint / Word, so exporting these new chart types will fail.
We reported this bug to Microsoft on Feb 6, 2018 and received a response that the ability to copy these new chart types programmatically is not yet implemented, and that Microsoft does not have a timeline for when this functionality will be available. If you need to export a waterfall chart, use Macabacus' waterfall Quick Chart rather than the native waterfall chart.
Excel data may be deleted unexpectedly
In August or September 2017, Microsoft released an Office update that introduced a bug that may cause Excel 2016 purchased via an Office 365 subscription (only) to delete data unexpectedly after saving when Macabacus' AutoColor on Entry is enabled. This bug was discovered in Office 2016 build 8326, and may be present in other builds. It is believed that you will only encounter this problem if you see the AutoSave option (enabled or disabled) in the top left corner of the Excel window. To avoid this bug, you can disable AutoColor on Entry (which is disabled by default). We reported this bug to Microsoft on Sep 7, 2017 and they have acknowledged it. Any updates will be posted here.
Some Macabacus dialogs do not respond to keyboard input
If some Macabacus dialogs do not respond to keyboard input, another add-in may be causing this condition with low-level keyboard hooks that "hijack" your keyboard. While keyboard hooking has legitimate uses, it should never interfere with the operation of other software. We have observed this conflict only with Workshare's Excel add-in, specifically, although other add-ins might produce the same result. Disable the Workshare or other conflicting COM add-in to resolve the problem, and report the problem to that add-in's manufacturer. This issue seems to affect only modeless Macabacus dialogs (e.g., Pro Precedents/Dependents), not modal dialogs.
This section describes and/or troubleshoots unresolved problems involving Macabacus' Excel add-in not addressed elsewhere in this documentation, which are due to bugs in either our add-in or Microsoft Office that we have not been able to confirm. If your problem is not listed here, check the applicable section of this documentation and our general usage tips.
This section describes and/or troubleshoots unresolved problems involving Macabacus' PowerPoint add-in not addressed elsewhere in this documentation, which are due to bugs in either our add-in or Microsoft Office that we have not been able to confirm. If your problem is not listed here, check the applicable section of this documentation and our general usage tips.
There are no known problems using Macabacus for PowerPoint that are not documented in the applicable section of this documentation.
This section describes and/or troubleshoots unresolved problems involving Macabacus' Word add-in not addressed elsewhere in this documentation, which are due to bugs in either our add-in or Microsoft Office that we have not been able to confirm. If your problem is not listed here, check the applicable section of this documentation and our general usage tips.
When opening Word attachments in email, an error message reads "This method or property is not available because this command is not available for reading."
File > Options > General and uncheck the "Open e-mail attachments and other uneditable files in reading view" box.