IIS error (possible related to microsoft word interop or windows update 0x80070070 error)

Yesterday I installed office on the production server because my application (C#) is using Microsoft Word Interop. I still got the problem and the part of the application that was using Word Interop (document creation) was not working but the application itself was working fine. In the morning the application was off, and keep throwing "500 error". I uninstalled office but the problem was still there. Finally I performed the windows update and problem solved. Can anyone tell me what could possible go wrong? Here is a part of the windows update log:

03:00:56:161 996 1b54 Handler ::::::::::::: 2017-11-16 03:00:56:161 996 1b54 Handler :: START :: Handler: MSI Install 2017-11-16 03:00:56:161 996 1b54 Handler ::::::::: 2017-11-16 03:00:56:161 996 1b54 Handler : Updates to install = 1 2017-11-16 03:00:56:161 996 1b54 Handler Extracting MSP file stored in CAB filterpack-x-none.cab 2017-11-16 03:00:56:176 996 1b54 Handler FATAL: Extraction of CAB filterpack-x-none.cab failed, error = 0x80070070 2017-11-16 03:00:56:176 996 1b54 Handler : WARNING: Operation failed at update 0, Exit code = 0x80070070 2017-11-16 03:00:56:176 996 1b54 Handler ::::::::: 2017-11-16 03:00:56:176 996 1b54 Handler :: END :: Handler: MSI Install 2017-11-16 03:00:56:176 996 1b54 Handler ::::::::::::: 2017-11-16 03:00:56:176 868 ca4 DnldMgr Regulation: {7971F918-A847-4430-9279-4A52D1EFE18D} - Update D5ACB45E-3FF2-4DD1-AB54-3BA19C4B4440 is "Defaults" regulated and can NOT download. Sequence 2467 vs AcceptRate 0. 2017-11-16 03:00:56:176 868 ca4 DnldMgr Regulation: {7971F918-A847-4430-9279-4A52D1EFE18D} - Update 6CCF7EC0-EE26-4E69-9700-6F0395CD3E53 is "Defaults" regulated and can NOT download. Sequence 2467 vs AcceptRate 0.

EDIT

I found that error 0x80070070 in windows update log is related to insufficient disk space. Is this possible related with the "500 error" of the iis server? There is 3GB free space in the main hd, the other hds have more than 5GB free space.

You should think about changing the way you have coded if you can. Placing office on a backend server to interact behind the scenes for you is notoriously bad. Usually, you let the client deal with document types etc, the only thing that is important is that you ensure IIS has relevant entries in it's MIME Types list to be able to handle the office documents (which I think by default it has anyway).