Finally got it working. Removing "BranchCache" through the Server Manager and disabling the print spooler freed up port 80 and permitted the installation to proceed. (Fortunately we do not need either of these features.) Hopefully this will save someone else hours of banging their head against this problem!
This is completely insane!
We have services running under those ports, why does FileMaker claim these ports without the option to chose another??????
Impossible to use as it is!
Thank for the find!
Despite running netstat against port 80 of which it showed nothing on my VM, the installer was still reporting the port 80 conflict.
I'm having the exact same issue and can't seem to get past it. I've spent hours trying to figure this out as nothing appears to be using port 80 or 443. At this point, if I didn't need to use this software, I wouldn't.
On Windows 2008 R2 Server, you need to Stop "Web Deployment Agent Service" and make it manual. This runs on port 80 with PID 4. I was then to able to install FMS13.
Use the netstat -a -o from the command line to see what port is using 80 and 443.
Don't know if this will help you, but I had a conflict on port 80 with IIS hosting a website. Stopped IIS and it didn't clear the conflict so I restarted the server, which worked. FMS (15) has now installed and I have reconfigured IIS which is now also working correctly.