bgrorud

Good work. Kudos to you, and shame on Microsoft. You can have the rest of the day off! -Brad

Have you tried to use the PROCMON tool from System Internals to see if anything else is accessing that registry key? You might be real close to figuring out what is going on if something else is indeed modifying or restricting this registry path (possibly something in Windows itself). If you haven't used Process Monitor before, it can be overwhelming, but it tracks all file, registry, network, etc access on the system. So when you start capturing, there will be hundreds of thousands of entries in under a minute. You can start by turning off the everything except for registry monitoring. Might be pretty daunting though, since you'll still generate thousands of entries every minute, but maybe filtering by that registry path could tell you something. This is my intention if I ever have another one fail, but thus far I haven't. -Brad

UAC may be a contributing factor to it. For my 3 issues, on all 3, I have UAC off, and on one of them for sure I change the Local Security Policy for "Run all administrators in admin approval mode" to Disabled. I did change it back to the default of Enabled and turn UAC on while troubleshooting, but perhaps the damage was already done by that point. 2 PCs are joined to the domain, but I don't enforce UAC via group policy. 1 PC was just a standalone system. -Brad

I have not had the issue on other PCs besides the 3 I had, but FYI - others have reported that the above fix was not a permanent solution. Still worth trying though. -Brad

From Md Shamim Ahmed MSFT | Microsoft Agent | Moderator (from the link in the above post) (Some of this seems to just be throwing everything possible at the problem, but I have not done all the steps listed at the same time, so if I encounter the problem again, I will follow these steps and see what happens. -Brad) Root Cause Analysis The disappearing rights in the CapAuthz folder might indicate: Corrupted Office installation. Interference from security software (e.g., Endpoint Protection or third-party antivirus). Registry permission conflicts due to Windows Updates or third-party applications. Potential Solutions: Confirm and Reset Permissions Open the Registry Editor with administrative privileges. Navigate to: Copy codeHKLM\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Microsoft\SecurityManager\CapAuthz Right-click the CapAuthz folder and choose Permissions. Ensure the necessary groups/users (e.g., SYSTEM, Administrators) have Full Control. Apply and propagate permissions to child objects. Rebuild Office 2019 Licensing Token A damaged licensing token could cause the "Not Implemented" error. Steps: Run the following command in an elevated Command Prompt: bashCopy codecscript "C:\Program Files (x86)\Microsoft Office\Office16\ospp.vbs" /rearm Restart the machine and test Outlook functionality. Repair Office Installation Use the Quick Repair or Online Repair options: Go to Control Panel > Programs > Programs and Features. Select Microsoft Office 2019, then click Change. Choose Online Repair for a deeper reset. Check for Updates Confirm that Office 2019 is running the latest update. Run: bashCopy codewinword.exe /update This ensures any bug fixes or compatibility improvements are applied. Disable Conflicting Add-ins Open Outlook in Safe Mode: bashCopy codeoutlook.exe /safe If the problem resolves, disable all third-party add-ins via File > Options > Add-ins and re-enable them one by one to identify the culprit. Investigate Group Policy or Security Software If in a managed environment, check if a Group Policy is restricting permissions on the CapAuthz folder. Temporarily disable third-party antivirus/firewall software to test its involvement. If the Problem Recurs After Reboot Use the Procmon tool from Sysinternals to track real-time changes to the registry, focusing on the CapAuthz folder. Monitor which processes or services modify the permissions.

I received a response with more detailed instructions from Microsoft on their forum. https://answers.microsoft.com/en-us/outlook_com/forum/outlk_win-outtop_classic-outsub_ofb/outlook-not-implemented-or-limited-connection/ea9726e8-ba1c-44a4-830a-d974ba3ea422?messageId=20364b43-d4db-437d-9688-d3e8450e48e3 I'll post another reply with the content of the port in case in the future the link no longer works. -Brad

