Messages

1

RogueKiller / Re: ==> Crash/Hang/Block, please come here <==

« on: June 24, 2016, 02:52:42 PM »

I am having a new problem recently using the old interface. It doesn't seem to be hanging, but after the scan completes, none of the results show. Attached is a picture of the problem. Each tab displays blank underneath it like shown.

2

RogueKiller / Re: ==> Crash/Hang/Block, please come here <==

« on: May 24, 2016, 08:26:21 PM »

Awesome, thanks so much!

3

RogueKiller / Re: ==> Crash/Hang/Block, please come here <==

« on: May 19, 2016, 05:54:42 PM »

Okay, thanks. So only option is to use the new interface then?   

Edit: the "old interface" version numbers are still increasing along with the new interface version numbers. Why is the old interface being updated if it's not supported?

4

RogueKiller / Re: ==> Crash/Hang/Block, please come here <==

« on: May 11, 2016, 12:47:38 AM »

I am using the old version of Roguekiller (I don't really care for the new interface) and I'm having a problem with it on most computers. It usually gets to around 50% before the interface freezes. I can open up Task Manager and see that Roguekiller is still doing something, I can move the Roguekiller window around as well. But I can't get the Stop button to work.

If I leave it sit for a while (>10 minutes), the stop button eventually functions. If I leave it sit even longer, Roguekiller will eventually finish its scan. It usually takes longer than 30 minutes for it to "snap out of it." This happens on 32- and 64-bit versions of Windows 7, 8, and 10. Task Manager shows Roguekiller's CPU usage, RAM usage, and disk usage changing the entire time, so like I said, it still appears to be doing something even when the interface is frozen.

I never had this problem with the versions of Roguekiller prior to the interface change, nor with the new interface, but as I stated, I don't like the new interface so I switched over to using the "old" versions shortly after the new interface was released. I just updated to 12.2.0.0 and I'm still having this problem on pretty much every computer.