Getting an infinite loop where robo copy tries to move the files "AsIO2.dll, AsIO3.dll, and AsusDownloadLicense.exe" from System 32

Getting an infinite loop where robo copy tries to move the files "AsIO2.dll, AsIO3.dll, and AsusDownloadLicense.exe" from System 32

@ArasakaApart Do you run the script in Admin privilege?

Getting an infinite loop where robo copy tries to move the files "AsIO2.dll, AsIO3.dll, and AsusDownloadLicense.exe" from System 32

@ArasakaApart Do you run the script in Admin privilege?

Yes.

@ArasakaApart, Could you try this test version? deepclean_test.cmd
Since I don't have your environment, I had to create a test version for you. I suspect that AsIO and AsusDownloadLicense are still running on your system. This led to this result. I've made some improvements to address the problems you reported. I hope you will be able to run this version. If it fixes your problem, I will merge it back into this main release.

@ArasakaApart, Could you try this test version? deepclean_test.cmd Since I don't have your environment, I had to create a test version for you. I suspect that AsIO and AsusDownloadLicense are still running on your system. This led to this result. I've made some improvements to address the problems you reported. I hope you will be able to run this version. If it fixes your problem, I will merge it back into this main release.

Seemed to work in my case, thanks!

Epic tool - my computer runs so much better now. Thanks!

You're a legend, thank you

I think you need to also:

sc stop asusgio2
sc stop asusgio3
sc delete asusgio2
sc delete asusgio3

EDITED: Removed the accidental addition of p in the driver names.

I think you need to also:

sc stop asusgpio2
sc stop asusgpio3
sc delete asusgpio2
sc delete asusgpio3

Hi @LeadAssimilator,
I cannot confirm the existence of this service. I tested three of my ASUS devices, and none of them run with this service.
I used the following command:
Get-Service | Where-Object { $_.Name -like "*asus*" }

There are no services associated with asusgpio*.
However, I believe the correct driver name should be:

driverquery | findstr /i "asus"
Asusgio3     Asusgio3               Kernel

The correct name appears to be Asusgio3, not Asusgpio3.
Additionally, since this is a kernel driver rather than a Windows service, we should use pnputil instead of sc commands to manage it.
Conclusion:
Removing the registry entries and deleting the system files should be sufficient to fully clean up the GIO drivers.

I think you need to also:

sc stop asusgpio2
sc stop asusgpio3
sc delete asusgpio2
sc delete asusgpio3

Hi @LeadAssimilator, I cannot confirm the existence of this service. I tested three of my ASUS devices, and none of them run with this service. I used the following command: Get-Service | Where-Object { $_.Name -like "*asus*" }

There are no services associated with asusgpio*. However, I believe the correct driver name should be:

driverquery | findstr /i "asus"
Asusgio3     Asusgio3               Kernel

The correct name appears to be Asusgio3, not Asusgpio3. Additionally, since this is a kernel driver rather than a Windows service, we should use pnputil instead of sc commands to manage it. Conclusion: Removing the registry entries and deleting the system files should be sufficient to fully clean up the GIO drivers.

