title: vba shell command unexpectedly terminates excel with no error message
body: <p>I had a vba macro that previously launched a .bat batch file using the shell command.  </p>
  
  <p>The form of shell command used was very simple (as shown):</p>
  
  <pre><code>dblResult = Shell("c:\fullPath\batchFile.bat")
  </code></pre>
  
  <p>All of a sudden this has stopped working, with the excel application closing unexpectedly at this line of code, without error or warning message and before the command window opens for the batch file to begin executing its DOS commands. </p>
  
  <p>The batch files will still run successfully if launched manually rather than from the excel VBA macro.  </p>
  
  <p>This ran on a corporate workstation so I'm wondering if there may have been any system changes made by security updates that now prevent what might be perceived as a risky behavior from an application.</p>
  
  <p>Has anyone else encountered this issue?</p>
  
  <p>Addendum 2017-09-06 :</p>
  
  <p>The fault with VBA shell command closing/crashing excel was first noticed just after 10th July and was found to be also manifest across other Windows 7 machines in the business. </p>
  
  <p>Today a corporate Windows 7 laptop, which when previously tested was found to have the same issue has now since (mysteriously) reverted back to the Shell command working again.</p>
  
  <p>The only difference between the laptop for which the shell command is functioning and the desktop where it crashes the Excel application is a Windows Security update KB3203468 which was automatically installed on the (working) laptop 25th July, which I believe post-dates the time when the laptop was first tested and found to display the same problematic behavior.</p>
  
  <p>At the moment this is the only lead towards solving this, and the description on the update given refers to </p>
  
  <p>"A security vulnerability exists in Microsoft Office 2010 32-Bit Edition that could allow arbitrary code to run when a maliciously modified file is opened. This update resolves that vulnerability."</p>
  
  <p>which seems to be in the right ball park of what is being affected, namely VBA for applications.  </p>
  
  <p>Interestingly the published issue date of the update is 11th July coinciding with the problem first occurring, even while it appears to have been responsible for resolving the issue on the laptop.</p>
  
  <p>Unfortunately any attempt to install this update on the desktop (as administrator) to verify if this resolves the problem closes with message 'There are no products affected by this package installed on this system' and so it fails to install.</p>
  
  <p>A corporate IT guy is looking into it....</p>