Office 2019 version 16.0.10416.20007 bug issue

[TheGirlInIT]

Hi,

 

We've noticed since the latest Office update (12th Nov 24) staff have been experiencing issues with Word and Outlook. This causes word to throw up pop-ups about macros etc when opening word, and Outlook giving errors and not sending emails (stuck in outbox). When send/receive is run it fails. We've not found anything else online supporting this bug so wondering if anyone else has been faced with it? We're going through the process of removing 2019 and installing 2021 on machines affected but they're coming in thick and fast.

 

Windows 10 64-bit

Microsoft Office 2019 version 16.0.10416.20007

 

Anyone else experiencing Office 2019 issues since last update?

 

Thanks!

[stevenlong1985]

I have a few staff unable to copy and paste between documents. but nothing as bad as yours. Word or Outlook just sort of crashes and you can't do anything to force close the Word or outlook

[bgrorud]

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

[bgrorud]

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

Edited November 22, 2024 by bgrorud

[bgrorud]

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

Edited November 22, 2024 by bgrorud

[bgrorud]

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

[OfficeBugs]

I'm experiencing the same exact problems (as well as the symptoms posted by bgrorud below) with one of my clients, though no reports from any other clients, even ones with similar environments. It seems to be random people, not necessarily across the board, and it seems to primarily impact Windows 10 users, though it happened to one user after upgrading to Windows 11, and in all case they're using the same Office 2019 Standard build, 16.0.10416.20007. I have found that a quick repair doesn't fix the problem, but fully uninstalling and reinstalling does. In all cases, attempting an online repair results in an error being thrown at the end that I've traced to an ose00000.exe program in C:\Windows\Temp getting stuck running in the background during the uninstall - the uninstall still seems to succeed, but the error ends the repair process prematurely and the ose00000.exe process has to be killed before Office can be reinstalled properly again. I have found that for the most part, people that I've repaired this way have been OK, though in a few cases the problem has randomly returned several days later with no obvious cause.

 

In one case of recurrence, I fully scrubbed every possible remnant of Office from all associated folders and the registry, and before reinstalling I checked for Windows updates again, and it inexplicably tried to reinstall KB5046613 (i.e. the Win10 Cumulative update that was also releasd on November 12 alongside this Office update), despite it already being installed prior to the scrub. In that case, I hid the update to prevent it from trying to install again, though I do not know if this was necessary. In another case, this update was uninstalled and hidden after correcting, but a standalone security update then installed afterward that seemed to trigger the bug again. I've also had it reoccur for a user after upgrading to Windows 11 and then rolling back to Windows 10, as well as one case where it reoccured after upgrading to Windows 11. In at least one case, Office was reinstalled, everything was fine for a few days, but then it randomly broke again with no record of any updates having been installed or any other changes being made - I have no idea what triggered the bug to reoccur for them. We have a third-party patch management software that enforces silent updates of other non-Microsoft programs, but I noticed that it also includes .NET framework and .NET redist, which I believe also had security updates around the same time, so I have an unconfirmed suspicion that it's related - I excluded .NET programs from the patch management software afterward, just in case.

 

There definitely seems to be some sort of association between the new Office build and new security patches for Windows - my theory at the moment is that installing any of these security updates somehow breaks the new build of Office, requiring it to be reinstalled to correct it, but because they're a client that pays for time, I don't have the freedom to do too much testing to verify any of my suspicions. All is stable at the moment, but I suspect that I'm going to have more users report problems again at some point. I should also add that this particular client has Windows updates enforced across the board, so they experienced this problem pretty much immediately when the new patches released and I've been dealing with it ever since. I've been reluctant to roll them back, as the majority of users have not been reporting any issues.

Edited November 26, 2024 by OfficeBugs
Typo

[bgrorud]

I have found that for the most part, people that I've repaired this way have been OK, though in a few cases the problem has randomly returned several days later with no obvious cause.

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

[bgrorud]

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

[bgrorud]

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

[bgrorud]

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

 

1. Open the Registry Editor with administrative privileges.
   
2. Navigate to:
   Copy codeHKLM\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Microsoft\SecurityManager\CapAuthz
   