@allenk Yes, sorry that was my mistake. I had retyped the names and accidentally added the p. It really should have the p in the name (gpio is what the driver does - gio isn't really a thing), but asus removed the p presumably so their driver could fit in 8.3 naming convention. The correct names are as you stated, without the p:

sc stop asusgio2
sc stop asusgio3
sc delete asusgio2
sc delete asusgio3

I disagree with the use of pnputil over sc. Using sc is perfectly fine if not preferred for managing legacy/non-pnp drivers. The above script is already using sc for managing such drivers anyway, so why change it?

Take IOMap as an example. It is a legacy/non-pnp driver that is both stopped and deleted via sc by the script. If deleting the registry entries and files was sufficient, then why is IOMap explicitly stopped and deleted via sc? The answer is because it isn't sufficient! The driver needs stopped first if it is running at the very least. Once stopped, sure you could delete it via the registry, but why do that when sc can do the job easier.

The above, corrected (sorry about that again) 4 sc commands should still be added to the script or else it will continue to fall short of actually cleaning everything up.

Hi @LeadAssimilator,

Thanks again for your feedback! I’ve reviewed your suggestions and I agree with your recommendation to include the sc stop and sc delete commands for both asusgio2 and asusgio3. I’ve now added them to the script.

sc query asusgio3

SERVICE_NAME: asusgio3
        TYPE               : 1  KERNEL_DRIVER
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

I change the sc query type from service to all and confirmed your suggestion.

In addition, I also made some updates to improve the cleanup coverage by stopping and removing a few more related ASUS services that were previously missing. This should make the cleanup process more complete and reliable.

Really appreciate your input in helping improve this tool!

Best regards,
Allen

This is fkn hilarious, thanks for the laugh

2025/08/15 11:22:30 ERROR 32 (0x00000020) Deleting Source Directory C:\Windows\System32\
The process cannot access the file because it is being used by another process.
True

This is fkn hilarious, thanks for the laugh

2025/08/15 11:22:30 ERROR 32 (0x00000020) Deleting Source Directory C:\Windows\System32\
The process cannot access the file because it is being used by another process.
True

Hi @dmiller423,
Actually, don't worry—it just looks alarming. But it won't actually happen. Of course, I've improved this part anyway, so it doesn't seem so nerve-wracking!

My keyboard and mouse stopped working after running two times and a restart of the cmd🥲

Thanks for writing this and making it available. I moved my Windows from running on bare metal (ASUS ROG) to a KVM and these utilities were causing me lots of problems.

My keyboard and mouse stopped working after running two times and a restart of the cmd🥲

Same here how can we fix this please it was working great up until recent revisions i have total loss of Keyboard & mouse now, Nothing works even a different plugged in keyboard or mouse!! This has bricked my system since i cannot use a keyboard or mouse

Hi @mem1991 , @CutiePika

Sorry I didn't notice this comment until now. I'm guessing you're referring to the ASUS laptop platform.
Here, I provide a test version and I remove ACSEVirtualBus and ACSEHIDRemap clean up.
https://gist.github.com/allenk/9fa00e6230937b708865b8159f112ed2

I wonder if this removal caused the issue. It's an ASUS HID REMAP with VirtualBus.
Logically, it should have been reinstalled along with ARMOURY CRATE.

Reinstall the drivers,
In "C:\Program Files\ASUS\ARMOURY CRATE SE Controller Emulator" Provide these drivers
ACSEVirtualBus.inf ACSEHIDRemap.inf Right-click => Install

If you can't find it, try searching. C:\Windows\System32\DriverStore\FileRepository to install the driver.
C:\Windows\System32\DriverStore\FileRepository\acsehidremap.inf_amd64_8e593d7bf03c7be4\acsehidremap.inf
C:\Windows\System32\DriverStore\FileRepository\acsevirtualbus.inf_amd64_bab6970ada0053f8\acsevirtualbus.inf

I look forward to your feedback. If it is positive, I will remove the removal of these two components. This appears to be necessary for certain devices.

Hi @mem1991 , @CutiePika

Sorry I didn't notice this comment until now. I'm guessing you're referring to the ASUS laptop platform. Here, I provide a test version and I remove ACSEVirtualBus and ACSEHIDRemap clean up. https://gist.github.com/allenk/9fa00e6230937b708865b8159f112ed2

I wonder if this removal caused the issue. It's an ASUS HID REMAP with VirtualBus. Logically, it should have been reinstalled along with ARMOURY CRATE.

Reinstall the drivers, In "C:\Program Files\ASUS\ARMOURY CRATE SE Controller Emulator" Provide these drivers ACSEVirtualBus.inf ACSEHIDRemap.inf Right-click => Install

If you can't find it, try searching. C:\Windows\System32\DriverStore\FileRepository to install the driver. C:\Windows\System32\DriverStore\FileRepository\acsehidremap.inf_amd64_8e593d7bf03c7be4\acsehidremap.inf C:\Windows\System32\DriverStore\FileRepository\acsevirtualbus.inf_amd64_bab6970ada0053f8\acsevirtualbus.inf

I look forward to your feedback. If it is positive, I will remove the removal of these two components. This appears to be necessary for certain devices.

Thankyou for the reply the issue is how can I reinstall drivers if I’ve lost total keyboard and mouse input I can’t do anything in windows itself ? It’s literally broken doing anything in windows desktop itself, Safe mode is also the same no Input,

@mem1991

I'm sorry you're experiencing this issue. Let's try to recover your system now:
Troubleshooting (No keyboard/mouse after cleanup) — try these options in order

Try external USB input first

• Plug in a wired USB-A keyboard and mouse (avoid hubs/docks/adapters if possible).
• Try different USB ports (prefer USB-A / USB 2.0 ports if available).
• Check if the keyboard works in BIOS/UEFI (e.g., press F2/Del during boot).
• If it works in BIOS but not in Windows, this is likely a Windows driver/filter issue and can be repaired.

Try Windows Recovery (WinRE) + System Restore

• Enter WinRE (Recovery Environment):
• Power on → when Windows starts loading/spinning, hold power button to force off.
• Repeat 2–3 times until you see Automatic Repair / Recovery options.
• Go to: Troubleshoot → Advanced options → System Restore
• Pick a restore point before running the cleanup tool.

If no restore point / restore doesn’t help: Repair using a Windows install USB (NOT reinstall)

• On another PC, create a Windows 10/11 installation USB.
• Boot the affected PC from the USB.
• Choose Repair your computer (do NOT click Install).
• Go to: Troubleshoot → Advanced options → Command Prompt
• Find the Windows drive letter (often not C: in WinRE):
• Run: diskpart → list vol → identify the Windows volume → exit
  Then reinstall the drivers offline from DriverStore (replace D: with your Windows drive letter, and adjust folder names if different):

dir D:\Windows\System32\DriverStore\FileRepository\acse*.inf* /ad

dism /image:D:\ /Add-Driver /Driver:"D:\Windows\System32\DriverStore\FileRepository\acsevirtualbus.inf_amd64_*\acsevirtualbus.inf"
dism /image:D:\ /Add-Driver /Driver:"D:\Windows\System32\DriverStore\FileRepository\acsehidremap.inf_amd64_*\acsehidremap.inf"

• Reboot and test input devices again.
  Note: If BitLocker is enabled, WinRE may ask for a recovery key.

@mem1991,

Also note that in the driver installation command:

dism /image:<WindowsDriveLetter>:\ ...

This refers to the original system location. It is typically D:\ because C:\ is being used by the USB PE.

@mem1991,

Also note that in the driver installation command:

dism /image:<WindowsDriveLetter>:\ ...

This refers to the original system location. It is typically D:\ because C:\ is being used by the USB PE.

Resolved with "dism /image:c:\ /add-driver /driver:d:\ /recurse" in WinRE from bootable USB, Opened CMD from WinRE replaced with my systems Drive letter :) rebooted and voila! :)

