Hey everyone!
I wanted to share how I managed to bring my completely dead ASUS ROG Strix SCAR 17 keyboard back to life after spending days troubleshooting.
The keyboard and RGB lighting are now working perfectly again, without replacing a single hardware component!
I'm sharing the complete process in simple steps because I know how frustrating this issue can be.
My laptop and symptoms
Model: ASUS ROG Strix SCAR 17 G733PYV
Problem started: After overnight Windows/ASUS updates.
What happened:
Internal keyboard completely stopped working.
RGB keyboard lighting disappeared.
Keyboard didn't work even inside BIOS.
External USB keyboard worked normally.
Windows didn't recognize the internal keyboard as a normal ASUS keyboard.
I initially thought the keyboard or motherboard had died.
Things I tried that DID NOT work
Before finding the solution, I tried:
EC reset (holding the power button)
Keyboard driver reinstallations and rollbacks
BIOS update from 334 to 336
Official ASUS keyboard firmware updater
Completely reinstalling Windows
Having a technician inspect and reconnect the keyboard ribbon cable
Nothing worked.
Step 1: Check if your keyboard is stuck in recovery mode
This was our first major discovery.
Connect an external USB keyboard, open Device Manager, and look for a device called:
ITE Upgrade Mode
You can also open PowerShell and run:
Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -like "*VID_048D&PID_89DB*" }
In my case, the controller appeared as:
USB\VID_048D&PID_89DB
This meant Windows could still detect the keyboard controller, but it was operating in firmware recovery mode instead of normal keyboard mode.
Important: This device ID matched my particular recovery situation. Other models may behave differently.
Step 2: Download your EXACT ASUS keyboard firmware
Go to the official ASUS support website and find your exact laptop model.
For my G733PYV, the support page was:
https://www.asus.com/us/supportonly/g733pyv/helpdesk_bios/
I downloaded:
ROGNkeyFWupdate_ASUS_Z_V3.8.3.008_15637_5.exe
I extracted the package using 7-Zip.
Inside, I found:
ROGKBFWUpdateTool.exe
OEM_Library.dll
info.ini
fw\FGA00000.G733PYV.315
The .315 file was the firmware intended for my G733PYV.
Do not use firmware from another laptop model. You could permanently damage the keyboard controller.
I kept the original extracted files untouched and made a separate recovery copy for troubleshooting.
Step 3: Check the ASUS firmware registry entry
This was an important part of our troubleshooting.
We inspected the official ASUS updater using ILSpy and discovered that its recovery routine reads a stored firmware version from the Windows registry.
Asus you need to fix this!!!!
Because I had performed a clean Windows installation, this registry entry was missing.
The location was:
HKEY_LOCAL_MACHINE\SOFTWARE\ASUS\FWVersion\ROGKBFW
In Administrator PowerShell, we created the following entry:
reg add "HKLM\SOFTWARE\ASUS\FWVersion\ROGKBFW" /v "FW version" /t REG_SZ /d "FGA00000.G733PYV.314" /f /reg:64
Then verified it using:
reg query "HKLM\SOFTWARE\ASUS\FWVersion\ROGKBFW" /reg:64
VERY IMPORTANT: The .314 value was an experimental placeholder based on our specific G733PYV firmware family. It was not a verified previously installed firmware version.
This is NOT a universal registry fix. Do not copy this command blindly, especially if you have a different ASUS model or already have a valid registry entry.
Also, creating this registry entry did not immediately fix my problem.
The updater still failed.
We eventually found another issue.
Step 4: Install the missing Microsoft Visual C++ files (THIS WAS THE BREAKTHROUGH!)
Every time I launched the ASUS keyboard firmware updater, it displayed:
Failed to update the keyboard's firmware.
We checked the updater logs here:
C:\ProgramData\ASUS\ROGKBFWUpdateToolLog\
Then we investigated why the updater couldn't initialize properly.
We discovered that Windows was missing several Microsoft Visual C++ runtime files:
MSVCP140.dll
VCRUNTIME140.dll
VCRUNTIME140_1.dll
The ASUS updater depended on these libraries to load its native keyboard communication component.
Our diagnostic initially returned:
Normal DLL load failed.
Windows error: 126
Error 126 indicated that a required module could not be found.
Here's what fixed that part:
Download the official Microsoft Visual C++ Redistributable (x64):
https://aka.ms/vs/17/release/vc_redist.x64.exe
Install it, or select Repair if already installed.
Restart your laptop.
Open PowerShell and check:
foreach($n in 'MSVCP140.dll','VCRUNTIME140.dll','VCRUNTIME140_1.dll'){ [PSCustomObject]@{DLL=$n;Exists=Test-Path "C:\Windows\System32\$n"} }
All three should show True.
After installing the runtime, our native DLL loading test finally returned:
DLL LOAD SUCCESSFUL
This was the turning point.
Step 5: Run the official ASUS firmware updater again
After fixing the missing dependencies, I launched the official ASUS firmware updater from my extracted recovery folder.
My working folder was:
C:\DRIVERS\ROG-G733PYV-Recovery\
I used Administrator PowerShell:
Start-Process -FilePath "C:\DRIVERS\ROG-G733PYV-Recovery\ROGKBFWUpdateTool.exe" -WorkingDirectory "C:\DRIVERS\ROG-G733PYV-Recovery" -Verb RunAs
Make sure you're using the official updater and correct firmware for your exact model.
Keep your laptop connected to AC power. Do not interrupt an update once flashing begins.
AND THIS TIME IT WORKED!
The official ASUS firmware recovery completed successfully.
My internal keyboard came back to life, and the RGB lighting started working again!
No motherboard replacement. No keyboard replacement. No expensive repair.
Keep a copy of your official ASUS firmware package.
IMPORTANT: Use AI to adapt these steps to YOUR ASUS model
One thing that made this recovery possible was using ChatGPT throughout the troubleshooting process.
Instead of blindly copying fixes from different ASUS laptops, I used AI to help inspect logs, understand the ASUS firmware updater, identify missing Windows dependencies, and investigate the recovery-mode device.
If you have a different ASUS model, do not blindly follow my firmware filenames or registry command.
You can paste the following into ChatGPT or another AI assistant:
My ASUS ROG laptop's internal keyboard and RGB lighting stopped working after an update. The keyboard doesn't work in BIOS, but an external USB keyboard works.
I found this recovery thread for the ASUS G733PYV, but my laptop may be a different model.
Please guide me step by step to identify my exact model, check Device Manager for ITE Upgrade Mode, locate the official ASUS keyboard firmware package, inspect the updater logs, verify Microsoft Visual C++ dependencies, and determine whether a registry backup is missing.
Do not assume the G733PYV firmware or registry value applies to my laptop. Explain the risks before any firmware flash or registry modification. Prefer read-only diagnostics first.
AI can help interpret the results and tailor the troubleshooting process, but it cannot guarantee that a firmware file or registry value is safe. Always verify the exact model and use official ASUS firmware.
Credit to the original ASUS ROG Forum recovery thread
A massive thank-you to the people who documented a similar keyboard firmware recovery on the ASUS ROG Strix G16 G614PR.
Original thread:
https://rog-forum.asus.com/t5/gaming-notebooks/rog-strix-g16-g614pr-built-in-keyboard-stopped-working-after/td-p/1153955
That discussion pointed us toward the firmware recovery process and helped us understand that a keyboard showing up in ITE Upgrade Mode might still be recoverable.
My G733PYV required additional troubleshooting, especially identifying the missing Visual C++ runtime dependencies.
Final thoughts
If your ASUS ROG keyboard suddenly stops working, even inside BIOS, don't immediately assume the hardware is dead.
In my case, the controller was still detectable in ITE recovery mode, and the official firmware updater initially failed because its native library couldn't load properly.
We also recreated a missing ASUS firmware-version registry entry during troubleshooting. I cannot confirm whether that registry entry was required for the final recovery, because it was already present when we fixed the Visual C++ dependency issue.
The confirmed breakthrough was installing the missing Microsoft Visual C++ runtime, after which the official ASUS updater worked.
Hopefully this helps someone avoid days of frustration or an unnecessary keyboard/motherboard replacement.
Good luck, and huge thanks again to nthe ROG community!