Dumb and dumberer!!!

  • Thread starter Thread starter Kathleen
  • Start date Start date
K

Kathleen

I accidentally removed the file association for .exe
files! Dumb, dumb, dumb. Anyway, does anyone know the
registry fix to reassociate .exe files? I can't run any
applications now.

I tried hkey_classes_root on local machine and deleting
the "junk" .exe and adding a new one that looks like:

<No Name> :REG_SZ:exefile
Content Type :REG_SZ:application/x-msdownload

But this didn't work either.
 
Kathleen wrote in
I accidentally removed the file association for .exe
files! Dumb, dumb, dumb. Anyway, does anyone know the
registry fix to reassociate .exe files? I can't run any
applications now.

I tried hkey_classes_root on local machine and deleting
the "junk" .exe and adding a new one that looks like:

<No Name> :REG_SZ:exefile
Content Type :REG_SZ:application/x-msdownload
Click to expand...

You don't say the OS...
W2K here and .exe association looks like this:

REGEDIT4

[HKEY_CLASSES_ROOT\.exe]
@="exefile"
"Content Type"="application/x-msdownload"

[HKEY_CLASSES_ROOT\.exe\PersistentHandler]
@="{098f2470-bae0-11cd-b579-08002b30bfeb}"

Did you lose "exefile" filetype too?

YMMV
 
Kathleen wrote in
I accidentally removed the file association for .exe
files! Dumb, dumb, dumb. Anyway, does anyone know the
registry fix to reassociate .exe files? I can't run any
applications now.

I tried hkey_classes_root on local machine and deleting
the "junk" .exe and adding a new one that looks like:

<No Name> :REG_SZ:exefile
Content Type :REG_SZ:application/x-msdownload
Click to expand...

You don't say the OS...
W2K here and .exe association looks like this:

REGEDIT4

[HKEY_CLASSES_ROOT\.exe]
@="exefile"
"Content Type"="application/x-msdownload"

[HKEY_CLASSES_ROOT\.exe\PersistentHandler]
@="{098f2470-bae0-11cd-b579-08002b30bfeb}"

Did you lose "exefile" filetype too?

YMMV
 
I accidentally removed the file association for .exe
files! Dumb, dumb, dumb. Anyway, does anyone know the
registry fix to reassociate .exe files? I can't run any
applications now.

I tried hkey_classes_root on local machine and deleting
the "junk" .exe and adding a new one that looks like:

<No Name> :REG_SZ:exefile
Content Type :REG_SZ:application/x-msdownload

But this didn't work either.
Click to expand...


HKEY_CLASSES_ROOT\exefile\shell\open\command as an unnamed value of type REG_SZ
with a string of "%1" %*

Unfortuneatly, since EXE files won't run, you can not use the REGEDT32.EXE.
Temporarily rename regedt32.exe to regedt32.com and fix it.



Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com
 
I accidentally removed the file association for .exe
files! Dumb, dumb, dumb. Anyway, does anyone know the
registry fix to reassociate .exe files? I can't run any
applications now.

I tried hkey_classes_root on local machine and deleting
the "junk" .exe and adding a new one that looks like:

<No Name> :REG_SZ:exefile
Content Type :REG_SZ:application/x-msdownload

But this didn't work either.
Click to expand...


HKEY_CLASSES_ROOT\exefile\shell\open\command as an unnamed value of type REG_SZ
with a string of "%1" %*

Unfortuneatly, since EXE files won't run, you can not use the REGEDT32.EXE.
Temporarily rename regedt32.exe to regedt32.com and fix it.



Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com
 
1. On a PC that was working ok I ran: assoc |more from a
command prompt. This lists all of the associations.

2. Noted that .exe was associated as .exe=exefile

3. On my PC I used Explorer to run command.com from
c:\winnt\system32 since it won't work from Start-Run.

4. Ran the following command: assoc .exe=exefile

5. Logged out and back in and it worked!
 
1. On a PC that was working ok I ran: assoc |more from a
command prompt. This lists all of the associations.

2. Noted that .exe was associated as .exe=exefile

3. On my PC I used Explorer to run command.com from
c:\winnt\system32 since it won't work from Start-Run.

4. Ran the following command: assoc .exe=exefile

5. Logged out and back in and it worked!
 
Jerold Schulman said:
HKEY_CLASSES_ROOT\exefile\shell\open\command as an unnamed value of type REG_SZ
with a string of "%1" %*

Unfortuneatly, since EXE files won't run, you can not use the REGEDT32.EXE.
Temporarily rename regedt32.exe to regedt32.com and fix it.



Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com
Click to expand...
Click to expand...
 
Jerold Schulman said:
HKEY_CLASSES_ROOT\exefile\shell\open\command as an unnamed value of type REG_SZ
with a string of "%1" %*

Unfortuneatly, since EXE files won't run, you can not use the REGEDT32.EXE.
Temporarily rename regedt32.exe to regedt32.com and fix it.



Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com
Click to expand...
Click to expand...
 
You can always connect to the machine remotely via REGEDT32 from another
machine or run REG.EXE and point it to the remote machine to make these
modifications.

I was once working on a system (Security hardening to DoD DITSCAP standards)
where manually editing registry permissions was necessary. It was a long
late night and I change some permission that totally hosed EVERYTHING.
Nothing was associated with anything (all icons were there but blank - no
pictures). This was a production machine and I didn't want to roll back.
After some thought I decided to try and modify the registry permissions from
another machine. I pushed the necessary permissions changes form the other
machine and everything was OK.

I've also remotely fixed an NT system where someone changed the screen
refresh settings so they couldn't really see anything once the system came
up. Changed the settings remotely and rebooted - all was fine again.

Moral .... you don't always need to fix the machine that needs to be fixed
from the machine that needs to be fixed.

HTH,

Robert


 
You can always connect to the machine remotely via REGEDT32 from another
machine or run REG.EXE and point it to the remote machine to make these
modifications.

I was once working on a system (Security hardening to DoD DITSCAP standards)
where manually editing registry permissions was necessary. It was a long
late night and I change some permission that totally hosed EVERYTHING.
Nothing was associated with anything (all icons were there but blank - no
pictures). This was a production machine and I didn't want to roll back.
After some thought I decided to try and modify the registry permissions from
another machine. I pushed the necessary permissions changes form the other
machine and everything was OK.

I've also remotely fixed an NT system where someone changed the screen
refresh settings so they couldn't really see anything once the system came
up. Changed the settings remotely and rebooted - all was fine again.

Moral .... you don't always need to fix the machine that needs to be fixed
from the machine that needs to be fixed.

HTH,

Robert


 
Back
Top