ID 532049 - Nuke's MSI installer doesn't register Nuke as the default app for .nk files when installed on Windows

Problem summary:
Nuke's MSI installer doesn't register Nuke as the default app for .nk files when installed on Windows
 
Customer reported version:
Nuke 14.0v1
 
Customer reported platform:
Windows 11
 
Steps to reproduce:
1) Have a version of Nuke prior to 14.0v1 installed, such as 13.2v5
2) Download and install Nuke 14.0v1 with default settings
3) Launch Nuke and save a .nk file to the Desktop with File > Save Comp
4) Double click the file on the Desktop to launch Nuke
 
Expected behavior:
Nuke Scripts should be associated with the most recent installed version and open that version when selected
 
Actual behavior:
Nuke scripts are opened with the previous installation of Nuke, not Nuke 14.0v1
 
Workaround:
Changing the Windows file association for the correct version allows .nk files to be opened in the specified version. For more information on this, please review the following KB or non-registry options below:
Q100576: Setting the default .nk script launchers for Nuke/NukeX
 
Non-Registry options:

Windows 10
1) Locate and Right-Click a Nuke script that has the .nk extension

2) Select the Open with... option and check the box labeled Always use this app to open .nk files.

3) If Nuke14.0 isn't an option, click on More apps and then select Look for another app on this PC

4) Navigate to your Nuke installation directory and select the Nuke14.0.exe file

5) Click Open and Nuke 14.0v1 will be the default app for .nk files

 

Windows 11

1) Locate and Right-Click a Nuke script that has the .nk extension

2) Hover over Open with and select Choose another app

3) If Nuke14.0 isn't an option, scroll down and select Choose an app on your PC

4) Navigate to your Nuke installation directory and select the Nuke14.0.exe file

5) With Nuke14.0 now selected, click the Always button to make Nuke14.0v1 the default app for .nk files

Reproduced by Support in:
Nuke 14.0v1 - Windows 10, Windows 11 - Regression
 
Unable to reproduce bug in:
Nuke 13.2v5 - Windows 10
 
Earliest version tested:
Nuke 13.2v5 - This feature (MSI installer) did not exist in this version and the issue has regressed