Skip to main content

Vista anti-malware

A computer got infected with this. It pretends that your computer is infected with x amount of spyware/malware and you have to get the registered version to remove the (fake) malware. From the page here the steps to getting rid of this annoyance are:

  1. Type Ctrl/Shift/Escape to bring up the task manager (or right click on the task bar).
  2. Kill the ave.exe process. The popups will disappear. Leave the task scheduler up.[NOTE: you can use procexp too]
  3. Type Windows/R (to get the Run box) and type regedit and OK.
  4. Ave.exe will start again, just do step #2 again.
    [Note: Be careful with regedit. If you are not familiar with it, use other solutions for this infection]
  5. In Regedit, go to HKCR\.exe\shell\open\command. You will see something like this for (default):
    "C:\Documents and Settings\[your account]\Local Settings\Application Data\ave.exe" /START "%1" %*
  6. Modify the value to be:
    "%1" %*
  7. Do the same with HKCR\secfile\shell\open\command.
  8. Delete ave.exe from the location in step 5. [NOTE: I could just not find this program]
    At this point, you have control back and no more popups.
  9. Download the current version of Malwarebytes' Anti-Malware and run it.
  10. Choose to fix the items the scan found.
  11. Run a scan of your regular anit-virus program.

Comments

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...
Post a Comment
Read more

Remove field code from Word document

e.g. before submitting a MS, or hand manipulating some formatting because Word does things (like cross-references) so half-assed [from here ] Select all the text (CTRL-A) Press Ctrl+Shift+F9 Editing to remove anonymous comments that only contain thanks. I really appreciate the thanks, but it makes it harder to find comments that carry pertinent information. I'm also going to try and paste informative comments in the body of the post to make them easier to find.
24 comments
Read more

h5py and multiprocessing

The HDF5 format has been working awesome for me, but I ran into danger when I started to mix it with multiprocessing. It was the worst kind of danger: the intermittent error. Here are the dangers/issues in order of escalation (TL;DR is use a generator to feed data from your file into the child processes as they spawn. It's the easiest way. Read on for harder ways.) An h5py file handle can't be pickled and therefore can't be passed as an argument using pool.map() If you set the handle as a global and access it from the child processes you run the risk of racing which leads to corrupted reads. My personal runin was that my code sometimes ran fine but sometimes would complain that there are NaNs or Infinity in the data. This wasted some time tracking down. Other people have had this kind of problem [ 1 ]. Same problem if you pass the filename and have the different processes open individual instances of the file separately. The hard way to solve this problem is to sw...
Post a Comment
Read more