title: How to force `findstr` to ignore `Cannot open` returns
body: <p>I'm trying to use <code>findstr</code> to search inside a folder looking for some string:</p>
  
  <pre><code>findstr /spin /c:"string" *
  </code></pre>
  
  <p>however it returns back with a lot of <code>Cannot open</code> errors which make it difficult for me to find the exact matches found. </p>
  
  <p>When using <code>Cmder</code> command:</p>
  
  <pre><code>grep -r "string" .
  </code></pre>
  
  <p>I got <code>Permission denied</code> error for the same folders. If I use the command:</p>
  
  <pre><code>grep -rs "string" .
  </code></pre>
  
  <p>it gives me the results nice and clean. Is there a similar flag for <code>findstr</code> or a combination of <code>cmd</code> commands to do the same?</p>
  
  <p>there are already some posts for <code>findstr</code> <code>Cannot open</code> error, explaining what is wrong and how to solve it, but I don't care why it is happening. I just want the command to ignore the <code>Cannot open</code> lines and prints out just the lines with exact matches.</p>