F5F Stay Refreshed Software PC Gaming Valorant VAN1067 Error encountered. Please try again later.

Valorant VAN1067 Error encountered. Please try again later.

Valorant VAN1067 Error encountered. Please try again later.

R
Razlorus
Posting Freak
Find
976
03-08-2021, 05:48 AM
#1
Hi, I see you're having trouble with your Acer Aspire A515-51G laptop. It seems like the issue might be related to the boot settings. You mentioned trying to switch from Legacy mode to UEFI but getting a "No bootable device found" error. Also, your TPM2.0 is enabled and you have TPM 1.16 active. Have you checked if there are any updates for your BIOS or Windows? If you're not comfortable with technical details, it might help to contact RIOT support directly or reach out to a tech support service. Let me know what you find!
Reply
Reply
R
Razlorus
03-08-2021, 05:48 AM #1

Hi, I see you're having trouble with your Acer Aspire A515-51G laptop. It seems like the issue might be related to the boot settings. You mentioned trying to switch from Legacy mode to UEFI but getting a "No bootable device found" error. Also, your TPM2.0 is enabled and you have TPM 1.16 active. Have you checked if there are any updates for your BIOS or Windows? If you're not comfortable with technical details, it might help to contact RIOT support directly or reach out to a tech support service. Let me know what you find!

Reply
Reply
P
Puppypower48
Member
Find
147
03-08-2021, 08:24 PM
#2
It’s clear that the TPM and secure boot settings are only needed for Windows 11, not Windows 10. This is likely because your BIOS is still in legacy mode, so the drive probably uses MBR instead of GPT—explaining why no bootable devices appear after switching to UEFI with secure boot enabled. The error message you’re seeing applies only to Windows 11, suggesting a problem during installation. If this is true, the solution may involve erasing the drive and starting fresh with Windows 10.
Reply
Reply
P
Puppypower48
03-08-2021, 08:24 PM #2

It’s clear that the TPM and secure boot settings are only needed for Windows 11, not Windows 10. This is likely because your BIOS is still in legacy mode, so the drive probably uses MBR instead of GPT—explaining why no bootable devices appear after switching to UEFI with secure boot enabled. The error message you’re seeing applies only to Windows 11, suggesting a problem during installation. If this is true, the solution may involve erasing the drive and starting fresh with Windows 10.

Reply
Reply