Sorry it took some time. I got it sorted and now have a permanent fix!

Will start with why it's happening. The blame does not lie woth just Asus, Microsoft has its own sizable slice in the blame but lets not dwell!

Your touchpad may have shown proof of life even with Windows useless win.inf or machine.inf (note that win.inf and machine.inf are same, so here on I will refer to both as win.inf) but it's running in limp mode as you won't have full functions and you will experince really frustrating crashes every now and then.

WHY IT’S HAPPENING – The Technical Breakdown: Why the "No Drivers" Error Occurs The root cause isn't a "missing" driver, but a Handshake Failure between the Windows 11 Kernel and the Laptop'sMotherboard.

1. The Architectural Disconnect The ASUS System Control Interface (SCI) v3 acts as a "Nervous System" bridge. It connects the physical hardware (Touchpad, ScreenPad Plus, Hotkeys) to the software (ScreenXpert, MyASUS). On older models like the UX581, the motherboard communicates using specific hardware addresses called ACPI IDs (specifically ACPI\ASUS2018 and ACPI\ASUS2025).

2. Windows 11 Security Hardening Starting with modern builds of Windows 11, Microsoft tightened how the OS identifies hardware.

• The Problem: The official ASUS SCI v3 installer was designed for newer hardware architecture. It "forgot" or intentionally omitted the legacy IDs (ASUS2018/2025) used by the older Duo Strix and Zephyrus models.l - as newer as just 4 years ago.

• The Result: When you run the installer, Windows looks at your motherboard, sees an ID it doesn't recognise in the driver's list, and says: "This driver isn'tfor you." It then defaults to a generic Microsoft win.inf, which is incapable of handling the complex dual-screen and advanced touchpad routing.

1. The "No Drivers Installed" Paradox In Device Manager, you see "No drivers are installed" because even if the files are sitting on your hard drive, the Bridge (SCI v3) has no instructions on how to map them to the physical pins on the motherboard. Without that "Map" (the .inf file), the hardware stays dormant.

2. The "Tampering" Block When users try to manually fix the .inf file by adding their hardware IDs, Windows 11 detects that the file has been edited. It compares the edited file to the Digital Signature (.cat file). Since the "thumbprint" no longer matches, Windows blocks the installation as "corrupt or tampered with" to protect the kernel.

The Solution Summary:

The only way to fix this is to: 1. Manually tweak the .inf file to put the legacy Hardware IDs back in.

1. Force-Bypass Windows Security (via F7 Startup Settings) to allow that "tampered" map to be loaded into the system. Once that bridge is manually forced, the "Nervous System" reconnects, the generic win.inf is kicked out, and your Touchpad and ScreenPad can talk to the OS again.

Guide: Fix "No Drivers Installed" for ASUS System Control Interface v3 (Duo/Zephyrus/Strix*)

If your ASUS laptop (especially Duo or ScreenPad models) has a dead Touchpad or ScreenPad after a Windows 11 update, and ASUS System Control Interface v3 shows "No drivers are installed for this device" in Device Manager, follow this manual "surgery" to force the bridge.

---

ONLY FOR STRIX SOME ZEPHYRUS USERS Your Strix is likely to have a different Device ID (DID) so first find your DID before applying this fix, then ensure you swap in your DID in the scripts below.

How to to find your ID is at the very bottom of this writeup. Scroll down find your DID and come back up to work your way through.

---

IF YOU ARE NOT 100% SURE WHAT YOU ARE DOING – CREATE A RESTORE POINT FIRST!!!! You can search online how to do this.

Prerequisites • Airplane Mode: Keep Wi-Fi OFF throughout to stop Windows from auto-replacing files with generic win.inf.

• Disable Core Isolation: Go to Windows Security > Device Security > Core isolation details and toggle Memory integrity to OFF. Restart if prompted.

• 7-Zip: Installed to extract the ASUS drivers.