This was the issue for no Keyboard & Mouse specifically the "acsevirtualbus.inf" & "acsehidremap.inf" was the root cause for the loss,

Other than that back to normal :) Thankyou

⚠️ IMPORTANT / Emergency Recovery

@mem1991 ,
Confirmed root cause (ASUS laptops): Removing ACSEVirtualBus / ACSEHIDRemap can break the HID/keyboard/mouse stack on some models, causing total loss of input (including external USB devices in Windows).
Fix: Boot into WinRE and reinstall the drivers offline with DISM.
Starting from the latest revision, I will not remove these components by default.

Emergency Recovery: No keyboard/mouse after cleanup (WinRE + DISM)

1. Create a Windows 10/11 bootable USB on another PC.
2. Boot from the USB → choose Repair your computer (NOT Install).
3. Go to Troubleshoot → Advanced options → Command Prompt.
4. Identify drive letters:
   • In WinRE, your offline Windows is often C: (but not always), and the USB/PE is often X:.
   • Verify by running: dir C:\Windows (try D:\Windows, E:\Windows if needed).
5. Reinstall drivers (example: Windows is on C:, driver files are on D:)

Search Drivers:
dir D:\Windows\System32\DriverStore\FileRepository\acse*.inf* /ad

Install Driers:
dism /image:D:\ /Add-Driver /Driver:"D:\Windows\System32\DriverStore\FileRepository\acsevirtualbus.inf_amd64_*\acsevirtualbus.inf"
dism /image:D:\ /Add-Driver /Driver:"D:\Windows\System32\DriverStore\FileRepository\acsehidremap.inf_amd64_*\acsehidremap.inf"
dism /image:c:\ /add-driver /driver:d:\ /recurse