Solved Can't reset default program to open .themepack file

[confuzled]

Hello,

Recently I accidentally clicked "open with" instead of "open" on a .themepack file and managed to reset the default program.

I've researched online how to fix this problem, except that once I set the default program to shell32.dll, I get an error message saying "Execution of *************.themepack failed." I've also gotten messages saying ".themepack is not a valid win32 application."

I would very much appreciate help from anyone who could sort me out on this. Thank you!

 

[ryo]

hi and welcome.
did you already try this http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[Brink]

Hello Confuzled, and welcome to Seven Forums.

If you like, you could download and merge the themepack option in the tutorial below to restore it's default associations.

http://www.sevenforums.com/tutorials/19449-default-file-type-associations-restore.html

Hope this helps,
Shawn

 

[A Guy]

Welcome to Seven Forums confuzled. If the SFC does not fix this (be aware it will undo any customizations you have done, and you will have to repatch your system if you are using a 3rd party theme). Look to see what the default application is for .themepack

Start> In search box type file type> Choose Make a file type always open in a specific program from the list> Scroll down to .themepack and see what is listed as the current default

If it is not listed, that means it already has a file associated with it. A Guy

 

[A Guy]

Hello Confuzled, and welcome to Seven Forums.

If you like, you could download and merge the themepack option in the tutorial below to restore it's default associations.

http://www.sevenforums.com/tutorials/19449-default-file-type-associations-restore.html

Hope this helps,
Shawn

Hey! You just added .themepack to that list! I was going to point him to that, but .themepack wasn't on the list you sly devil

A Guy

 

[Brink]

LOL.

:devil2:

 

[confuzled]

Thank you, folks!

I tried the sfc scan, and that didn't work, although I did learn how to open Command Prompt.

I tried "Make a file type always open in . . . " and I got the same error messages.

Third time's the charm, though, and the default association restore worked. I've bookmarked that page for further emergencies, too.

Thank you! While you haven't saved my life or anything, you've allowed me to talk to geeks I don't know instead of trying to explain to geeks I do know what I did this time

 

[boohbah]

you'll still have to explain to them when they ask.

 

[Brink]

You're most welcome Confuzled. I'm glad that we could help.

 

[A Guy]

Glad you got it sorted. You now may have geek tendencies

A Guy