Cannot find a process with the process identifier 4704

[arthurcruz1]

I am experiencing the an error during the Install ASUS Setup step

Get-Process : Cannot find a process with the process identifier 4704.
At C:\Users\adm_cruz\Downloads\Asus-Setup-Tool\Asus Setup Tool\Source\setup.psm1:601 char:18
+         $Setup = Get-Process -Id $Setup.Id
+                  ~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (4704:Int32) [Get-Process], ProcessCommandException
    + FullyQualifiedErrorId : NoProcessFoundForGivenId,Microsoft.PowerShell.Commands.GetProcessCommand


Cannot bind argument to parameter 'Id' because it is null.

[codecrafting-io]

This is related to AiSuite3 quick setup initialization. It seems that the process doesn't run long enough (fails or is prevented from starting?) causing this error, which I couldn't reproduce until now. Does this persist after a reboot? Can you run the AiSuite3 setup? Just launching it will install basic services and drivers that is required for a proper AuraSync, and you don't need to install AiSuite3. Meanwhile, I will make a patch to handle this situation to fail properly.

[codecrafting-io]

I made some changes to the Set-ASUSServices. Replace the files below inside Source folder, by downloading them (right click and save link as)

• settings.json - SHA256: 7111AD3289FB09EAB4CFFEB0C44E69A5C1DF109E95B2DF4EE46BAFD2A3269BC0
• setup.ps1 - SHA256: 9CA540BD168A73110583EE6E37BBBE05571E5A3FD2879A2022EF0AE2A10BF309

This may not fix your issue, but at least will have better handling when AiSuite3 stops unexpectedly

[arthurcruz1]

The error persists after a reboot.

After replacing the files:

Failed to set Asus service. AiSuite3 quick setup failed to launch

I don't need AiSuite3 but was able to run the setup in the Apps folder. As I workaround I ran the AuraSync setup in the folder.

[codecrafting-io]

Sorry, but I really can't reproduce the situation. Through PowerShell it seems that AiSuite3 setup does not start or is killed earlier. Not sure why. AiSuite3 is used to install ASUS basic services before installing AuraSync, which is done by simply running AiSuite3 setup. It doesn't install AiSuite3 itself. For now, unfurtonatatly, I will mark this as "wontfix"

[codecrafting-io]

I made another small tweak in the setup.psm1 file to improve the Start-Process failures and detection when the AiSuite3 window appears (indicating that ASUS basic services have been successfully set up). Still, it probably won't fix your problem 😔, just tighten up the handling of AiSuite3 startup. You can try it anyway.

• setup.psm1 - SHA256: 2DDAF76BD4897047F1FB7591DB48FC700DAACF9AA5F4F5E8E51737107E280E09

If you could attach the most recent log file, it may help to understand why AiSuite3 Setup does not start with PowerShell

[codecrafting-io]

All of these changes have been fully integrated into v0.9.0

[codecrafting-io]

For those still having the issue, try version v0.7.1 and see if it works. This may be related to newer ASUS services introduced in 0.8.0. Still investigating

[ExtremeFiretop]

I just had this issue. Was related to having Windows Defender Device Security enabled. Specifically "Core isolation" settings .
Once I disabled memory integrity and kernel-mode enforced stack protection the error went away.

[ExtremeFiretop]

Sorry; correction, the reason the error went away was because i opted to try to install AiSuite3 just to see what it did.
I tried again just now with Defender Security disabled, and still got the same error as long as I selected to not install AiSuite 3.

If I select to install it, no errors are shown.

[codecrafting-io]

The decision to install or not install AiSuite3 is not the cause, more likely something is blocking the setup from running. Unfortunately I haven't been able to reproduce the problem on several systems I've tried. The AiSuite3 setup is used even if you don't choose to install it, due to the quick setup for services and drivers, although the application itself only installs it if you choose to at the beginning. You can try version 0.7.1 to use older ASUS services, but I don't think it will help.

[ExtremeFiretop]

The decision to install or not install AiSuite3 is not the cause, more likely something is blocking the setup from running. Unfortunately I can't reproduce the problem on several systems I've tried. The AiSuite3 setup is used even if you don't choose to install it, due to the quick setup for services and drivers, although the application itself only installs it if you choose to at the beginning. You can try version 0.7.1 to use older ASUS services, but I don't think it will help.

No point in trying, even when installed it didn't function correctly for me unfortunately. Kept saying the service could not be started.

[codecrafting-io]

The decision to install or not install AiSuite3 is not the cause, more likely something is blocking the setup from running. Unfortunately I can't reproduce the problem on several systems I've tried. The AiSuite3 setup is used even if you don't choose to install it, due to the quick setup for services and drivers, although the application itself only installs it if you choose to at the beginning. You can try version 0.7.1 to use older ASUS services, but I don't think it will help.

No point in trying, even when installed it didn't function correctly for me unfortunately. Kept saying the service could not be started.

I am sorry if you are experiencing these problems, but I have not been able to reproduce the situation. For future reference and further investigation, if possible, please answer the following questions:

