How can i forcably remove an Outlook JavaScript Dev Add-in?

Simeon Kostadinov 20 Reputation points
2023-08-15T09:07:59.5766667+00:00

Problem:

At some point i realised that changes to my manifest.xml files dont get reflected on the running dev instance of the add-in. I went ahead and tried to remove the add in, so i can re-add it and forcably reflect the changes, just to find the remove button greyed out:

Screenshot 2023-08-15 104805

After that I went and added the Add-In anyways. I hoped to overwrite the seemigly "broken" one. This wasn't the case and I now have two Add-Ins which i cannot remove. One of them dissapeared over-night causing even more confusion as to what's going on.

I sadly can't develop due to this issue because no changes to the Manifest files get reflected since (I assume) a cached version of an old one (or two) is saved somewhere and being read instead of the updated one.

What I've tried so far:

System Info:

  • React TypeScript Add-In generated with yeoman
  • Outlook 365 (Version 2307 Build 16626.20170)
  • manifest.xml
Microsoft 365 and Office Development Office JavaScript API
Outlook Windows Classic Outlook for Windows For business
Microsoft 365 and Office Install, redeem, activate For business Windows
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. ChristyZhang-MSFT 26,121 Reputation points Microsoft External Staff
    2023-08-16T06:11:34.2866667+00:00

    Hi @Simeon Kostadinov ,

    Welcome to our forum!

    Does this issue occur with other computers?

    According to your description, i notice that you have tried several troubleshooting steps, it's suggested that you could try to remove an add-in from the registry in Outlook:

    1. Close Outlook.
    2. Press the Windows key + R to open the Run dialog box.
    3. Type "regedit" and press Enter to open the Registry Editor.
    4. Navigate to the following registry key: HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins
    5. Find the add-in you want to remove and right-click on it.
    6. Select "Delete" and confirm that you want to delete the key.
    7. Close the Registry Editor and restart Outlook.

    (Note: Serious problems can occur if you modify the registry incorrectly. Before making changes, back up the registry to restore it in case something goes wrong.)

    Hope to help you!


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.

  2. ChristyZhang-MSFT 26,121 Reputation points Microsoft External Staff
    2023-08-17T02:06:13.2333333+00:00

    Hi @Simeon Kostadinov ,

    Glad to hear this issue has been resolved!

    Thanks for the sharing.


    However, due to a recent update in forum policy, the question author now is not able to accept their own answers.

    So I have written a brief summary of the solution this issue. Please feel free to accept it as the answer, which would benefit others who also has similar issues in forum.

    Issue:

    Developed add-in cannot be removed in Outlook, the Remove option greyed out.

    Solution1:

    Remove an add-in from the registry in Outlook:

    1. Close Outlook.
    2. Press the Windows key + R to open the Run dialog box.
    3. Type "regedit" and press Enter to open the Registry Editor.
    4. Navigate to the following registry key: HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins
    5. Find the add-in you want to remove and right-click on it.
    6. Select "Delete" and confirm that you want to delete the key.
    7. Close the Registry Editor and restart Outlook.

    Solution2:

    Remove the Add-In from the Browser version of Outlook for the cached manifest.xml to be completely forgotten.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.