FearlessX
30th January 2008, 14:45
Hello, this is my first tutorial and it is about solving the .reg opening with Notepad. You might first experience it with Moonlight Engine where you had to double click the .reg file. I personally had this experience before and i solved it, and i will show you how to solve it.
Note: Only a few people might have this problem. It is caused by a virus/malware. Many trojan horses, viruses and other malwares make changes to the registry. They may affect one or more of the shellopencommand keys. By changing these keys they can make themselves be executed each time that you 'open' a certain type of file e.g. if they modified the exefileshellopencommand key then the trojan will be invoked every time you start any executable (.exe) file. Same thing can happen with registry (.reg) file.
This tutorial will solve not only .reg opening with notepad but .exe, .com, .bat, .pif, .scr from opening with notepad.
One instance of solving .reg opening with notepad is with a simple way which most users are familiar with is opening with Regedit.exe.
All you need to do is the following:
1. Click Start, Run, type in: RegEdit.exe
2. In Registry Editor click File, Import, then browse to the .reg file and click okay.
3. Done!
However that way, you need to do it all the time with different .reg so unless you want to repetitively do the same process over again, there is another which solves it with one go.
Download UnhookExecOpen.inf from this thread.
After downloading it, right-click on the file and select 'install'. This way it will not display any success message but your registry editor will work now again.
What UnhookExecOpen does is it will simply reset the shell open command for executable files:
.exe, .com, .bat, .pif, .scr (screensavers!)
and also for .reg files (registry data files).
Further on it will re-enable editing the registry altogether and make sure that the application associated with registry batch files (*.reg) is indeed the official registry editor and not some trojan horse.
Well thats it, I hoped I solved your problem. Remember it doesnt affect most of you, but it will affect a small minority of you, including myself.
-Mods, if this is in the wrong section please move it, i don't know where it goes.
Virus Scan of UnhookExecOpen.inf:
File: UnHookExecOpen.inf
Status:
OK
MD5: f77f8599a54b94239881efe7731242ff
Packers detected:
-
Bit9 reports: File not found
Scanner results
Scan taken on 30 Jan 2008 10:16:03 (GMT)
A-Squared
Found nothing
AntiVir
Found nothing
ArcaVir
Found nothing
Avast
Found nothing
AVG Antivirus
Found nothing
BitDefender
Found nothing
ClamAV
Found nothing
CPsecure
Found nothing
Dr.Web
Found nothing
F-Prot Antivirus
Found nothing
F-Secure Anti-Virus
Found nothing
Fortinet
Found nothing
Ikarus
Found nothing
Kaspersky Anti-Virus
Found nothing
NOD32
Found nothing
Norman Virus Control
Found nothing
Panda Antivirus
Found nothing
Rising Antivirus
Found nothing
Sophos Antivirus
Found nothing
VirusBuster
Found nothing
VBA32
Found nothing
Note: Only a few people might have this problem. It is caused by a virus/malware. Many trojan horses, viruses and other malwares make changes to the registry. They may affect one or more of the shellopencommand keys. By changing these keys they can make themselves be executed each time that you 'open' a certain type of file e.g. if they modified the exefileshellopencommand key then the trojan will be invoked every time you start any executable (.exe) file. Same thing can happen with registry (.reg) file.
This tutorial will solve not only .reg opening with notepad but .exe, .com, .bat, .pif, .scr from opening with notepad.
One instance of solving .reg opening with notepad is with a simple way which most users are familiar with is opening with Regedit.exe.
All you need to do is the following:
1. Click Start, Run, type in: RegEdit.exe
2. In Registry Editor click File, Import, then browse to the .reg file and click okay.
3. Done!
However that way, you need to do it all the time with different .reg so unless you want to repetitively do the same process over again, there is another which solves it with one go.
Download UnhookExecOpen.inf from this thread.
After downloading it, right-click on the file and select 'install'. This way it will not display any success message but your registry editor will work now again.
What UnhookExecOpen does is it will simply reset the shell open command for executable files:
.exe, .com, .bat, .pif, .scr (screensavers!)
and also for .reg files (registry data files).
Further on it will re-enable editing the registry altogether and make sure that the application associated with registry batch files (*.reg) is indeed the official registry editor and not some trojan horse.
Well thats it, I hoped I solved your problem. Remember it doesnt affect most of you, but it will affect a small minority of you, including myself.
-Mods, if this is in the wrong section please move it, i don't know where it goes.
Virus Scan of UnhookExecOpen.inf:
File: UnHookExecOpen.inf
Status:
OK
MD5: f77f8599a54b94239881efe7731242ff
Packers detected:
-
Bit9 reports: File not found
Scanner results
Scan taken on 30 Jan 2008 10:16:03 (GMT)
A-Squared
Found nothing
AntiVir
Found nothing
ArcaVir
Found nothing
Avast
Found nothing
AVG Antivirus
Found nothing
BitDefender
Found nothing
ClamAV
Found nothing
CPsecure
Found nothing
Dr.Web
Found nothing
F-Prot Antivirus
Found nothing
F-Secure Anti-Virus
Found nothing
Fortinet
Found nothing
Ikarus
Found nothing
Kaspersky Anti-Virus
Found nothing
NOD32
Found nothing
Norman Virus Control
Found nothing
Panda Antivirus
Found nothing
Rising Antivirus
Found nothing
Sophos Antivirus
Found nothing
VirusBuster
Found nothing
VBA32
Found nothing