MSO Word 2016 will crash when double click the added Zip file. (after installed patch of 2024-02) (KB5002542)

Question

MSO Word 2016 will crash when double click the added Zip file. (after installed patch of 2024-02)

Update: It should caused by KB5002542, it can be resumed after un-install KB5002542.

Is it the known issue of patch?

Answer 1

Hi,

Does this issue also occur in other types of files?

I suggest you open it in safe mode running the following command: Press Win + R, type "winword /safe" in the blank box, press Enter. If it works fine in safe mode, please check the add-ins in your Word and disable them.

Click File > Options > Add-Ins on the left side of the dialog. Then click the drop-down arrow at the bottom of the dialog box and select "COM Add-Ins" from the list, then click the GO button. What comes up is a list of COM-Add Ins that are loaded and running.

Just checking in to see if the information was helpful. Please let us know if you would like further assistance.

---

If the response is helpful, please click "Accept Answer" and upvote it.

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.

Answer 2

After more test, We find my home PC has no this problem. Windows 11 + MSO 2016, and Windows update from Microsoft directly. The problem PCs, my working PCs, Windows 10 + MSO2016 and Windows update from WSUS. Seem this is the difference OS, I have try to removed KB5034763 (Windows 10 Update Patch) in my working PC but still problem. then I have try to install back the KB5034763 and remove the KB5002542 (MSO Word Update Patch) to resumed normal. I have checked in Microsoft Website the KB5034763 has no any dependency. I do not know why the KB5034763 is no problem in Windows 11. Or say, the working PC is updating by WSUS, any patch is missed ?

Answer 3

https://support.microsoft.com/fr-fr/topic/mise-%C3%A0-jour-du-13-mars-2024-pour-office-2016-kb4484303-3101a4cb-90bf-1fdf-658e-e65e7be35c49

Here is the KB from March 13th that solves the problem.

Answer 4

We are having the same issue. Does anyone know if there are plans to publish the fix KB4484303 to WSUS or the MS catalog site, as we need to deploy this to a lot of computers.