SHIII.exe...takes 2 double clicks to start?

prowler3 · 01-24-21, 03:37 PM

I have a clean, unmodded install of SHIII (1.4b) with no Starforce protection.
SHIII is installed on it's own, dedicated HDD and my OS is Windows 7 Ultimate.

I am looking forward to getting back into SHIII and will be using GWX 3.0 supermod along with a widescreen GUI mod and some other smaller mods.

Before I touch this clean SHIII install, I have a minor annoyance that I want to clear up before I start modding.

Double-clicking the "SHIII.exe", the first time, does nothing. Whether it's the actually exe or a shortcut...nothing much seems to happen...maybe a bit of HDD access but game will not open. Double-clicking a second time on the EXE or shortcut opens the game immediately.

This may be some Windows 7 UAC stupidity...I don't know as no errors come up on first attempt. It's a minor annoyance BUT...I would like to ensure it is not an indication of something importantly wrong with this install before I move ahead.

Any enlightenment is appreciated.

01-24-21, 03:37 PM	#1
prowler3 XO Join Date: Mar 2007 Location: Colorado, for now. Any RED State, ASAP. Posts: 401 Downloads: 77 Uploads: 0	SHIII.exe...takes 2 double clicks to start? I have a clean, unmodded install of SHIII (1.4b) with no Starforce protection. SHIII is installed on it's own, dedicated HDD and my OS is Windows 7 Ultimate. I am looking forward to getting back into SHIII and will be using GWX 3.0 supermod along with a widescreen GUI mod and some other smaller mods. Before I touch this clean SHIII install, I have a minor annoyance that I want to clear up before I start modding. Double-clicking the "SHIII.exe", the first time, does nothing. Whether it's the actually exe or a shortcut...nothing much seems to happen...maybe a bit of HDD access but game will not open. Double-clicking a second time on the EXE or shortcut opens the game immediately. This may be some Windows 7 UAC stupidity...I don't know as no errors come up on first attempt. It's a minor annoyance BUT...I would like to ensure it is not an indication of something importantly wrong with this install before I move ahead. Any enlightenment is appreciated.