Comodo Firewall 10.0.1.6223 + Windows Defender Security Center = ERROR

Hello all,
I have Windows 10 + Comodo Firewall 10, after Windows 10 Creator Update I cannot open Windows Defender Security Center interface (GUI).

In event Log I have This Errors:
Error1
Faulting application name: SecHealthUI.exe, version: 10.0.15063.0, time stamp: 0x58ccbce5
Faulting module name: SecHealthUIDataModel.dll, version: 0.0.0.0, time stamp: 0x58ccbc8d
Exception code: 0xc0000409
Fault offset: 0x000000000002f700
Faulting process id: 0x45fc
Faulting application start time: 0x01d2cdc17e4a78e8
Faulting application path: C:\Windows\SystemApps\Microsoft.Windows.SecHealthUI_cw5n1h2txyewy\SecHealthUI.exe
Faulting module path: C:\Windows\SystemApps\Microsoft.Windows.SecHealthUI_cw5n1h2txyewy\SecHealthUIDataModel.dll
Report Id: 635fd857-501e-4115-9926-f5512e14eef6
Faulting package full name: Microsoft.Windows.SecHealthUI_10.0.15063.0_neutral__cw5n1h2txyewy
Faulting package-relative application ID: SecHealthUI

Error2
Activation of app Microsoft.Windows.SecHealthUI_cw5n1h2txyewy!SecHealthUI failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

I search the internet and found this:
https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_security/windows-defender-conflicts-with-comodo-firewall/3e959171-5610-459f-9efc-e6499ee679e8

I have this error from the first day after Windows 10 Creator Update but I waited for Comodo update or Windows Update to fix the problem.

I tried to uninstall Comodo firewall then install CIS. With CIS everything was good without problems so I decide to remove the Antivirus Component and restarted my Computer and everything still good until Comodo firewall installed new updates then same error returned.

Then I discovered that SecurityHealthService service not running after startup so I run it manually and I can open Windows Defender Security Center GUI.
But unfortunately I must run it manually every time after restart.

I think that Comodo firewall prevents SecurityHealthService from start automatic at startup time.

After restart I find the service with this status:
Get-Service|where {$_.Name -eq “SecurityHealthService” } | fl *
Name : SecurityHealthService
RequiredServices : {RpcSs}
CanPauseAndContinue : False
CanShutdown : False
CanStop : False
DisplayName : Windows Defender Security Center Service
DependentServices : {}
MachineName : .
ServiceName : SecurityHealthService
ServicesDependedOn : {RpcSs}
ServiceHandle :
Status : Stopped
ServiceType : Win32OwnProcess
StartType : Automatic
Site :
Container :

After restart I found these events in Event log:

Error1
A timeout was reached (30000 milliseconds) while waiting for the SecurityHealthService service to connect.

Error2
The WinDefend service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

Error3
A timeout was reached (30000 milliseconds) while waiting for the WinDefend service to connect.

Error4
The SecurityHealthService service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

Error5
A timeout was reached (30000 milliseconds) while waiting for the FontCache3.0.0.0 service to connect.

Error6
The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

Thanks a lot.

+1 I have same issue.

Please edit your post to be in the required bug reporting format so it can be forwarded to Comodo thanks.