Cant Set File Association

[Hoggy Dog]

[SOLVED] Cant Set File Association

I have used two methods (normal Windows 7 "always use this software to open this file type" and FileTypesMan x64 I found linked in a 5-year-old thread here on Seven Forums.

Neither worked- I was able to "apparently" set NifSkope.exe as the default file handler for *.nif, but when I double-clicked on a nif it took me to the File Association dialog and suggested that I use CreationKit instead- and when I (for the 17th time) browsed to NifSkope.exe, it happily accepted that and returned me to the File Association dialog, where NifSkope was not listed at all and CreationKit was highlighted.

In short, Windows is letting me go through the motions, and then completely ignoring my selection.

I'm runniing Windows 7 Home x64 SP1 updated through this morning. I ran sfc /scannow and it found nothing amiss, amuck or awry.

I can open the nif by launching NifSkope.exe first and browsing to the nif file, but that is a pain in the WinTen - I really need help figuring out some way to force Windows, kicking and screaming, into just doing its job.

Thanks in advance for any help.


UPDATE: Pls see new comment below. Thanks to all who responded.

 

[iko22]

Hi Hoggy Dog

Sounds to me like you have two choices:

1) Follow Option Two :ar: Set File Association to Default Program, or

2) Completely Uninstall and Reinstall NifSkope. File Associations could be set that way.


Hope that helps.

 

[SIW2]

You can use cmd prompt.

E.G. Type

assoc .txt

It will return .txt=txtfile

Then type what you want to associate txtfile with - using full path to executable as follows:

ftype txtfile="C:\Program Files\Notepad2\Notepad2.exe" "%1"

It will return txtfile="C:\Program Files\Notepad2\Notepad2.exe" "%1"
so you know it has worked.



It is not impossible that another program will later on associate itself with the filetype - particularly if you install it later. In which case, you can run those 2 commands again.

 

[Hoggy Dog]

I somehow stumbled into a way to set it, and I'm sorry that I have no idea how I did it. I tried literally everything short of reinstalling Windows, and after trying several options in a row, I tested and found that the file association refusal had been overcome and NifSkope was (and still is) correctly associated with nif meshes, Thanks.

 

[Snick]

Gotta love Windows!