@AEF
By updates, I am assuming you mean the FortiGuard Services. On the dashboard, does the License Information widget shows the 110C has a valid/registered support contract and that the (FortiGuard) services are reachable?
Not in front of a fgt running the newer firmware, but the FortiGuard panel should still be the same/similar as on 4.0 MR3 (System->Config->FortiGuard) -- can you confirm the FortiGuard Subscription Services are all activate? After this, expand the " AV & IPS Download Options" section and click on the [Update Now] button.
Under " Web Filtering and Email Filtering Options" the port section should indicated the FortiGuard services are reachable by the port selected -- if it does not, try selecting the other port (port 53 or 8888) (remember to click apply after making a port change).
After clicking on the [Update Now] button (above) and assuming you have logging enabled - check the Event Log (under Log@Report) to see if you have something similar to...
" Fortigate update now virdb(22.00445) idsdb(4.00522) aven(5.00147) idsen(2.00174) from xx.xx.xx.xx:443"
From the CLI, type: exec ping service.fortiguard.net
If you get an " Unable to resolve hostname" error then it likely means a DNS or routing related issue. Edit: As a test, try changing the DNS (under System->Network->DNS) to 8.8.8.8. And see if service.fortiguard.net is resolvable.
After the ping test, type the following on the CLI: get webfilter status
You should get a list of IP addresses.
Also just to confirm you do have firewall policies using UTM features (anti-virus/Fortigate web filtering, IPS, App Sensor, etc.)? From what others have reported 3-4 months back (on the forums), the Fortigate may not update if there is no UTM features used on it.
NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C