![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 72%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERF%3C/text%3E%3C/svg%3E)
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,464 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 32%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
Office doesn't require IIS. It looks like you might be trying to install an office component that is attempting to integrate with the web server. I have no idea what that could be in the core Office product.
Another possibility is that there was already an Office install (or start of one) that is trying to repair itself when you run the new install. This used to happen quite a bit but I haven't seen it in years. It is the self-repair feature of the installer. Historically it was related to a bad COM registration generally.
My first suggestion is to look at the installed products on your machine and remove any Office-related products. There is a lengthy article on StackOverflow that walks through all the things you can do to fix the machine so you can then run the Office installer.