3. Right-click the CapAuthz folder and choose Permissions.
   
4. Ensure the necessary groups/users (e.g., SYSTEM, Administrators) have Full Control.
   
5. Apply and propagate permissions to child objects.
   

Rebuild Office 2019 Licensing Token

 

• A damaged licensing token could cause the "Not Implemented" error.
  
• Steps:
  
  1. Run the following command in an elevated Command Prompt:
     bashCopy codecscript "C:\Program Files (x86)\Microsoft Office\Office16\ospp.vbs" /rearm
     
  2. Restart the machine and test Outlook functionality.
     

Repair Office Installation

 

• Use the Quick Repair or Online Repair options:
  
  1. Go to Control Panel > Programs > Programs and Features.
     
  2. Select Microsoft Office 2019, then click Change.
     
  3. 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

 

1. Use the Procmon tool from Sysinternals to track real-time changes to the registry, focusing on the CapAuthz folder.
   
2. Monitor which processes or services modify the permissions.
   

Edited November 27, 2024 by bgrorud

[bgrorud]

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

[OfficeBugs]

I do believe we have Office updates enforced as well, however I will say that in every case, I check for updates afterward and always find that it says it's already up to date. I've just had this happen again to few more users. The only thing that seems to have happened is some unrelated HP software was updated through Windows update - I'm not sure if that's related whatsoever. One new thing that I've discovered is that they have a policy that forcibly disabled UAC. I don't know if it matters, but I have had cases in the past where some software does not like UAC being disabled.

 

I have attempted the fix involving taking control of and deleting the "HKLM\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Microsoft\SecurityManager" key. Prior to this, I discovered that the permissions were in fact corrupt on it, and underneath it the only thing that existed was an empty CapAuthz key, also with no permission. Prior to reinstalling Office, I deleted the SecurityManager key and then ran a quick repair. The quick repair did not fix anything, and the key was not regenerated. After this, I tried an online repair. Once again, an error was thrown at the end, OSE00000.exe was stuck running in the background, and the repair ended, leaving Office uninstalled. Prior to reinstalling, I rebooted the computer. I then installed Office 2019 again - this ended with the same error once again and OSE.exe being stuck running in the background, however Office did seem to otherwise successfully install. Office is now working once again, however upon checking the registry, I found that the SecurityManager key still was not recreated (and therefore no CapAuthz underneath it), so I really do not know what to make of that. I believe that this is all related and that this is inevitably going to break again so long as this behavior is still present. One thing to note is that OSE.exe / OSE00000.exe always has the time stamp of November 1, 2024, so obviously this file has been updated in the latest version.

 

In the one case where I mass scrubbed every single possible remnant of Office from the computer, I do not believe that the install crashed at the end with OSE.exe being stuck, and that user has not reported any more problems since, so I guess a full comprehensive scrub may be necessary?

Edited December 3, 2024 by OfficeBugs

[bgrorud]

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

[bgrorud]

I have attempted the fix involving taking control of and deleting the "HKLM\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Microsoft\SecurityManager" key. Prior to this, I discovered that the permissions were in fact corrupt on it, and underneath it the only thing that existed was an empty CapAuthz key, also with no permission. Prior to reinstalling Office, I deleted the SecurityManager key and then ran a quick repair. The quick repair did not fix anything, and the key was not regenerated. After this, I tried an online repair. Once again, an error was thrown at the end, OSE00000.exe was stuck running in the background, and the repair ended, leaving Office uninstalled. Prior to reinstalling, I rebooted the computer. I then installed Office 2019 again - this ended with the same error once again and OSE.exe being stuck running in the background, however Office did seem to otherwise successfully install. Office is now working once again, however upon checking the registry, I found that the SecurityManager key still was not recreated (and therefore no CapAuthz underneath it), so I really do not know what to make of that. I believe that this is all related and that this is inevitably going to break again so long as this behavior is still present. One thing to note is that OSE.exe / OSE00000.exe always has the time stamp of November 1, 2024, so obviously this file has been updated in the latest version.

 

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

[OfficeBugs]