Just got an update to my Reddit post, it was stated that they fixed it by following Method 1 from https://learn.microsoft.com/en-us/outlook/troubleshoot/profiles-and-accounts/metered-connection-warning In summary here, these are the steps they listed - Method 1: Delete the SecurityManager key in the registry The article states the issue is with the following key - HKLM\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Microsoft\SecurityManager\CapAuthz\ApplicationsEx but says to delete the "SecurityManager" key and let it delete all the sub-contents NOTE: you need to apply permissions to the key in order to delete it, right-click "SecurityManager", select "Permissions" and then on the Advanced tab, check "Replace all child object permission entries..." and click OK. Then run a repair on the office application. I don't have any currently in a broken state to test this on, so if you have a chance to test this out, let me know the results. This gives me some more items to search on to see if I can find other case studies. -Brad

Does your patch management include office updates? Have you tried immediately after the repair, opening an Office application and hitting - File - Account - Office Updates and letting it update again? When I did that, my last user immediately broke again and maybe your cases where it comes back are ones where it takes a few days before Office reinstalls the update. There are surprisingly few posts on this issue. I created a topic on Reddit - Sysadmin but failed to get any comments. Given that it hit 3 of my clients separately (only 1 PC at each client), there must be more people experiencing it than the 3 of us... -Brad

I'm about out of time for now, so I'm re-installing my original version and going to disable office updates so I can troubleshoot more in the future. A few other points about my setup - * All users are running Windows 10 * All users are using the 64 bit version of Office 2019 Standard * All users have the product key scripted in the XML file * All users have local admin rights on the PC * 1 user had Admin rights with no UAC and policy set to not run in Admin Approval mode (equivalent of Windows 7 admin rights without UAC) * 1 user did not have any 3rd party antivirus (just Windows Defender), the other 2 had Malwarebytes Endpoint Protection Cloud * 1 user was stand-alone Windows 10 Home system, the other 2 were Pro and joined to a domain * Issues were experienced across all user accounts on that PC -Brad

If you try to uninstall or do an "Online Repair" you get the error "Access denied to installation source" Error Code: 30015-23 (5). At which point, the uninstall has completed. For this test, I did not do the manual cleanup of folders and registry. During the reinstall from the original source (mine was from 2021) it generates a "Something went wrong" error code 30016-22 but continues the installation. After the install is done, it appears all programs operate normally and report version 1808 Build 10353.20037. If I force an Office update, let it run through, download, "applying updates..." then goes to "Something went wrong" Error Code 30169-29 (589852) but the updates are applied as the version number is back to Build 10416.20007 and my problems have returned. More symptoms now, when you click "File" in Outlook, it says "Metered Connection Warning" and "Upgrade in Progress" and the "Account Settings" are inaccessible. -Brad

To fill in a few other symptoms I've seen, In Outlook, Trying to "reply all" will get a dialog box that just says "Not Implemented" After uninstalling, the Microsoft manual uninstall procedure tells you to delete the following - 1. %ProgramFiles%\Microsoft Office 16 folder. 2. %ProgramFiles%\Microsoft Office folder. 3. %ProgramFiles(x86)%\Microsoft Office folder. 4. Delete the Office registry sub keys HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun (for every PC with the issue, I cannot delete this folder due to permissions on a "REGISTRY" sub key, I have to apply permissions to that branch in order to delete it) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppVISV HKEY_CURRENT_USER\Software\Microsoft\Office -Brad

Yes, an office update is creating the same issue for me. Running Office 2019 LTSC. One user had the Macro in Word issue. Outlook gets messed up. And the one symptom reported the most often is unable to open Word or Excel files from network locations. If you copy the files to a local C: drive they open just fine. For network files: Safe mode doesn't work. Using File - Open doesn't work. When I uninstall office or try to do the extensive repair on the installation, I get an error about not being able to access the installation source (but it does uninstall). Reinstall of 2019 does not fix it, and I've been pressed for time, so I just fixed by installing Office 2021 LTSC. I have another user with the issue today and I'm hoping to do a bit more research to find the root cause rather than just upgrading. Let me know if you ever found an answer. -Brad