<SOLUTION>
I did some testing in my test lab and confirmed your comment about response buffer limit is the correct solution. I have been plagued with this issue for three years. I revisited this issue this year because my users are still complaining that the web page hangs up for 3 minutes while a process is running. My web page was designed to show the user STEP01, STEP02, STEP03 progress along with OK or ERROR at each step. After upgrading to IIS 7.5 this completely broke and I was lost to figure out how to fix it without rolling back. I wanted to either 1) start the process and move on or 2) Provide step-by-step feedback while the job is running. Both solutions require the RunShell() with @NOWAIT or the Run() to be used. The RunShell() with @NOWAIT feature was not working correctly and would hang until the command was done executing. Once I made the following changes the web page was interactive and the RunShell @NOWAIT would move smoothly past the command execution and leave it to complete while the web page and WebBatch continued moving forward. This solution works for IIS 7.5+
1. Open IIS Manager and go to Connections > WebSite > Handler Mappings and click on the webcgi subfolder from the root. Go to Handler Mappings and look at the CgiModule handler. Get the name of the handler. Mine is CGI-exe.
2. Open a cmd as administrator
3. cd c:\windows\SysWOW64\inetsrv
To Get Current Setting
4.
appcmd.exe list config /section:handlers | Find "CGI-exe" My before change setting:
<add name="CGI-exe" path="*.exe" verb="*" modules="CgiModule" resourceType="File" requireAccess="Execute" allowPathInfo="true" />To set the response buffer limit to 0
5.
appcmd.exe set config /section:handlers "/[name='CGI-exe'].ResponseBufferLimit:0" My after change setting:
<add name="CGI-exe" path="*.exe" verb="*" modules="CgiModule" resourceType="File" requireAccess="Execute" allowPathInfo="true" responseBufferLimit="0" />6. Done!
</SOLUTION>
When you compare the two outputs from step 4 and step 5 and you will notice after the change that the CgiModule has the responseBufferLimit set to "0". This is all that was needed to get the web page to be interactive. Now I can kick off a process without having the user wait for the response in IIS 7.5. Just in time to upgrade to IIS 10.

Happy 2018! Best Regards,
Bruce