ROG Strix G16 - Keyboard Not Working in MyASUS Cloud Recovery

[Asuslaptopuser]

Is anyone else expirencing this issue?

Issue: The keyboard (both built-in and external USB keyboards) does not work in the MyASUS Cloud Recovery environment (WinRE). Only the trackpad is functional.

Model: ROG Strix G16 (i7 13th gen, RTX 4060)

Steps to reproduce:

Boot into ASUS Cloud Recovery from MyASUS app

Select Troubleshoot → MyASUS in WinRE

Reach the wifi password entry screen

Keyboard is completely non-responsive - cannot type password

What I've tried:

External USB keyboards in multiple ports (none work)

Different USB ports

No on-screen keyboard option available

Only trackpad functions properly

Impact: This makes the MyASUS Cloud Recovery feature completely unusable. I cannot proceed past the password screen, defeating the entire purpose of ASUS's cloud recovery solution.

Request: Please fix the USB/keyboard driver loading in the WinRE environment or provide a workaround. This appears to be a widespread issue affecting multiple ROG users based on online reports.

[ElectroStingz]

Hello,

What happens if you try the cloud recovery directly from the BIOS?

https://www.asus.com/uk/support/faq/1048106

[Asuslaptopuser]

Thanks for the suggestion! Unfortunately, I can't access the BIOS recovery menu - pressing F9 during boot doesn't work on my laptop. The keyboard issue extends to boot-time as well.

The keyboard works fine once Windows is fully loaded, but in any pre-Windows environment (BIOS access, recovery menus, WinRE), it becomes non-responsive. Only the trackpad functions in the MyASUS recovery environment accessed through the app.

[ElectroStingz]

When you see the ASUS ROG logo its usually F2?

[ElectroStingz]

Just another idea to get into the BIOS, you can do this through windows using the advanced startup option.

If you choose that and press on restart it will take you to some other screens, so if your mouse works this should get you into the BIOS, the next screens are as follows.

Choose Troubleshoot

Choose Advanced options

Choose UEFI Firmware Settings

Choose Restart

And this should take you into the BIOS, if the keyboard doesn't work here something is wrong. (Consider disabling fast boot should be in your BIOS somewhere, save and exit and try again). But if working, get to the advanced BIOS section and do the cloud recovery.

[Zalevskiy]

This isn't the correct MyASUS WinPE menu. To add it according to the instructions, you need hidden disk partitions and editing them via the reagent command line.
https://github.com/mjishnu/Fix-MyAsus-In-WinRE?ysclid=mgz7ugaf3o605207017

Or an alternative in the form of a bootable USB drive
Google > MyASUS in WinRE for USB

[Flo]

Are you using Windows 25h2?

https://www.techpowerup.com/342032/windows-11-25h2-october-update-bug-renders-recovery-environment-u...

[Zalevskiy]

Based on my observations of my G814JV 2023, after BIOS 331 and downgrade 313, I've developed a keyboard-related issue. If I press a large number of keys fairly quickly during boot before the logo appears, the keyboard doesn't work in Windows or in the BIOS.

After holding down the power button, pressing the power button, and then pressing the keys gently during boot, the keyboard works as usual. This strongly suggests some kind of password protection mechanism or an NVRAM settings conflict!?

I have an asus.swm file that can be installed via winntsetup. Unfortunately, it's a China Home SL.
X64W11_24H2_SWP_G614JI_00.03 (G16/G18)
https://cloud.mail.**/public/jpBx/uTqruk7yC

I recommend the Zephyrus G16 GU603VU 22H2 factory image (install.wim). Unfortunately, I couldn't find the US EN asus.swm file. Zephyrus has the exact same drivers that were available when I purchased the G16/G18 Strix 2023 and that were later removed from the ASUS driver page. You'll need to install Thunderbolt WHQL and probably replace the DTT driver with the Strix driver. Otherwise, this Windows is much better because it's configured for similar devices.

https://supportlaptop.com/asus-rog-strix-g18-g814jv-issues-and-how-to-fix/

I've seen multiple confirmations online that the very first drivers + 22H2 are more stable. 24H2 and newer drivers have many audio issues.