G
Guest
I am having an issue with a development box. We have many in-house
applications that our users access off of a terminal server. With the
Security that comes along with SP1 a developer was having a hard time with a
security dialogue box that kept prompting the users if they really wanted to
launch this app. Somewhere between that and now he has managed to
unassociate exe files with what program they should launch. Now any exe file
(ie, explorer, regedit, plus the in-house developed apps) that is launched
gets the Windows cannot open this file. To open this file, Windows needs to
know what program created it. Windows can go online to look it up
automatically, or you can manually select from a list of programs on your
computer.
Is there anyway through the registry (was able to launch regedit by renaming
to regedit.com) to get exe's launching again?
Thanks,
DP
applications that our users access off of a terminal server. With the
Security that comes along with SP1 a developer was having a hard time with a
security dialogue box that kept prompting the users if they really wanted to
launch this app. Somewhere between that and now he has managed to
unassociate exe files with what program they should launch. Now any exe file
(ie, explorer, regedit, plus the in-house developed apps) that is launched
gets the Windows cannot open this file. To open this file, Windows needs to
know what program created it. Windows can go online to look it up
automatically, or you can manually select from a list of programs on your
computer.
Is there anyway through the registry (was able to launch regedit by renaming
to regedit.com) to get exe's launching again?
Thanks,
DP