try updating msi afterburner, and your radeon software, and your video drivers also.
ah3 runs just fine for me on the latest windows update. im wondering if one of your other programs is interfering.
All are the latest versions running. This is clearly Win 10 interfering w\ the AHIII client auto updater routine on my box. Never had it do this ever until now (been running Win 10 for 3 yrs+ so not new to it), so it's most likely due to some Windows Update that got installed. Was thinking it was Windows Security related (embedded in Win 10) but AHIII (both Dx9 & Dx11) is still checked to be allowed to operate unhindered (but Windows updates this embedded security software regularly so it may still be suspect). My read is that MS wants all software to adhere to the "Windows Store" routine for "security reasons". I'll find out if this was an outlier on the next AHIII vers update...…….
Once I downloaded the full game software install package from the AHIII web site & installed it (to get the latest updated version of AHIII) Win 10 was happy now & all is running well. Now as far as the issue w\ my latest versions of AB & HWINFO64 not hooking into the latest version of AHIII when it starts up now so my overlay will appear, again this is due to an issue related w\ DirectX (also embedded in Win 10)….have been here before (why I updated all to latest versions before this happened as everyone has to try to keep up w\ MS to maintain backwards compatibility w\ Dx9 & Dx11.....if MS had it's way all would be forced onto Dx12 API). I use these 2 softwares for monitoring purposes only (all control is thru AHIII game client\AMD Adrenalin Settings\drivers thru the OS) so it's no big deal if it's not hooking right now.....it'll get sorted out.
I have noticed w\ this latest AHIII vers update something has indeed changed....for the better as I noted that the in game FR has jumped higher when running the Dx11 version on my RX Vega 64 vid card w\ Enhanced Synch enabled driver side. The 3503 vers would run at native monitor RR of 144 Hz (so 144 FPS), now this latest 3507 vers is exceeding the native monitor's RR & is running at 166 Hz or 166 FPS. This is due to AMD's Enhanced Synch now being allowed to unsynch from the monitor's native RR & max out the vid card's ability to process (as Enhanced Synch is coded to do) but still maintain tear free graphics (which it is doing, also as Enhanced Synch is coded to do). Now this could be from Hitech making improvements in the Dx11 version to enhance VR graphics operations that my RX Vega 64's drivers are picking up on (nothing wrong w\ that at all if it is what is occurring as the game does need to move forward) which the latest versions of AB & HWINFO64 can't hook into....yet. But this is the same client software coding used in the Dx9 vers as well (AB & HWINFO64 can't hook into this 1 either now) so the issue IMHO isn't related to the game client per se but it is related to the Windows 10 OS as it handles all Dx calls from the game client then translates them to the AMD vid card drivers (where the AB\HWINFO64 software hooking takes place) to execute so the issue is centered around the OS, not the AHIII game client.
Now this FPS improvement is a good result to have but the OS interference w\ the game client's auto updater routine isn't & this has nothing to do w\ any other software except the OS & AHIII's auto updater routine. I highly suspect a Windows Update that is related to some new security measures that decided that AHIII's updater routine is a "security threat" so it wouldn't allow the game to run to update itself. It would allow the update to occur the old fashioned way so the OS can run it's security checks (as well as any 3rd party anti-virus software running) on the download package before installation (allowing the game software to erase\write files to itself & thus to Windows).
I posted this to bring awareness to this development as I have never seen this behavior before from Win 10 concerning AHIII as others, depending on which version of Win 10 they're using & how they've set it up as far as security goes, may run into this sometime down the line.