jason
-
Posts
2,989 -
Joined
-
Last visited
-
Days Won
132
Posts posted by jason
-
-
3 hours ago, dnalloheoj said:
Shit, I hadn't considered the chair this entire time. You might be on to something here...
But seriously, yep, still on 5276, tasklist attached. About to jump into a meeting here at 1:30-2ish so can't compare for similaraties right this second - but suspect the only differences might be more web browser processes, MSPaint, Notepad. Maybe PowerToys wasn't running on the other profiles? But nothing crazy different.I have moved my chair back and forth and still have not been able to reproduce it. Was it side to side or towards and away?
-
4 minutes ago, dnalloheoj said:
Correction - it's broken.
I did nothing, just moved my chair over 4 feet to sit in front of it (since typing up that last message). Disconnected. Unplug/plug back in, 1s connected then DC'd.you are using the same build? Anything different in processes? What happens if you move your chair back 4 feet?
-
Just now, dnalloheoj said:
I can't break it simply by unplugging/plugging back in, which has allowed me to break it in the past, yes.
I can start going wild and installing software to get it to break again, though, if that's the next goal.I think so.
-
45 minutes ago, dnalloheoj said:
Correct, I did not update. I only hit the update button (On the left prompt - it's not apparent in the picture, as I already clicked it) in order to bring up the prompt (on the right) that I was more used to seeing. I'm still on 5276.
So right now, you are on a working system, and can't break it yet. Is that correct?
-
2 minutes ago, dnalloheoj said:
That's the difference I noticed. I clicked on the 'Update' button on the left prompt in order to bring up the right one. But the left prompt was never showing up for me prior. It'd always show the right one straight away.
So yeah, could be that I wasn't using that build before, only thing that's been uninstalled on this PC would be the ASUS software, IIRC. Everything else would've just been installed and left to sit.You would not update. So the updates are automatic on this 'one' channel that we are testing. But the future updates will break things. So ignore that.
-
Just now, dnalloheoj said:
Previously broken profile (Prior to creating two new local admin accounts) works on v5276.
Not quite certain which build it was on prior, unfortunately, but I just logged in, opened it up, and it worked. It prompted for the update, but did so in a manner that I've only now seen twice, this time, and just ~10 minutes ago. Previously any prompts for update were from a more Windows-Store style prompt.
It must be related to that build, and one of the uninstalls you did. Can you clarify what you mean about prompted update, the skipapp? Can you post a screenshot?
-
2 minutes ago, dnalloheoj said:
Resulted in the same behavior with the second new account - 1s-ish of connectivity, then DC'd. Nothing new and fun in Event Viewer.
Note, yes an absence of ASUS software, but reg keys are still installed.Hang on, could be nothing. When you are on the new user account, you should use the following build: 5276
-
4 minutes ago, jason said:
Does windows event manager show anything suspicious after the new account was created and then when it started to fail?
Another idea. Create a new account. Print running processes. Cause it to fail (unplug/plug). Print processes again. Diff
-
1
-
-
16 minutes ago, dnalloheoj said:
Certainly possible. And yeah see my edit - I was able to get it to come back after enough plug-cycles.
@AeroCluster may be able to confirm for us that before you try ripping ASUS out though, since he already did.Does windows event manager show anything suspicious after the new account was created and then when it started to fail?
-
25 minutes ago, dnalloheoj said:
I wouldn't say that I've narrowed it down specifically to these two pieces of software specifically, no, but I think whatever both of these software do, is what the issue is. And my guess is cert related tbh.
A Mac reporting in doesn't surprise me one bit, for essentially the same reasons. Macs are going to be locked down a lot further than a Windows PC natively. "Macs don't get viruses" - Yeah, it's because they have their own rootkit(/AVish thing) already installed.
I'm available here pretty much all day with a non-working PC sitting right beside me if you want access to it since I'm on my work PC. At this point, looks like I'll need to reinstall Windows again anyway so you're welcome to break anything you want, basically.Yeah. Let’s connect with all team viewer. I’ll be at the office in about 45
-
2 hours ago, dnalloheoj said:
Uninstalled. Still broken.
Suspicions all but confirmed here. This thing took about 45 minutes to install, yet the uninstaller removed it in all but <2 minutes? No way.
Pop open regedit, CTRL+F "ASUS" keep hitting F3, look at em all. Everywhere. And guess what the very first one that pops up is? AsusCertService. That uninstaller doesn't clean up shit.
I really don't know if this is going to be possible without an actual reinstall. That is messy. fucking. software.
@jason was half-joking. But seriously. Burn it with fire.
E: aaaaand now synology photobackup fucked up my restore point, lmao, darn.
E2: Nevermind, synology was just holding it up. Got the restore to go through. Guess what still didn't get removed? Fuckin' Asus' wild regedits.I repeat:
Except apparently, you can't.
So here's the question - does anyone here, who is having issues, use a computer where ASUS Crate, or Forticlient has NEVER been installed?I’m a bit confused. Have you narrowed it down to these two pieces of software? Honestly I can solve this if you put a machine in front of me. It’s just a matter of trial and error. Maybe changing my HID report to confuse windows and not claim my device. Or figure out how to write a custom driver that just tells windows and other programs to fuck off. But I still don’t know if this is the problem.
I've shipped 300. There are others who wrote in not participating here, but only a few. Of all shipped, some people had macs. I stopped shipping when this started as it became clear it was a problem. -
Just now, theboomr said:
@jason this is also the config I was selecting to use with my Series X. I didn't have time to do thorough testing yet but it seemed like all buttons were problematic, not any one in particular.
Got it, thank you.
-
19 hours ago, theboomr said:
Ooh I'm having this issue with a Series X as well. I thought maybe it was just that my Xbox is at the bottom of my console and wasn't receiving the IR well enough but even if I stick the remote directly in front of the IR receiver on the console, it still doesn't seem to be 100% consistent.
Can you export your configuration, attach here? Is there one button inparticular that is problematic?
-
14 hours ago, Fardi273 said:
Here's the results. I just notice when typing now that I press skip remote 1st in each file. Hope it's fine. If not, I take again next time.
log1: Ch down button (problematic with skip, ok on original). Skip remote, followed by original remote.
log2: Ch up button (OK. TV channel was changed). Skip remote, followed by original remote.
my_flirc_log1 - Ch down (no response).txt my_flirc_log2 - Ch up (OK).txt
@Fardi273I'm stuck. I'm not sure what I'm looking at.
Can you separate these. Can you create two distinct files. One with CH down skip. One with Channel down original. And also attach your configuration, specify which device is giving you the problem? -
Can you go to remote manager, export your config, and post that? I'm having a bit of trouble reproducing this.
-
Can you save your config and post it, I'll take a look, repeat, and fix it.
-
anyone have a mac? Let's grab the logs off the remote. I'll get this fixed in the next update.
-
4 hours ago, jason said:
Major thanks to @Agustin
Okay, FInd our Same 20A0 device under HID-compliant Vendor-Defined Device.
Go to the details tab. Go to `Physical Device Object Name`
Now open up the process explorer application. Search for your `value` you have for above, here is mine in the screenshot:
What is the process? If it says non-existent, go to run->resmon
Sort by PID, and find the match!
@AeroCluster@sWRbQTFGSIAWare you able to try this?
-
4 minutes ago, theboomr said:
Still doesn't work. It's worth noting that Steam does not auto-start with Windows on my PC, I had to go and start it myself in order to get that result to show up in Process Explorer.
I looked around a bit in Steam's controller settings and it doesn't seem like it shows anything detected in the UI, so it's weird that the process grabs it at all, but yeah, Skip App still doesn't work after closing Steam back down, and I checked for any running background processes.make sure you use the public version, some of our test versions had a bunch of stuff in them that intentionally broke things but meant to get us useful logs.
-
1 hour ago, jason said:
Major thanks to @Agustin
Okay, FInd our Same 20A0 device under HID-compliant Vendor-Defined Device.
Go to the details tab. Go to `Physical Device Object Name`
Now open up the process explorer application. Search for your `value` you have for above, here is mine in the screenshot:
What is the process? If it says non-existent, go to run->resmon
Sort by PID, and find the match!
@dnalloheojCan you try this? Can you also let us know if you kill all steam tasks, does skipapp find the remote? (use the public version)
-
7 minutes ago, theboomr said:
Ok that's interesting. If I open steam and then search Process Explorer for 20A0, it shows up for me as well just like this.
omfg. Kill it and try the skipapp again.
-
Just now, theboomr said:
Correct and correct
Let's try this. Take a can of gasoline, carefully pour it on the computer, light it on fire, and call a priest, because the fucking thing must be possessed by the devil.
-
1
-
-
2 minutes ago, theboomr said:
And you were searching for \Device\00000134 ?
You are not running any virtual machine software, is that correct?
-
Just now, pen2paper said:
Thanks, Jason - new file attached
Sorry, can you also do one with the okay key (the one that seems to overlap)
Skip App v0.9.4 Beta
in Beta Feedback
Posted
Try doing it again, but do not auto-update. Leave it on 5726