1. Motherboard model and BIOS version:
2. Windows build version (e.g. Windows 11 22631.4391):
3. Attach the latest log file
4. Print screen of the issue

[ExtremeFiretop]

The decision to install or not install AiSuite3 is not the cause, more likely something is blocking the setup from running. Unfortunately I can't reproduce the problem on several systems I've tried. The AiSuite3 setup is used even if you don't choose to install it, due to the quick setup for services and drivers, although the application itself only installs it if you choose to at the beginning. You can try version 0.7.1 to use older ASUS services, but I don't think it will help.

No point in trying, even when installed it didn't function correctly for me unfortunately. Kept saying the service could not be started.

I am sorry if you are experiencing these problems, but I have not been able to reproduce the situation. For future reference and further investigation, if possible, please answer the following questions:

1. Motherboard model and BIOS version:
2. Windows build version (e.g. Windows 11 22631.4391):
3. Attach the latest log file
4. Print screen of the issue

Sorry for the lack of helpful feedback in the last reply, I was getting frustrated at the time after spending more hours than I want to admit on this. I'm willing to try again after cooling off a bit and provide some useful feedback this time, don't give up on me just yet lol!

I used to be able to control my motherboard RGB using Aura Sync and iCue back in the day, then Armoury crate came along and that worked for me as well to control the RGB with iCue. At some point it stopped working and I went to ASUS first, they told me my motherboard isn't supported by Armoury crate, which is how I started looking for alternative solutions like this repo.

1. ASUS Prime X370-Pro with the latest BIOS that patches Sinkclose found here:
   https://www.asus.com/supportonly/prime%20x370-pro/helpdesk_bios/

2. Windows 11 24H2 Build 26100.2161
   

3. Log file below:
   2024-10-27.log

4. Screenshots below:
   Dynamic Lighting Disabled in Windows:
   
   Windows Defender Core Isolation Disabled in Windows
   
   Installation Process:
   
   
   Error Message:
   

[ExtremeFiretop]

3. Attach the latest log file

Based on the log file I see these of possible interest:

2024/10/27 01:44:47 [INFO]: Stopping driver 'Asusgio3'
2024/10/27 01:44:55 [DEBUG]: caught exception 'Microsoft.PowerShell.Commands.ServiceCommandException' at 'H:\Joel\Downloads\Asus-Setup-Tool\Source\utils.psm1:415'
Service 'Asusgio3 (Asusgio3)' cannot be stopped due to the following error: Cannot stop Asusgio3 service on computer '.'.

2024/10/27 02:01:40 [INFO]: Unregister tasks
2024/10/27 02:01:41 [ERROR]: caught exception 'System.IO.FileNotFoundException' at 'H:\Joel\Downloads\Asus-Setup-Tool\Source\setup.psm1:366'
The system cannot find the file specified. (Exception from HRESULT: 0x80070002)

2024/10/27 02:02:09 [INFO]: Removing 'C:\WINDOWS\SysWOW64\drivers\AsUpIO.sys'
2024/10/27 02:02:09 [ERROR]: caught exception 'System.UnauthorizedAccessException' at 'H:\Joel\Downloads\Asus-Setup-Tool\Source\utils.psm1:263'
Cannot remove item C:\WINDOWS\SysWOW64\drivers\AsUpIO.sys: Access to the path 'C:\WINDOWS\SysWOW64\drivers\AsUpIO.sys' is denied.

I did have to run it twice, the first time gave me this error:

[ExtremeFiretop]

@codecrafting-io

I noticed in the logs it was having trouble stopping the Asusgio3 service. Turns out every other ASUS service had to be stopped first. Then I was able to stop it with: Stop-Service -Name "Asusgio3" -Force

After the "LightingSevice", "AsusCertService" and "AsComSvc" service was stopped. I was able to stop the Asusgio3 service.

I also was only able to manually delete the following file: C:\WINDOWS\SysWOW64\drivers\AsUpIO.sys while using a safe mode with minimal drivers loaded.

Edit:
Even after reinstalling after confirming that it was properly cleaned up, and downgrading my BIOS, I still have the issue.

[codecrafting-io]

@ExtremeFiretop Thanks for the response. Let's try to break this down:

