When Office stops working as expected, start with the shortest official checks before you reinstall anything.
Problem Description: Debug Pop Up Add
Hello all, Currently developing a JavaScript add-in for Microsoft word and are looking to start running live tests with users. To facilitate this I wish to remove the following pop-up that appears when the add in button is pressed. (Clicking "cancel" does not stop the dialog from appearing in the future.) A thread on StackOverflow has advised adding --no-debug to the package.json file (as below). Which has not been successful here. Is there another setting I can change to remove the pop-up? Thanks in advance!  ```json "scripts": { "build": "webpack --mode production", "build:dev": "webpack --mode development", "configure-sso": "office-addin-sso configure manifest.xml", "dev-server": "node --inspect=localhost:8080 dist/middletier.js", "lint": "office-addin-lint check", "lint:fix": "office-addin-lint fix", "prettier": "office-addin-lint prettier", "start": "office-addin-debugging start manifest.xml --no-debug", "start:desktop": "office-addin-debugging start manifest.xml --no-debug", "start:web": "office-addin-debugging start manifest.xml --no-debug", "validate": "office-addin-manifest validate manifest.xml --no-debug" }, ```

Quick Answer for Office Won't Complete Task
To remove the debug pop-up when running your JavaScript add-in for Microsoft Word, you can try the following steps: Open the **`package.json`** file in your project.
Likely Causes Behind Common Document Triggers
The Microsoft account or license context may not match the purchase or device.
Cached credentials, outdated builds, or damaged local components can trigger document & file issues.
A file-specific corruption or add-in conflict can mimic a broader application failure.
Recommended Solution: Repairing Office Startup Issues
When to use this: Apply these steps when the symptoms match and you can access the relevant Microsoft account or administrator.
Locate the **`"start"`** script in the **`"scripts"`** section of the **`package.json`** file.
It should look like this: ``` jsonCopy code "start": "office-addin-debugging start manifest.xml --no-debug" ``` Remove the **`--no-debug`** option from the **`"start"`** script, so it becomes: ``` jsonCopy code "start": "office-addin-debugging start manifest.xml" ``` Save the **`package.json`** file.
By removing the **`--no-debug`** option, the add-in will be launched without suppressing the debug pop-up.
Now, when you press the add-in button, the pop-up should no longer appear.
After making this change, you may need to rebuild or restart your project for the updated configuration to take effect.
Alternative Solutions for Broader Document Workarounds
Retry the Microsoft-side steps after restarting the app and device.
Test the same action in a private browser session or a new blank file to isolate account vs file issues.
Capture exact error text and screenshots before contacting Microsoft Support or your administrator.
Working with WPS Office: Using WPS While Office Is Unavailable

WPS Office cannot replace Microsoft account, activation, or cloud fixes for this scenario. It remains one of the best free Microsoft Office-compatible alternatives for opening and editing local files.
Download and install WPS Office from the official website.
Open local Word, Excel, PowerPoint, or PDF files in the matching WPS app.
Save a working copy locally while Microsoft-side issues are resolved.
Return to Microsoft Office after the primary fix succeeds.
If you need a practical local workspace in the meantime, try WPS Office.
Prevention Tips for Avoiding Repeat Document
Keep one primary Microsoft account for subscriptions and Office sign-in.
Install updates for Office and Windows before retrying failed workflows.
Back up important files before repair, reset, or reinstall actions.
Work on copies and keep version history enabled when available.
FAQs About Debug Troubleshooting FAQ
Can WPS Office fix this document & file issues issue directly? Only when the WPS steps match the formatting or file task. Account, activation, and cloud issues stay on the Microsoft side.
Should I reinstall Office before trying these steps? Not first. Confirm account, license, and the exact error before reinstalling.
What should I send to Microsoft Support? The affected account email, device type, Office version, exact error text, and screenshots with personal data hidden.




