Warning: Hijack.DisplayProperties cleaned out

Microsoft Windows 7 home premium oem 64b...
March 16, 2010 at 21:33:35
Specs: Windows 7 Home Premium 64bit, P4 660 3.6/3Gig RAM
I am posting this as an experience and as a warning. May some take some benefit from it. (Problem solved though)
Over the last few days, I have been having a problem with windows 7 home premium 64bit. It has without warning closed down programs and come back with "....windows has recovered...." and the box from microsoft asking about going online to find a solution. and occasionally a restart. I suspected an infection, but updating and rescanning could not find anything (I have used Webroot's Antivirus with SpySweeper successfully for a number of years....That's YEARS without an infection it did not pick up on immediately!) My computer is MILDLY overclocked and I have video card set to OC slightly only on two games. I eliminated the video OC entirely yesterday. Today after work, I rolled back on the cpu clocking even more, with the same results. Assuming again that it MUST be an infection I rolled out the alternate plan and installed Malwarebytes, and it found the infection:
Registry Data Item Infected: 1
HKEY_LOCAL_MACHINE\SOFTWAREMicrosoft\Windows\CurrentVersion\policies\Explorer\NoActiveDesktopChanges (Hijack.DisplayProperties) ->Bad: (1) Good: (0) -> Quarantined and deleted successfully.

It just goes to show you (and me) that even a good utility can miss a nasty that another might find. I am assuming that it messed with the graphics settings to force a shutdown or restart and make Windows 7 LOOK bad (or not as perfect at least).
I am posting it HERE to help others quickly find and fix this problem.


See More: Warning: Hijack.DisplayProperties cleaned out

Report •

#1
March 17, 2010 at 07:52:05
you must have pasted that into the post. It is a pain to read when having to keep sliding the bar over on each line.

Some HELP in posting on Computing.net plus free progs and instructions Cheers


Report •

#2
March 17, 2010 at 16:02:14
No. After printing, I had to restart so I had to type it all. My head must have a good buffer because I can type and keep track of where I am without constantly rechecking (not quite a 'touch typist' though). Right brain watches the left brain, and visa-versa ("whole brain"). It still isn't something I would like to have to do constantly.

Report •

#3
March 17, 2010 at 19:24:36
I may have declared it fixed prematurely. I had an unexpected restart this evening. It may be a lingering error caused by the infection, or another problem.

Report •

Related Solutions

#4
March 18, 2010 at 05:58:25
I guess I found the problem this time. My computer just failed Memtest35 three times in a row (test#1, test#0, test#1) and restarted each time. Since I purchased Crucial Balistix 2x2Gb 800mhz as a matched pair (4 or 5 months ago) I will look into getting the pair replaced under warrantee. I have 2 sticks or RAM I am not using (I believe they are DDR2 500MB around 400mhz - they have aluminum heat sinks covering any labels/markings and I was given them free) that I hope I can use (BUT I DOUBT IT) until I get them replaced. I am using a Gigabyte GA-G41M-ES2H and Windows 7 Home Premium 64bit with: Pentium Dual E2160, XFXPVT96GYGF3 GeForce 9600GT 512MB 256Bit DDR3 PCIe2.0x16, WD 500GB SATA 7200/32MB Black. I'm going to check ******Never Mind, even if the board can handle it, windows 7 64bit Won't!!!!! I have to hope that New Egg or Crucial will send me a new pair with the ability to return these after swapping out.....

Report •

#5
March 18, 2010 at 07:29:43
Update: Downloaded newer version on Memtest86 v4.00 (for multi-core processors) and it did not freeze, but it did find many errors. I stopped it at test #8 after 45min with over 150000 errors. I let it run this long since I began noticing a pattern: when it tested memory 176K - 2048M there was no errors (first stick) but when it tested the next set 2048M-2237M it found a continuous flow of errors. This is a matched set, so I cannot just replace one though. Tomorrow I am off work so I will try reseating RAM and retesting, then make phone calls if this does not help.

Report •

Ask Question