1. Looking at the log, the execution seems to have failed to set up basic services with an error that originated this issue, but on the second try it worked. This was because you were able to stop Asusgio3 manually?
2. The setup tries to stop ASUS services first and then the drivers, which sometimes fails, which can't happen. The script then proceeds to delete files, which in the case of system drivers is ignored if it fails, as Windows sometimes doesn't allow it, but they remain in a "degraded" state. After a reboot they will be gone, but normally Windows will allow reinstallation in this state.
3. I find it strange that services like "LightingService" are still running in the driver removal state. To remove a service, the setup first sends a Stop command with a NoWait parameter, then waits manually for 7 seconds, then sends another Stop command that waits, then removes with Remove-CimInstance or Remove-Service, then tries to remove again with sc.exe, and finally uses Stop-Process. So there are multiple attempts and a reasonable amount of time to wait, but it seems that this can still happen, which I would say is abnormal. However, I think I can push Stop-Process before removal and add a check to see if they are actually stopped and if not throw an error.
4. The error "AuraService is currently unavailable" is probably due to LightingService failing to start or be installed, which can happen and the setup won't show any errors unfortunately. Sometimes this requires running AsusServiceSetup manually to see if the "uninstall button" appears. In your case, it could be the failure of the Asusgio3 driver, which could be the cause of the AiSuite3 error.
5. I noticed that you selected the older AuraSync, have you tried the new option? This may not work as it could be a driver issue which is handled by the AiSuite3 quick setup instead, but you can try.
6. Lastly, I have not done a proper test with Windows 11 24H2, but I am not sure if this would interfere with Asusgio3 as this is the latest driver provided by ASUS and used in ArmouryCrate. That's why I think you could try older versions, like v0.6.0. You may be able to simply copy the patches folder to a newer setup version.
7. The Windows Dynamic Lighting thing will only interfere if your BIOS supports it, so if your BIOS doesn't have this option, don't worry. Usually this is in the Advanced tab > Onboard Devices

[ExtremeFiretop]

@ExtremeFiretop Thanks for the response. Let's try to break this down:

1. Looking at the log, the execution seems to have failed to set up basic services with an error that originated this issue, but on the second try it worked. This was because you were able to stop Asusgio3 manually?

1. No, no change between the first and second try on my part, other than trying again. It was the same behavior as when I first commented, I thought it was Windows Defender first, then I thought it was related to selecting AiSuite, but basically every other try it would work, so naturally whatever I tried changing between the "fail" and the second try, I would think was the "solution" but it's clear now it's just failing the first time and working correctly the second time almost every time.

My gut tells me it's if you don't accept this prompt in a timely manner:

It always happens around this step, seems to me if I wait a minute or two before selecting "y" and then wait a minute or two with the module window open, that I see the error.

2. The setup tries to stop ASUS services first and then the drivers, which sometimes fails, which can't happen. The script then proceeds to delete files, which in the case of system drivers is ignored if it fails, as Windows sometimes doesn't allow it, but they remain in a "degraded" state. After a reboot they will be gone, but normally Windows will allow reinstallation in this state.

2. Okay so what I am understanding is the errors of the drivers I couldn't remove is more or less okay, and not something to worry about. I did go ahead and cleaned them up anyways manually (booting into safe mode) but the errors in the logs are transient and can be ignored?

3. I find it strange that services like "LightingService" are still running in the driver removal state. To remove a service, the setup first sends a Stop command with a NoWait parameter, then waits manually for 7 seconds, then sends another Stop command that waits, then removes with Remove-CimInstance or Remove-Service, then tries to remove again with sc.exe, and finally uses Stop-Process. So there are multiple attempts and a reasonable amount of time to wait, but it seems that this can still happen, which I would say is abnormal. However, I think I can push Stop-Process before removal and add a check to see if they are actually stopped and if not throw an error.

3. Keep in mind when I mentioned this comment:

I noticed in the logs it was having trouble stopping the Asusgio3 service. Turns out every other ASUS service had to be stopped first. Then I was able to stop it with: Stop-Service -Name "Asusgio3" -Force

It was after the script had completed successfully in the above screenshots, the Aura app was giving me errors about the service, but it was installed and running. I was just trying to clean up manually what I was seeing in the logs before trying again, since I also knew that Asusgio3 was the newer version of Asusgio2 and probably came from Armoury crate, I figured I'd manually clean up before trying again. I noticed that I wasn't able to stop it myself manually in Powershell until stopping those other services.

4. The error "AuraService is currently unavailable" is probably due to LightingService failing to start or be installed, which can happen and the setup won't show any errors unfortunately. Sometimes this requires running AsusServiceSetup manually to see if the "uninstall button" appears. In your case, it could be the failure of the Asusgio3 driver, which could be the cause of the AiSuite3 error.

4. I confirmed it was installed and started as SYSTEM when I was getting the error. I manually tried installing the GlckIODrvSetup.exe and the AuraServiceSetup.exe without any success, the error continued.

5. I noticed that you selected the older AuraSync, have you tried the new option? This may not work as it could be a driver issue which is handled by the AiSuite3 quick setup instead, but you can try.

5. I tried it 4 or 5 days ago on my first comments, it did not work any better sadly.
   But I did not try it last night. I can try it again if you would like, please advise.

6. Lastly, I have not done a proper test with Windows 11 24H2, but I am not sure if this would interfere with Asusgio3 as this is the latest driver provided by ASUS and used in ArmouryCrate. That's why I think you could try older versions, like v0.6.0. You may be able to simply copy the patches folder to a newer setup version.

6. Please provide exact steps to patch the newer setup manually, and I'll gladly give it a try :)
   Also I noticed above you mentioned v0.7.1? Please advise of the extact version to try v0.6.0 or v0.7.1

