Issue installing a VM FortiGate
Good day,
I'm trying to install a Fortigate 7.6.6 VM for a lab and have this issue

After that I only get a white screen, and enter the trial license window or the device or anything. This is my configuration
FortiGate-VM64-KVM (port1) # show
config system interface
edit "port1"
set vdom "root"
set mode dhcp
set distance 1
set allowaccess ping https ssh http
set type physical
set snmp-index 1
next
end
FortiGate-VM64-KVM (dns) # show
config system dns
set primary 8.8.8.8
set secondary 8.8.4.4
end
FortiGate-VM64-KVM (1) # get
seq-num : 1
status : enable
dst : 0.0.0.0 0.0.0.0
gateway : 10.16.13.20
preferred-source : 0.0.0.0
distance : 1
weight : 0
priority : 1
device : port1
This is what I get when I do the
diagnose debug enable diagnose debug application update -1 execute update-now
FortiGate-VM64-KVM # execute update-now
upd_daemon[1981]-Received update request from pid=2518
FortiGate-VM64-KVM # do_setup[349]-Starting SETUP
upd_act_setup[126]-Trying Setup, fmg=0
__upd_comm_rcv[990]-data_len=24, pkg(buf=0x7ffdc0de1a9c, sz=8516, pos=0)
__upd_fix_rx_pkg[1009]-Failed, length=24, no res header.
upd_act_setup[137]-Failed receiving setup response, fmg=0, ret=-1
upd_act_setup[149]-Setup failed, fmg=0.
do_setup[353]-SETUP failed
upd_daemon[2157]-Disabling remaining actions 11
I can ping the FortiGate Servers without issues
FortiGate-VM64-KVM # execute ping service.fortiguard.net
PING guard.fortinet.net (12.34.97.71): 56 data bytes
64 bytes from 12.34.97.71: icmp_seq=0 ttl=52 time=61.2 ms
64 bytes from 12.34.97.71: icmp_seq=1 ttl=52 time=60.6 ms
64 bytes from 12.34.97.71: icmp_seq=2 ttl=52 time=64.6 ms
64 bytes from 12.34.97.71: icmp_seq=3 ttl=52 time=61.1 ms
64 bytes from 12.34.97.71: icmp_seq=4 ttl=52 time=60.6 ms
--- guard.fortinet.net ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 60.6/61.6/64.6 ms
FortiGate-VM64-KVM # execute ping update.fortiguard.net
PING fds1.fortinet.com (12.34.97.16): 56 data bytes
64 bytes from 12.34.97.16: icmp_seq=0 ttl=52 time=61.0 ms
64 bytes from 12.34.97.16: icmp_seq=1 ttl=52 time=60.9 ms
64 bytes from 12.34.97.16: icmp_seq=2 ttl=52 time=60.4 ms
64 bytes from 12.34.97.16: icmp_seq=3 ttl=52 time=60.6 ms
64 bytes from 12.34.97.16: icmp_seq=4 ttl=52 time=60.2 ms
--- fds1.fortinet.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 60.2/60.6/61.0 ms
My only way to get to the FortiGuard servers is the static route I created
FortiGate-VM64-KVM # get router info routing-table database
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
V - BGP VPNv4
> - selected route, * - FIB route, p - stale info
Routing table for VRF=0
S *> 0.0.0.0/0 [1/0] via 10.16.13.20, port1, [1/0]
C *> 10.16.13.0/24 is directly connected, port1
I can't seem to find how to solve the issue. Tried forcing the Fortiguard update interface to the port1 and the issue is the same.
FortiGate-VM64-KVM # get system status
Version: FortiGate-VM64-KVM v7.6.6,build3652,260127 (GA.M)
First GA patch build date: 240724
Current Security Level: High
Firmware Signature: certified
Virus-DB: 1.00000(2018-04-09 18:07)
Extended DB: 1.00000(2018-04-09 18:07)
Extreme DB: 1.00000(2018-04-09 18:07)
AV AI/ML Model: 0.00000(2001-01-01 00:00)
IPS-DB: 6.00741(2015-12-01 02:30)
IPS-ETDB: 6.00741(2015-12-01 02:30)
IPS-MLDB: 0.00000(2001-01-01 00:00)
APP-DB: 6.00741(2015-12-01 02:30)
AIAP-DB: 0.00000(2001-01-01 00:00)
Proxy-IPS-DB: 6.00741(2015-12-01 02:30)
Proxy-IPS-ETDB: 6.00741(2015-12-01 02:30)
Proxy-APP-DB: 6.00741(2015-12-01 02:30)
FMWP-DB: 0.00000(2001-01-01 00:00)
IPS Malicious URL Database: 1.00001(2015-01-01 01:01)
IoT-Detect: 0.00000(2022-08-17 17:31)
OT-Detect-DB: 0.00000(2001-01-01 00:00)
OT-Patch-DB: 0.00000(2001-01-01 00:00)
OT-Threat-DB: 6.00741(2015-12-01 02:30)
IPS-Engine: 7.01168(2025-11-19 22:41)
Timezone DB Version: 1.003
Timezone DB IANA Version: 2024a
Serial-Number: FGVMEVTMBHEDF96B
License Status: Invalid
VM Resources: 1 CPU/1 allowed, 1993 MB RAM/2048 MB allowed
Log hard disk: Available
Hostname: FortiGate-VM64-KVM
Operation Mode: NAT
Current virtual domain: root
Max number of virtual domains: 2
Virtual domains status: 1 in NAT mode, 0 in TP mode
Virtual domain configuration: disable
FIPS-CC mode: disable
Current HA mode: standalone
Branch point: 3652
Release Version Information: GA
FortiOS x86-64: Yes
System time: Wed Feb 4 13:26:58 2026
Last reboot reason: warm reboot
I read some months back that restarting some daemons solve the issue but can't seem to find the documentation. If someone knows hot to solve the issue and can help me I'll appreciate it