Question farcry 4 - not launching - anybody have a fix on launching isseus?

[BFN177_JP]

my farcry 4 ive puchased doesnt want to launch,i was able to launch this game when it first launched but was too slow on i5 CPU and have upgraded to i7, game startup with first screen, unisoft connect launches and syncronizes, steam is already running but before game executes it shuts down again, im running the following specs:

DXdiag:

Card name: NVIDIA GeForce GT 330M
Manufacturer: NVIDIA
Chip type: GeForce GT 330M
DAC type: Integrated RAMDAC
Device Type: Full Device
[DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 4568 MB
Dedicated Memory: 986 MB
Shared Memory: 3582 MB
Current Mode: 1366 x 768 (32 bit) (60Hz)

OS Name Microsoft Windows 10 Pro
Version 10.0.19045 Build 19045
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name
System Manufacturer Acer
System Model TravelMate 8572G
System Type x64-based PC
System SKU
Processor Intel(R) Core(TM) i7 CPU M 640 @ 2.80GHz, 2800 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date Phoenix V1.27, 2011/04/25
SMBIOS Version 2.6
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer Acer
BaseBoard Product BAP50-CP
BaseBoard Version Not Applicable
Platform Role Mobile
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Installed Physical Memory (RAM) 8,00 GB
Total Physical Memory 7,68 GB
Available Physical Memory 4,05 GB
Total Virtual Memory 8,86 GB
Available Virtual Memory 3,92 GB
Page File Space 1,19 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Running
Virtualization-based security Required Security Properties
Virtualization-based security Available Security Properties Base Virtualization Support
Virtualization-based security Services Configured
Virtualization-based security Services Running
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
A hypervisor has been detected. Features required for Hyper-V will not be displayed.