7. The Windows Dynamic Lighting thing will only interfere if your BIOS supports it, so if your BIOS doesn't have this option, don't worry. Usually this is in the Advanced tab > Onboard Devices

7. Last I checked my BIOS had an option to enable onboard RGB and disable it, and that was pretty much it, I wasn't aware the BIOS could have more control than that. I'll reboot to double check my specific situation.

[ExtremeFiretop]

@codecrafting-io

Find attached BIOS options enabled under Advanced and Onboard Devices

[codecrafting-io]

Your bios/motherboard does not have the option for Windows Dynamic Lighting (WDL), so no support and enabling or disabling WDL should not interfere. The setting "RGB Led Lighting should be on".

Okay so what I am understanding is the errors of the drivers I couldn't remove is more or less okay, and not something to worry about. I did go ahead and cleaned them up anyways manually (booting into safe mode) but the errors in the logs are transient and can be ignored?

Yes. The driver removal errors can be more or less ignored, as Windows may not allow removal at the moment, but they will be marked as degraded and can be replaced even without a reboot (but recommended).

My gut tells me it's if you don't accept this prompt in a timely manner:

Time should have no effect here. There's no timeout for the window. Removing the AuraSync modules does not change anything in the AiSuite3 files, so it should not be the reason why it works the second time, most likely the first time it runs partially but fails and the second time it runs successfully. There are log files for this in C:\ProgramData\ASUS\ARMOURY CRATE Diagnosis\install.

Another thing is to look in the C:\Program Files (x86)\LightingService folder. Sometimes modules fail to initialise and so does the service. The older version of AuraSync does not create a log file, but the new version does. You can also try to install all modules, which usually takes more time for the modules to fully initialise (the service says it's running, but it's still initialising, so AuraSync takes longer to open).

As for trying older versions, I mentioned v0.7.1 because that was for the change to the AXSP service (ASUS Com), but in your case the problem seems to be more related to Asusgio3, so that's why v0.6.0. I haven't tested this, but I think it should work normally if you try the v0.6.0 patches in v0.10.0 setup (you can also try v0.6.0, but there is no log system). Here are the steps:

1. Download v0.6.0 and v0.10.0.
2. Delete the v0.10.0 patches folder.
3. Copy the patches folder from v0.6.0 to v0.10.0
4. Replace lock.jsonc to this file (will update the integrity list): lock.jsonc
5. Edit the file setup.psm1 (v0.10.0) line 52 and update the hash to 571C6EE23C112DB6C0A8F13D3E01F1C0D2A2E0E0684C983672B5FBE4661952AE like below:

    $LockSettings.IntegrityList | Add-Member -Type NoteProperty -Name "..\\Source\\lock.jsonc" -Value "571C6EE23C112DB6C0A8F13D3E01F1C0D2A2E0E0684C983672B5FBE4661952AE"

Of course, you can also just try out v0.6.0

[ExtremeFiretop]

Your bios/motherboard does not have the option for Windows Dynamic Lighting (WDL), so no support and enabling or disabling WDL should not interfere. The setting "RGB Led Lighting should be on".

Great, so just to be 100% clear moving forwards, I will be keeping my motherboard BIOS as "ENABLED" as seen above unless otherwise directed.

but in your case the problem seems to be more related to Asusgio3, so that's why v0.6.0. I haven't tested this, but I think it should work normally if you try the v0.6.0 patches in v0.10.0 setup (you can also try v0.6.0, but there is no log system). Here are the steps:

1. Download v0.6.0 and v0.10.0.
2. Delete the v0.10.0 patches folder.
3. Copy the patches folder from v0.6.0 to v0.10.0
4. Replace lock.jsonc to this file (will update the integrity list): lock.jsonc
5. Edit the file setup.psm1 (v0.10.0) line 52 and update the hash to 571C6EE23C112DB6C0A8F13D3E01F1C0D2A2E0E0684C983672B5FBE4661952AE like below:

    $LockSettings.IntegrityList | Add-Member -Type NoteProperty -Name "..\\Source\\lock.jsonc" -Value "571C6EE23C112DB6C0A8F13D3E01F1C0D2A2E0E0684C983672B5FBE4661952AE"

I've done all the above steps and will attempt to run now and provide results and log files:

There are log files for this in C:\ProgramData\ASUS\ARMOURY CRATE Diagnosis\install.
Another thing is to look in the C:\Program Files (x86)\LightingService folder.

