Inventor 2024 won't associate with .stp or .step files in Windows Explorer.

Inventor 2024 won't associate with .stp or .step files in Windows Explorer.

dlandisadaptek
Advocate Advocate
932 Views
2 Replies
Message 1 of 3

Inventor 2024 won't associate with .stp or .step files in Windows Explorer.

dlandisadaptek
Advocate
Advocate

Installed recently and are now using Inventor 2024 in Windows 10 Pro.

 

Attempted to use "Open With" on a .step file to re-associate them with Inventor 2024 from 2023 but Inventor 2024 is not available on the "More Apps" list.  So, I select "More Apps on this PC" and browse to the Inventor 2024>BIN folder, find the Inventor.exe file in there and select it... voila Inventor 2023 opens, not 2024.

 

I attempted to use Windows "Choose Default Apps by File Type" but found that Inventor 2024 is not available as a selection for .step files there either.  Inventor 2024 "Read Only" is available but I don't want to open it read only.  The only other option is "Look for an app in the Microsoft Store".

 

Any suggestions?  Is there any other way to associate Inventor 2024 to various file types?

0 Likes
Accepted solutions (1)
933 Views
2 Replies
Replies (2)
Message 2 of 3

Gabriel_Watson
Mentor
Mentor

Have you tried right-clicking a sample file and then go to "Open With" > Choose another app (bottom option) > pick C:\Program Files\Autodesk\Inventor 2024\Bin\Inventor.exe , selecting "Always"?

0 Likes
Message 3 of 3

dlandisadaptek
Advocate
Advocate
Accepted solution

Absolutely.  Just as you described, navigating to the 2024 Inventor "BIN" folder and selecting Inventor.exe opened Inventor 2023 instead.  I likely won't be able to debug further because I just gave up and un-installed 2023.  Now I can select 2024 since it's the only available option.  I don't understand why 2024 wasn't an option until 2023 was removed but... had to find a work around and I'm now able to double-click a file in Windows Explorer and it opens in Inventor 2024.

 

First version upgrade that this has been an issue with.  Probably a Windows issue.

 

Thanks for the suggeston.