Excel 2016 cannot record macro or add ActiveX control in v.1809

This thing, with version 1809, is getting better and better every day.

I just found out that I can neither record macros in Excel 2016 x64 nor I can add ActiveX controls.

That's what I'm getting, when trying either one of them:




As it turns out, I'm not the only one in this world having this issue. And how could I possibly be, when we're talking about the Redmond geniuses?

In the Microsoft Community a lot of people have similar issues.
One user has stated that after installing Windows 10 Build 18309.rs_prerelease.181220-1256, the problem is resolved.

Does anyone have similar problems?

You have to enable TragicX, since it is considered non-trusted for Macro's. Enable or disable ActiveX settings in Office files - Office Support Also see this. https://support.microsoft.com/en-us/...nsert-controls Not the first time that Microsoft has broken their own software. https://support.microsoft.com/en-us/...solution-after

bro67 said:

You have to enable TragicX, since it is considered non-trusted for Macro's. Enable or disable ActiveX settings in Office files - Office Support Also see this. https://support.microsoft.com/en-us/...nsert-controls Not the first time that Microsoft has broken their own software. https://support.microsoft.com/en-us/...solution-after

Thanks a lot for your suggestion.
I tried the fix proposed by Microsoft, but unfortunately it didn't help.
It seems that I have to wait for the next FU (as suggested by a user in the MS forum), hoping that it will fix all the mess created by 1809.

OK...finally solved!

Errors solved:

1. Word cannot save files if COM addins are enabled
2. Acrobat PDFMaker addin (or other COM addins), although visible in Word ribbon, all its options are disabled.
3. Import/Export function in Outlook does not work and Outlook crashes when trying to import or export.
4. Adding an ActiveX control or recording a Macro in any Office application does not run.

All the above problems in version 1809 pertain to the regional settings (culture) used. I was using en-150 (English Europe)!
Users with "special" Windows regional settings (i.e. “UserCustomCulture”), need to change these settings to a “FrameworkCulture”.

There are several “UserCustomCulture” in Windows 10, to be precise 640 of them. Some examples of these “UserCustomCulture” are :
English (Europe), English (Austria), English (Bahamas), English (Cyprus), English (Germany), English (Netherlands), French (Morocco), German (Belgium), Greek (Cyprus), Russian (Ukraine), Spanish (United States), Spanish (Latin America) etc

To find out if you’re using a “UserCustomCulture” format do the following:
Open an elevated PowerShell and type the command:

Code:

[System.Globalization.CultureInfo]::GetCultures([System.Globalization.CultureTypes]::AllCultures) | Where-Object {$_.Name -EQ $(Get-Culture)} | FL

Check the “CultureTypes” property to see if it is UserCustomCulture.
If it is and most probably is, since you’re having any or all of the above problems, then you have to find another culture to use.

Examples of "FrameworkCulture" are:
English (United States), English (United Kingdom), English (Ireland), French (France), German (Germany), Greek (Greece), Italian (Italy), Spanish (Spain) etc.

To find a non-UserCustomCulture, i.e. a FrameworkCulture, in PowerShell type the following command:

Code:

[System.Globalization.CultureInfo]::GetCultures([System.Globalization.CultureTypes]::AllCultures) | where Culturetypes -Match 'FrameworkCultures' | select LCID, KeyboardLayoutId, Name, DisplayName | Sort DisplayName | FT -AutoSize

Check the long list that will be produced (203 entries) and make a note of the culture that suits your needs.

Now go to Control Panel > Region > Formats tab
and under Format choose the “FrameworkCulture” you selected from the previous PowerShell command.
Choose Apply and reboot.

All your problems have been solved!

HTH. Dimitri