I've not yet done that, though I have used PROCMON in the past. It's difficult because once I correct the problem temporarily, I don't have any computers to test with until they call in with a problem again. I think I may have had a bit of a breakthrough, but I haven't had a chance to test yet.

 

On the PC that the SecurityManager key did not recreate on, I discovered that it actually looked like it existed under another Wow6432Node key, i.e.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Wow6432Node\Microsoft\SecurityManager\CapAuthz

Notably, this particular user at some point had the 32-bit version of Office installed, which I assume is why this key was being used, and this may be similar for others having the same problem. On the one PC that I did a full comprehensive scrub that seems to have been OK since, One of the things I did was remove the entire HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office key, which would have cleared the Wow6432Node key as well if it was in use, and upon reinstall it didn't throw any errors and it seemed to properly recreate the correct CapAuthz key in the end.

 

In addition to this, one of the links you provided referenced that the equivalent fix for Office 2013 was to update permissions on this key: HKEY_CLASSES_ROOT\Installer\Components\F1291BD604B860441AN89E60BDEE0F9C

 

This 2013 fix peaked my interest, because we actually had longstanding issues in the past with a different client where we have this specifically as a workaround - in their case, the primary issue was that using the "Send to > Mail recipient" option in the context menu would throw an error saying that Outlook is not the default mail client, though I do think there were some other issues associated with it. It was something weird in their environment specifically causing it, but we could never figure out what it was, so we just applied this fix whenever it popped up and then it would never happen to them again. It persisted long after moving on from Office 2013 and they're using Office 365 now, so it definitely can impact other versions of Office somehow.

 

Going forward, if this pops up again, I'm going to attempt just updating the permissions on all three of these keys to see if that allows it to repair normally. I'm making the assumption that if I don't run into the error where it crashes and OSE.exe gets stuck running in the background, then it probably means that it has been permanently fixed.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Wow6432Node\Microsoft\SecurityManager\CapAuthz

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Microsoft\SecurityManager\CapAuthz

HKEY_CLASSES_ROOT\Installer\Components\F1291BD604B860441AN89E60BDEE0F9C

[OfficeBugs]

I thought I'd make a final update here. This workaround appears to have worked. Basically, I just closed office programs and added full access permissions to each of these registry keys to domain admins, local admins, and the particular user. Office immediately started working normally again after that, I didn't have to repair it or even reboot the computer. I might attempt to create some sort of group policy that automatically grants "Domain Users" permissions to these particular keys, which should accomplish the same thing, though I haven't looked into what's involved in that yet - if I can pull that off, then it should automatically fix it even if the problem somehow re-triggers again. I haven't bothered to work out which of these three keys was the important one to correct, and I don't think I'm even going to try because it's not worth the effort.

 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Wow6432Node\Microsoft\SecurityManager\CapAuthz

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Microsoft\SecurityManager\CapAuthz

HKEY_CLASSES_ROOT\Installer\Components\F1291BD604B86 0441AN89E60BDEE0F9C

Edited December 6, 2024 by OfficeBugs

[bgrorud]

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

 

-Brad

[OfficeBugs]

I thought that I had posted another update here, but perhaps I fogot to submit it. One more final, final update:

 

While this fix does work (it definitely revolves around the CapAuthz key, not the other HKEY_CLASSES_ROOT key), the fix is not really persistent on its own. Basically, as soon as you correct the permissions of the CapAuthz key, Office seems to automatically delete the whole SecurityManager key the next time you launch it. Office then continues to work just fine without this key, and nothing I do seems to cause the key to regenerate, however at some random point a few days or a week later, the key and subkeys seem to get recreated with the same corruption on CapAuthz as before. I struggled greatly with getting a group policy to automate this part - the policy would run, but for some reason would never correct the CapAuthz key. In the end, what I ended up getting to work was a policy that updated the permissions of the SecurityManager key and replace child permissions, in addition to a startup powershell script that recursively took ownership of the SecurityManager key and all sub keys. I can't tell if both were necessary or only one due to the fact that Office then deletes the key, but it appears to have worked, so I'm leaving it as-is until someone complains again.