Give me a bit of time as you said this is a bit of a slow process to install all the modules. I am starting with the same options (no AISuite, no LiveDash, and the oldest less bloated installer (option 2)

[ExtremeFiretop]

@codecrafting-io

So far, the install went well on the first try. No need to try a second time with this attempt when installing all the modules (option 2)

Log files attached:
ASIO3.log
2024-10-27.log

Nothing in C:\Program Files (x86)\LightingService as you expected since this is the older installer for now.
Will attempt to reboot and advise before I make any other changes.

[ExtremeFiretop]

@codecrafting-io

Still the same issue as found below:

And below is the state of the services (running):

I'm willing to try option 1, instead of 2, but I'll let you review the logs and provide feedback before I try anything more.

[codecrafting-io]

@ExtremeFiretop Try the new version of AuraSync and post the logs inside C:\Program Files (x86)\LightingService . This is most likely related to LightingService. Regarding the AiSuite3 quick setup, it's possible that the older Asusgio3 version may cause less problems for your system during installation.

[ExtremeFiretop]

Regarding the AiSuite3 quick setup, it's possible that the older Asusgio3 version may cause less problems for your system during installation.

@codecrafting-io Okay so I am still running the modified version of the v0.10.0 with the v0.6.0 patches as you described. Nothing changed since the last tests except I selected option 1 and cleared the log files before trying.

@ExtremeFiretop Try the new version of AuraSync and post the logs inside C:\Program Files (x86)\LightingService .

Find below logs:

2024-11-03.log
ASIO3.log

There is no log file located at: C:\Program Files (x86)\LightingService .
But I did find a log file located here: C:\ProgramData\ASUS\ARMOURY CRATE Diagnosis\LightingService found below:
LightingService.log

[ExtremeFiretop]

@codecrafting-io

Same issue post-reboot:

What does the option to start with Windows do in the script? What if I don't start with Windows and only start manually?

[ExtremeFiretop]

@codecrafting-io

I'm seeing multiple entries indicate that the lastprofile.xml file is either non-existent or corrupted?

[AuraSettingStore::LoadLastProfile] Return false.
Unable to comply due to the inexistence or the damage of lastprofile.xml !!!

And some device failures?

The enumerated device count of the hal ==> 0
Rolling back 2 ...
Creating a hal ... [GUID] =======================

I did run it as Admin, I do also have Corsair iCUE still installed. Could this be an issue?

[codecrafting-io]

What does the option to start with Windows do in the script? What if I don't start with Windows and only start manually?

This adds an option to manually start these services so that they only start when you open the application. Sometimes they may fail to do so. This option was created to keep the number of processes running on the system as low as possible, since many devices don't need them to maintain RGB settings, just to set the color and effects once. Starting it manually won't change anything for your situation.

I'm seeing multiple entries indicate that the lastprofile.xml file is either non-existent or corrupted?

The lastprofile.xml is where the RGB settings are stored. Program logs and internal messages usually use dramatic language. In your case, it's simply not loading the settings because there was never a previous profile, which is expected, normal behavior. This file is only created when a device is detected and LightingService is properly initialized.

--

Looking at the LightingService log file, I think I figured out what is going on. When LightingService detects a compatible device (Hal - Hardware Abstraction Layer) or fails to initialize these modules, this message appears when AuraSync is started. In your case, all modules were initialized because the log file did not hang at that stage, but no device was detected. I was able to simulate this by selecting no module, which resulted in the same message.

So my conclusion is that both the new and the old AuraSync probably does not support your motherboard. But there might be a last hope. During setup, select the older AuraSync and install LiveDash as well. Installing LiveDash will patch the LightingService with an older file MBIsSupported.dll from an even older AuraSync 1.07.60 instead of 1.07.66. This file is mainly responsible for motherboard detection. The 1.07.60 was not used because it is not available on the ASUS website.

[ExtremeFiretop]

What does the option to start with Windows do in the script? What if I don't start with Windows and only start manually?

This adds an option to manually start these services so that they only start when you open the application. Sometimes they may fail to do so. This option was created to keep the number of processes running on the system as low as possible, since many devices don't need them to maintain RGB settings, just to set the color and effects once. Starting it manually won't change anything for your situation.

I'm seeing multiple entries indicate that the lastprofile.xml file is either non-existent or corrupted?

The lastprofile.xml is where the RGB settings are stored. Program logs and internal messages usually use dramatic language. In your case, it's simply not loading the settings because there was never a previous profile, which is expected, normal behavior. This file is only created when a device is detected and LightingService is properly initialized.

--

Looking at the LightingService log file, I think I figured out what is going on. When LightingService detects a compatible device (Hal - Hardware Abstraction Layer) or fails to initialize these modules, this message appears when AuraSync is started. In your case, all modules were initialized because the log file did not hang at that stage, but no device was detected. I was able to simulate this by selecting no module, which resulted in the same message.

So my conclusion is that both the new and the old AuraSync probably does not support your motherboard. But there might be a last hope. During setup, select the older AuraSync and install LiveDash as well. Installing LiveDash will patch the LightingService with an older file MBIsSupported.dll from an even older AuraSync 1.07.60 instead of 1.07.66. This file is mainly responsible for motherboard detection. The 1.07.60 was not used because it is not available on the ASUS website.

Thanks for the advice.

I'll try it in the morning and advise the results. Seems that controlling the RGB on the board is becoming harder and harder to do as time goes on...

I should mention in the test tonight with the patched v0.10.0 i also did not have to run it twice to install, it ran all on the first try, in case that's valuable information to you.

[ExtremeFiretop]

@codecrafting-io

I tried your suggestion and got all this:

Even thhough Defender core isolation is disbled.

[ExtremeFiretop]

It's a never ending loop of popups! Yayy!

[ExtremeFiretop]

1. I've now completed Disabled Defender (AV, Firewall, Core Isolation, App Protection, etc)
   

2. Completed uninstalled Corsair iCue 5.
   It gave an error what it wasn't able to remove all the modules.
   Logs can be found here: C:\ProgramData\Corsair\iCUE5 Main Installer\logs
   2024-11-03_10-20-42.log
   2024-11-03_10-20-47.log

3. Manually deleted: C:\ProgramData\Corsair and C:\Program Files\Corsair

4. Rebooted the device and re-tried your suggestion of the oldest Aura Service with LiveDash.

5. No errors this time or popups, it just installed like usual.

6. When prompted to start the device with windows, I select selected "no" to start manfully instead. I realize this loads doesn't keep it running as you described, but it should still run when the app is opened manually.

7. This is the 4th time running the script without needing to run it twice in row. Still working on the first try with this setup.
   

[ExtremeFiretop]

@codecrafting-io

Post-reboot I clicked on Aura and it started the service but the app never opened. It also never gave the error I usually get about the service being unavailable. It just did nothing...

Based on the warning in the above screenshot that reboot is required for the AiSuite3; I went into the Apps\AiSuite3 folder and ran: AsusSetup.exe

[ExtremeFiretop]

Post-reboot I get the same error again after installing AiSuite3:

[ExtremeFiretop]

@codecrafting-io

The 1.07.60 was not used because it is not available on the ASUS website.

Just an FYI that I seem to be able to download it from: https://dlcdnets.asus.com/pub/ASUS/mb/14Utilities/Lighting_Control_1.07.60.zip

I will try again with this version.

[ExtremeFiretop]

I give up for today, before I start getting frustrated again; it's not working.
More or less the same situation.

[codecrafting-io]

I understand your frustration. I find it curious that in your Windows show these drivers popups. Anyway, you can also try to install the modified v0.10.0 (select old Aura) and just replace the MBIsSupported.dll in the C:\Program Files (x86)\LightingService folder. You will need to stop the service first. If none of this works, you can look at this subreddit https://www.reddit.com/r/ASUS/comments/eh1ouk/asus_aura_archived_versions/ and try older versions, but you will have to apply the patches manually. To apply the patches manually, follow these steps

1. Download one of the older versions
2. Copy the DrvResource folder inside the patches folder to the AiSuite3 setup folder. Just replace the files
3. Run AiSuite3. Once the window opens, the basic drivers should be installed. You can see this in the Services panel. Close the window (you don't need to install AiSuite3).
4. Copy the AXSP folder inside Patches\AiSuite3\DrvResource to the same folder of the selected AuraSync. It is probably in the aac folder.
5. Install AuraSync manually by launching the setup.
6. Test if you can open the application. If not, try another version and repeat steps 4-6.

I really hope this helps, otherwise I am not sure what else can be done. Thanks for the feedback on the original question of this issue. I would just ask one thing. Can you try the default v0.10.0 again? If the AiSuite3 error happens again, it's definitely the ASIO3 version that can cause problems on some machines.

[ExtremeFiretop]

I understand your frustration. I find it curious that in your Windows show these drivers popups.

Seems some ASUS drivers aren't deemed safe by whatever standard defender uses. I believe the driver's need to be updated to support core isolation but I have that disabled so I'm not sure why the popups came up.

Anyway, you can also try to install the modified v0.10.0 (select old Aura) and just replace the MBIsSupported.dll in the C:\Program Files (x86)\LightingService folder. You will need to stop the service first. If none of this works, you can look at this subreddit https://www.reddit.com/r/ASUS/comments/eh1ouk/asus_aura_archived_versions/ and try older versions, but you will have to apply the patches manually. To apply the patches manually, follow these steps

1. Download one of the older versions
2. Copy the DrvResource folder inside the patches folder to the AiSuite3 setup folder. Just replace the files
3. Run AiSuite3. Once the window opens, the basic drivers should be installed. You can see this in the Services panel. Close the window (you don't need to install AiSuite3).
4. Copy the AXSP folder inside Patches\AiSuite3\DrvResource to the same folder of the selected AuraSync. It is probably in the aac folder.
5. Install AuraSync manually by launching the setup.
6. Test if you can open the application. If not, try another version and repeat steps 4-6.

I really hope this helps, otherwise I am not sure what else can be done.

I appreciate you trying to solve this issue with me. I realize it's not your fault. Your tool is more or less just giving us a clean slate with a few patches to help the software run correctly. I was hoping that the older versions of Aura would work correctly but it seems like this software was holding on by a thread and maybe something in windows or later BIOS/firmware upgrades broke the old software and I'm not supported by Armoury Crate.

it seems in my situation I'm in-between a rock and a hard place. I realize the board is getting old, but it still runs a 5950X so I really don't see a reason to go to AM5 yet. I'll give it a try tonight and advise.

Thanks for the feedback on the original question of this issue. I would just ask one thing. Can you try the default v0.10.0 again? If the AiSuite3 error happens again, it's definitely the ASIO3 version that can cause problems on some machines.

Absolutely. I can try the default again and see if the error happens again, with the patched version it never showed up in the 4 or 5 tests I did. If it shows up again I would have to agree with your statement.

[ExtremeFiretop]

@codecrafting-io @lucasmarotta

Anyway, you can also try to install the modified v0.10.0 (select old Aura) and just replace the MBIsSupported.dll in the C:\Program Files (x86)\LightingService folder. You will need to stop the service first.

I tried this now with the modified 0.10.0 and selected te old Aura, and manually replaced the MBIsSupported.dll in the C:\Program Files (x86)\LightingService folder after stopping the service with the one located in the scripts: \Asus-Setup-Tool\Patches folder. And the problem continues. However again this all installed on the first try with your script without the error from this reported issue.

Thanks for the feedback on the original question of this issue. I would just ask one thing. Can you try the default v0.10.0 again? If the AiSuite3 error happens again, it's definitely the ASIO3 version that can cause problems on some machines.

I ran your original script a second time just now (not modified) and was unable to replicate the error anymore....

I think I will try one of the oldest Aura from the URL you provided: 1.04.29 and keep my fingers crossed it works. At this point though I don't think I can provide much more feedback for your tool unfortunately since it simply does not work for me at all anymore. :(

[ExtremeFiretop]

The older version of Aura gave me these errors:

When trying to start the app.

[ExtremeFiretop]

@codecrafting-io @lucasmarotta

Is it possible that Windows Driver signature enforcement needs to be disabled along with Secure Boot?

bcdedit /set nointegritychecks on

[ExtremeFiretop]

@codecrafting-io @lucasmarotta

I managed to re-create the error by re-installing armoury crate first; then without rebooting; using the released/original version v0.10.0

Now I will swap back to the patched version of v0.10.0

[ExtremeFiretop]

@codecrafting-io @lucasmarotta

Patched version installed without any errors on the first try; but sadly even with driver signature enforcement disabled and secure boot; the app gives the same error about the service.

I think this is the end of the line for me. Best of luck my friend; thanks for your time. Hope this was valuable to you in some ways.

[codecrafting-io]

@ExtremeFiretop

I don't think the problem in your case is related to drivers anymore. Sure, you may have had trouble installing some of them, but that is more related to Windows itself. Your problem is with LightingService, which is simply not detecting your devices.

As for older versions of Aura, if you have a version prior to 1.05, it probably just won't work at all or can't be patched, which makes it not work again. In your case, since none of the third-party RGB software works, you may have to rely on dedicated RGB controllers.

Regarding the AiSuite3 error, I am not quite sure why reinstalling ArmouryCrate would cause the error to reappear, but this is related to the transition to ASIO3 1.2.22.0, which can cause problems on some systems.

Thanks for the feedback and I still have not decided what approach to take in this situation. I might wait for ASUS to release a new version instead.

[ExtremeFiretop]

@ExtremeFiretop

I don't think the problem in your case is related to drivers anymore. Sure, you may have had trouble installing some of them, but that is more related to Windows itself. Your problem is with LightingService, which is simply not detecting your devices.

As for older versions of Aura, if you have a version prior to 1.05, it probably just won't work at all or can't be patched, which makes it not work again. In your case, since none of the third-party RGB software works, you may have to rely on dedicated RGB controllers.

Regarding the AiSuite3 error, I am not quite sure why reinstalling ArmouryCrate would cause the error to reappear, but this is related to the transition to ASIO3 1.2.22.0, which can cause problems on some systems.

Thanks for the feedback and I still have not decided what approach to take in this situation. I might wait for ASUS to release a new version instead.

I noticed some interesting issues related to USB on my system, for example. I can plug an old USB 2.0 drive on my front IO port and it works no problem, can see it and copy files. Same with any of the rear IO ports.

But If I plug in my brand new OnePlus 12, (USB 3.2 Gen 1 ) it only works from only one USB port on my system in the back IO. The front IO or even any of the other rear IO it connects and gives me a "This device cannot be recognized" error.

Seems almost like a USB bus/comms issue? Is that possible? How does the LightingSevice detect/communicate directly to the board RGB?

I don't plug any USB into the board to control it, I'm assuming it may be using some onboard USB or PCI bus?

[ExtremeFiretop]

@codecrafting-io @lucasmarotta Do you have Asmedia 3.1 USB Controller enabled on your BIOS?
What bout XHCI hand-off workaround?
Or Legacy USB Support?

[codecrafting-io]

@ExtremeFiretop Not sure what the problem is with your USB, but on my system I only install the chipset and network drivers.

I am sorry, but I will ask you to focus on the topic at hand. If you want to start other discussions or just talk to me, look me up on Reddit or start a Github discussion.

[ExtremeFiretop]

I am sorry, but I will ask you to focus on the topic at hand. If you want to start other discussions or just talk to me, look me up on Reddit or start a Github discussion.

Maybe you missed it so I'll just quote the question again:

How does the LightingSevice detect/communicate directly to the board RGB?

I don't plug any USB into the board to control it, I'm assuming it may be using some onboard USB or PCI bus?

[ExtremeFiretop]

@codecrafting-io Seems it uses the SMBus potentially? I'll dive more into that. Thanks!

[ExtremeFiretop]

As you can probably now tell; my question was to determine if my USB problem was related or not.
And therefore, was related to the topic/issue at hand. If the Lighting Service used the same bus as USB for example, then my USB issues could indicate a deeper problem (such as a dead controller, etc)

However; after testing lots, I've confirmed the USB issues are unrelated to the Lighting Service :)
USB is working fine for every other device; seems to be a compatibility issue between the phone and the host USB hub/controller and pretty common: https://www.reddit.com/r/oneplus/comments/1ayzwg4/issues_with_oneplus_12_and_connecting_to_the_pc/

At this point; I'm out of ideas or theories. Best of luck to your project; but I can confirm that your script did not resolve my issues and I don't appear to have any hardware problems.

[codecrafting-io]

As you can probably now tell; my question was to determine if my USB problem was related or not. And therefore, was related to the topic/issue at hand. If the Lighting Service used the same bus as USB for example, then my USB issues could indicate a deeper problem (such as a dead controller, etc)

However; after testing lots, I've confirmed the USB issues are unrelated to the Lighting Service :) USB is working fine for every other device; seems to be a compatibility issue between the phone and the host USB hub/controller and pretty common: https://www.reddit.com/r/oneplus/comments/1ayzwg4/issues_with_oneplus_12_and_connecting_to_the_pc/

At this point; I'm out of ideas or theories. Best of luck to your project; but I can confirm that your script did not resolve my issues and I don't appear to have any hardware problems.

Sorry, I misunderstood. The RGB lighting on the motherboard is not related to USB. I think for your case, unfortunately, you may have to buy an RGB controller or another motherboard.

[ExtremeFiretop]

@codecrafting-io and @lucasmarotta

Just wanted to mention; I ended up upgrading my ASUS Prime X370-Pro motherboard to an ASUS ROG Crosshair VIII Dark Hero Motherboard (found a good used one at a great price I couldn't refuse)

I retried your script, (production unmodified version of 0.10.0) and it worked perfectly on the first try; no errors, no bugs, no fuss. I didn't even disable Defender Core Isolation and it installed and works perfectly as found below:

You have my respect; I will continue to follow the project and any new releases. I've given a star.
Let me know BTW if you recommend re-running the script when/if you do any new releases.

[codecrafting-io]

@ExtremeFiretop Thanks. Glad you found a solution. The Core Isolation and other preparation steps are more for ASUS kernel drivers that may have trouble running when those features are enabled, but sometimes it works. Don't worry if it works for you, there's no real need to run the script again, even if it updates.

New updates are more to polish the setup or to update ASUS services and drivers to the latest found on ArmouryCrate. To this day, even the vanilla setup drivers from 1.07.84_v2 can work with a few tweaks and the right setup order. So I really don't think it's necessary. The setup can also work offline, so keep the folder to preserve the downloaded files in case ASUS removes the links.

[SabinGladys]

Hi, just came here to thank you and also help needed.
This tool had helped me to fix my Aura lights but it now doesn't work on a second computer. 🙏

Screenshot:

Failed to get Asus services, AiSuite3 quick setup failed to launch.

I'm using the OCT 2024 version (almost the latest version of tool I believe), and the info of PC are as follows:
Bother board: MSI B650M GAMING PLUS
System: Win10 64bit (10.0 19045)
BIOS: 1.82

Tried several times, and the Core isolation is disabled for sure.
I tried to find solution by reading this thread but it is really overwhelming so I wish to just follow-up by this reply and seeking help from you directly.

Again, thank you so much for creating this tool, I'm now trying to add my payment method too to treat you a cup of coffee

[ExtremeFiretop]

Hi, just came here to thank you and also help needed. This tool had helped me to fix my Aura lights but it now doesn't work on a second computer. 🙏

Screenshot: Failed to get Asus services, AiSuite3 quick setup failed to launch.

I'm using the OCT 2024 version (almost the latest version of tool I believe), and the info of PC are as follows: Bother board: MSI B650M GAMING PLUS System: Win10 64bit (10.0 19045) BIOS: 1.82

Tried several times, and the Core isolation is disabled for sure. I tried to find solution by reading this thread but it is really overwhelming so I wish to just follow-up by this reply and seeking help from you directly.

Again, thank you so much for creating this tool, I'm now trying to add my payment method too to treat you a cup of coffee

I don't disagree with you one bit on that front, it does look overwhelming if your just looking for a quick answer.
However I believe @codecrafting-io / @lucasmarotta is still investigating the cause which is why this issue is still open.

If you would like to skip directly to some steps to try, use this:

#6 (comment)