Windows 10: Issue in opening Program in wrong version.

ho2.exe is a c# program I wrote (VS 2017 Community), at the moment installed in version 1.6 . Months ago, when it was version 1.1, I associated the extension .ho2pro with this program. Now, when I double click a file *.ho2pro, ho2.exe starts, but with the old version 1.1 . Installed program is only the new version, dont know where he gets the old one. I tried several times in several ways to change the association, but without success. The system offers only a generic ho2.exe as default app. What can I do?






***Modified Title from: default app wrong version***

:)

 

Catalyst reporting wrong version fix

I think there was a similar issue that was never reported with the 12.2s, cause IIRC, when I opened CCC with those, it reported the package version as 12.3. Honestly, if the actual driver version rather than package version is listed correctly, then I wouldn't worry too much about it.

 

Catalyst reporting wrong version fix

Just thought I'd make a topic for this, as it seems, a few people, have this issue.

This an official response from AMD support.

Most people so far have been reporting that Catalyst 12.4 is installed, but continues to show as 12.3 Suite in the CCC software. It's a known issue, but the drivers are installed correctly.

After installing 12.4, compare the DRIVER version to the version listed on the release notes for 12.4. You can also check the driver version in Device Manager for that video card. If it is installed, it should list the version correctly.

Try these uninstall steps first, however:

**********
1. Download the WICU.
http://www.softpedia.com/get/Securit...-Utility.shtml

2. Uninstall everything related to ATI/AMD and reboot through programs and features in the Control Panel (programs and features).
Use DriverSweeper (freeware) to remove any remnants of AMD (check the "AMD Display" box) (_Please visit us at treexy.com).

3. Launch WICU and delete anything related to ATI/AMD/CCC.

4. Delete all ATI/AMD folders in "C:\Program Files" and "C:\Program Files (x86)".

5. Boot into safemode and navigate to the "C:\Windows\Assembly" folder and delete any assemblies which have the public token key "90ba9c70f846762e". It is possible that you won't find any, but check it.

6. Reboot.

7. Install the Catalyst package again. It should work now.

*Toast :toast:

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.