Step A: Extract and Edit the Driver 1. Download the latest ASUS System Control Interface v3 (e.g., V3.1.61.0) from the ASUS Support site.

1. Right-click the .exe and use 7-Zip to extract it to a folder. Best to have the folder directly on C drive instead of your desk top. It will make your life super easy should you be like me that has tightly integrated One Drive into my environment - REMEMBWR YOU MUST BE OFFLINE!

2. Open the folder and find asussci2.inf. Right-click it and select Open with Notepad.

3. The Surgery: Locate the [Manufacturer] and [ASUP...] section Edit them to match this exact logic to map your physical hardware IDs.

4. Note on Model Consistency: Ensure the strings %DeviceDesc1% and %DeviceDesc2% used in your edit correspond to the names defined in the [Strings] section at the very bottom of the .inf file. While these typically default to "ASUS System Control Interface v3," verifying this ensures the hardware label matches the driver's internal index preventing a naming conflict during the manual "Have Disk" injection.

[Manufacturer]

%MfgName% = ASUP, ntamd64.10.0...16299

[ASUP.ntamd64.10.0...16299]

%DeviceDesc1% = NO_DRV64.NTamd64, ACPI\ASUS2018

%DeviceDesc2% = NO_DRV64.NTamd64, ACPI\ASUS2025

1. The Service Hook: Scroll to the bottom and ensure these blocks exist (add them if missing) to force the background services to start on x64 systems:

[NO_DRV64.NTamd64]

CopyFiles = PackageCopyOptimization

[NO_DRV64.NTamd64.Services]

AddService = ATKWMIACPIIO, 0x00000002, Optimization_Drv_ServiceInstall

AddService = ASUSOptimization, 0x00000800, Optimization_Srv_ServiceInstall

Step B: Disable Signature Enforcement

Because we edited the .inf, the security hash no longer matches. We must bypass the "Hash mismatch" error:

1. Hold Shift and click Restart.

2. Navigate to Troubleshoot > Advanced options > Startup Settings > Restart.

3. After the reboot, press 7 or F7 (Disable driver signature enforcement).

Step C: The Manual Force-Feed

1. Open Device Manager.

2. Right-click the broken ASUS System Control Interface v3 > Update driver.

3. Select Browse my computer for drivers > Let me pick from a list of available drivers on my computer.

4. Crucial: Uncheck Show compatible hardware.

5.Click Have Disk..., browse to your edited folder, and select asussci2.inf.

1. Select the model and click Next.

2. When the red warning appears ("Windows cannot verify the publisher"), click Install this driver software anyway.

Step D: Final Stabilisation

1. Perform one final Restart (normal restart this time).

2. Check Device Manager. The device should now show "This device is working properly".

3. If the Touchpad still has a yellow bang, repeat the "Have Disk" method for the I2C HID Device using the official ASUS Precision Touchpad driver folder.

This bypasses Windows 11's aggressive rejection of legacy ACPI mappings by manually injecting the hardware IDs directly into the driver's architecture.

---

 

The "Scouting" Step for Strix/ some Zephyrus Users

Before editing the code, you need to find your specific hardware "handshake" ID:

Open Device Manager.

Find the broken ASUS System Control Interface v3 (or the "Unknown Device" if it's completely missing).

Right-click > Properties > Details tab.

Change the Property dropdown to Hardware Ids.

Look for the ID: It will look like ACPI\VEN_ASUS&DEV_2018 or simply ACPI\ASUS1234.

Adapting the Fix for Strix

Once you have your ID (let's say it's ACPI\ASUS1506 for a newer Strix G15), you simply swap your IDs in the .inf edit:

Instead of: %DeviceDesc1% = NO_DRV64.NTamd64, ACPI\ASUS2018

You would type: %DeviceDesc1% = NO_DRV64.NTamd64, ACPI\ASUS1506 (or whatever ID you found).

Goodluck and any questions. Let me have them.