[BUG] HayDay stuck on logo #708
Description
Describe the bug
When i try to run HayDay on WSA it simply stays on i=game icon
Steps to reproduce the issue
N/A
Expected behaviour
N/A
Downloaded Build Of WSA
Windows build number
25H2 Build 26200.6899
PC Specification
OS Name Microsoft Windows 11 Pro
Version 10.0.26200 Build 26200
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-3F8JEO4
System Manufacturer LENOVO
System Model 82V7
System Type x64-based PC
System SKU LENOVO_MT_82V7_BU_idea_FM_IdeaPad 1 15IGL7
Processor Intel(R) Celeron(R) N4020 CPU @ 1.10GHz, 1101 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date LENOVO KKCN25WW, 11/28/2024
SMBIOS Version 3.0
Embedded Controller Version 1.23
BIOS Mode UEFI
BaseBoard Manufacturer LENOVO
BaseBoard Product LNVNB161216
BaseBoard Version NO DPK
Platform Role Mobile
Secure Boot State On
PCR7 Configuration Binding Possible
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.26100.1"
User Name DESKTOP-3F8JEO4\Admin
Time Zone Egypt Standard Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.65 GB
Available Physical Memory 4.55 GB
Total Virtual Memory 7.67 GB
Available Virtual Memory 4.87 GB
Page File Space 16.0 MB
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, Secure Boot, DMA Protection, Secure Memory Overwrite, SMM Security Mitigations 1.0, Mode Based Execution Control, APIC Virtualization
Virtualization-based security Services Configured
Virtualization-based security Services Running
App Control for Business policy Enforced
App Control for Business user mode policy Off
Automatic Device Encryption Support Reasons for failed automatic device encryption: WinRE is not configured
A hypervisor has been detected. Features required for Hyper-V will not be displayed.
Additional context
No response