ROG SPATHA Does Not Work in Wired mode [Resolved]

[MLGbr]

Mr administrator: IT IS IMPOSSIBLE TO UPDATE MOUSE FIRMWARE IN CABLE MODE!


I will draw


Step 1 - Put Mouse on the cable



Step 2 - Open ROG ARMORY


Step 3 - Live Update


Crash!!


EVENTVIEWER



STATUS:
Wireless - OK
Wired - Not Work



MASSIVE LOGS HERE - From the beginning of the problems

https://www.dropbox.com/s/f64euplin26dngv/MyLogs.7z

I hope to help the ASUS peripheral team, In particular, the ROG ARMORY developers team.


I will use the mouse in Wireless mode, until ASUS found a solution.

Mr administrator: Do you want me to open a post "Rog Spatha does not work in wired mode", or can we continue here in this post?

[MLGbr]

HOW THE WIRELESS PROBLEM WAS RESOLVED

I bought a Corsair keyboard, and I installed the Corsair Utility Engine (CUE) version 2.20.72 on 12/18/2017.
A perfect month later (01/19) the problem occurred in the ROG SPATHA mouse.

Several times during these days, I suspected CUE, and disabled boot during tests and in my attempts to re-enable the Mouse.
But during the normal use of everyday life, I allowed CUE to be run in Windows start.

Between the dawn of 01/19/2018 and the afternoon of 01/07/2018, the wireless base was detected, but the mouse was not detected by ROG ARMORY, not being able to reprogram the mouse buttons in Wireless mode, although the simple operations of clicking and moving the cursor worked.

I do not have a screenshot, but in Wireless ROG Armory mode it did not display Mouse information, it only showed a reddish background.

