Once I started using SharePoint Management Shell for this, I never looked back to Central Admin, that's for sure. I have learned to loathe it. :)
So, on your server, find SharePoint Management Shell, right click and run as admin. Give it a minute to figure out what it is doing. Here's a reference for some of the commandlets I use.
Install-SPInfoPathFormTemplate -Path "C:\Temp\MyTemplate.xsn"
Change the path above to your XSN file that you have copied onto your servers someplace. If the template has not been activated before, you'll need to enable it:
Enable-SPInfoPathFormTemplate -Identity "MyTemplate.xsn" -Site http://server/site
Again, changing the template name and the site to the correct values.
You can also disable and uninstall a template, as well as stop or start:
Disable-SPInfoPathFormTemplate -Identity "MyTemplate.xsn" -Site http://server/site
Uninstall-SPInfoPathFormTemplate -Identity "MyTemplate.xsn"
Stop-SPInfoPathFormTemplate "MyTemplate.xsn"
Start-SPInfoPathFormTemplate "MyTemplate.xsn
If I were you, I would start disabling the form, then installing, then enabling it - see if that helps the situation. If not, you may want to try uninstalling as well - generally, I don't have to change my library at all when I disable / re-enable or uninstall - but you may want to try a test form activated to a test library.
As to your other post, where you mention now getting a correlation id, obviously go check your log files for that correlation, but I do sometimes see forms with code / qRules that are having deployment issues resolve these if re-deployed.