title: Windows: Does something temporarily grab the com ports on startup?
body: <p>I have a WPF/C# app that is launched as part of the "Startup" group on a Windows Embedded Standard machine. One of the first things the app does (in its static App() method) is create a new SerialPort object for COM1. COM1 is a hardwired serial port, not a USB virtual port or anything like that.</p>
  
  <p>My problem is that every so often (maybe 1 out of 12) on startup, I get an exception: 
  System.UnauthorizedAccessException: Access to the port 'COM1' is denied.</p>
  
  <p>There are no other applications using this port. Also, when I relaunch the app following this error, it grabs the port just fine. It's as if the com port isn't ready/set up for my app sometimes. </p>
  
  <p>I'm clueless on this one! Any insight is appreciated!</p>
  
  <p>UPDATE: I added a call to SerialPort.GetPortNames() and printout all available ports before attempting to open the port. In the failure case COM1 is indeed THERE! So, it's not that the port isn't ready. It looks like something in Windows is actually grabbing the port temporarily and blocking me.</p>