( It is not the real screen, it's just a similar drawing of SPATHA in wireless mode, without detection by ROG ARMORY )



INVESTIGATION - RETURN OF WIRELESS OPERATION


-Computer was shut down on 02/07/2018 at 03:30:20 (UTC-2), still with all problems

-Computer was connected on 02/07/2018 at 18:27:57 (UTC-2)

-Corsair Utility Engine (CUE) version 2.20.72 if run at Windows startup, and displayed a black popup saying there were updates.

-I opened the CUE application, and I used its graphical interface, to cancel any kind of update, but there was no option to cancel, and I ended up making no changes.
I was completely involved with the problems of the mouse, and I did not want this application to disturb me.

-CUE may have carried out some procedure without my consent. I've never updated the CUE application.

The ROG SPATHA mouse was detected again in wireless mode, allowing button programming and light change, even using the old ROG ARMORY version 10224.

I made a printscreen - SPATHA is complete detected in Wireless mode



-I updated the ROG ARMORY for version 2.04.04 on 02/07/2018 at 18:51:29 (UTC-2)

- After updating, the ROG SPATHA continued working perfectly in Wireless mode.

Then, I performed the procedure of opening the mouse and disconnecting the battery (as requested by the forum administrator), and I answered writing the post #7 in this thread.

The correction of the problem of the ROG SPATHA Wireless occurred on 02/07/2018, between 18:27:57 and 18:51:29 (UTC-2), AND I AM SURE THAT IT WAS CAUSED BY AN "unknown remote procedure" of Corsair Utility Engine version 2.20.72, which I did not order, and never allowed, and occurred when the application detected an online update (which I never asked to do).

- CUE is in version 2.20.72 in my PC, it is the same version that I installed on 12/18/2017, and officially no update occurred.




MY ANALISIS

File changes at critical moment, between the 'mouse correction event' and the ROG ARMORY update

"user-PC" is my local user


PATH - Data - Hour (UTC-2) - Size - User - FileName

--18:34

C:\Users\user\AppData\Roaming\Corsair\CUE
07/02/2018 18:34 <DIR> user-PC\user Corsair

C:\Users\user\AppData\Roaming\Corsair\CUE\Corsair
07/02/2018 18:34 365 user-PC\user CUE.cuecfg
07/02/2018 18:34 <DIR> user-PC\user ..
07/02/2018 18:34 <DIR> user-PC\user .

Comment: Files produced by CUE, automatically or during my access, although I have not made any changes

Corsair modification files at 18:34

There may have been changes in the Windows registry, I have no way of knowing.



--18:48

C:\Users\user\Pictures\2018-01-23
07/02/2018 18:48 67.565 user-PC\user TelaFuncionando.JPG

Comment: ROG SPATHA was working perfectly in wireless mode with ROG ARMORY v10224, and I did a screenshot using SnippingTool from Windows 7


C:\Users\user\AppData\Local\Microsoft\Windows\Hist ory\History.IE5
07/02/2018 18:48 <DIR> user-PC\user MSHist012018020720180208

C:\Users\user\AppData\Local\Microsoft\Windows\Hist ory\History.IE5\MSHist012018020720180208
07/02/2018 18:48 <DIR> user-PC\user ..
07/02/2018 18:48 0 user-PC\user container.dat
07/02/2018 18:48 <DIR> user-PC\user .


Comment: I never use Internet Explorer, it must have been opened as embeded by some other application, must have saved history when it was closed.


SOFTWARE ANALISIS


The application's XML may indicate an attempt to identify a Scimitar mouse.

Opening the configuration files, at the end of the file

C:\Users\user\AppData\Roaming\Corsair\CUE\profiles \"UNIQUE ID".cueprofiledata



I have a Corsair keyboard, but I've never had a Scimitar.

Perhaps this is the source of the all problems: Attempting to execute "Demo" in other hardwares.

I removed CUE from the startup.



NOTE: The Wireless Problem has been solved, but the mouse continues to have problems in the wired mode.

[MasterC@ROG]

As mentioned previously, please wait until the Live Update feature is ready. When it is, you should be able to update your firmware. From there we can we can determine what to do next. Version 2 of Armoury was actually not supposed to be available to the public last week.

[MLGbr]

ROG SPATHA STATUS:
Wired: Intermittent detection (less than 2 seconds)
Wireless: Perfect Operation



Connecting the ROG Spatha to the computer in wired mode, with ROG ARMORY 2.04.04 opened - Every 30 seconds Windows seems to try to detect it, but can not,
as if the mouse was connected for 2 seconds and then disconnected.


Windows does not recognize



Windows recognition only 2 seconds



And return to 'not-recognize normal situation' for 30 seconds



After some detection attempts, the behavior stops for a few minutes (leaving the mouse completely dead), and returns again.

Does the administrator have any ideas?

------------------------------------------------------------
What about the mysterious ASUS RMA in Brazil?

After a purchase, how many months does ASUS allow the user to do RMA, with a Brazilian shopping in a store in Brazil?
The manual of the Mouse says "1 month for the physical store", and supposed 6 months given by the Asus brand - It is possible that this guarantee should not be valid in Brazil, neither ASUS staff can answer that.

I tried to go from behind the RMA and had a brutally negative experience.
If the mouse problem is not solved, I'll be posting here what happened.

[MasterC@ROG]

Sorry the Live Update has been delayed until next week. It is best to wait for that before trying RMA.

For more info about RMA:
https://rog.asus.com/forum/showthrea...wide-RMA-Guide

[MasterC@ROG]

The new Armoury II (2.04.07) is now available, please try it by going to this thread to download:
https://rog.asus.com/forum/showthrea...ny-issues-here

[MLGbr]

1) I downloaded Rog Armory 2.04.07 zip file and unzipped into a folder
2) I connected the mouse Rog Spatha on the cable
2b) I use another common mouse to operate the computer
3) Close all Rog Armory executables (ArmoryLiveUpdate.exe, ROG Armory.exe, Mutually Exclusive Aura Agent.exe, MacroAgent.exe) and taskeng.exe
4) Execute Setup.exe of installation
5) I confirmed the uninstallation of Rog Armory previous version.
6) The installation closed and nothing happened.
7) Execute Setup.exe again
8) Installation occurs normally, and prompts you to restart
9) Restart computer
10) Execute Rog Armory (from desktop Link) as administrator
11) Rog Armory detects Rog Spatha mouse.
11b) The mouse pointer slowly slides to the right and down.
12) I make the mouse firmware update
12b) During firmware installation, Windows emits USB connection and disconnection sound several times, but I watch it without interfering.
13) The mouse returned to normal operation

The recorded macro was lost, possibly because of the reinstallation process, but I'm very happy.

[MasterC@ROG]

Glad everything work out!

[MLGbr]

I left the computer for 10 minutes.
When I came back,
Windows had a message that USB was not being recognized,
and Rog Spatha's mouse with the lights off.

Since surely the problem is caused by software - 100% by the ROG armory - I rebooted the computer, and the mouse returned to normal.

1) I closed all Rog Armory executables
2) Msconfig and removed "Armory live update" from startup.
3) Restart
4) I waited another 10 minutes, and everything continued normal.


The problem was solved by removing "Armory live update" from startup

It seems like a problem:
- Power management
- Some kind of TimeOut

This is a Rog Armory issue - 100% software;
The mouse working perfect without "Armory live update" from startup.

[MLGbr]

I found the final solution for the Rog Spatha Mouse.

After

1) Updating Rog Armory
2) Remove Rog Armory from Windows start

I CHANGE THE USB PORT !!!

Windows detected the mouse, did the installation, and now it works perfectly.

Never again of problem of bad detection.

100% solved!!!