title: Firmware update fails from SYSTEM session but works when ran from logged on session?
body: <p>I am using the Lenovo Firmware Update Tool:
  <a href="https://pcsupport.lenovo.com/ca/fr/downloads/ds504448" rel="nofollow noreferrer">https://pcsupport.lenovo.com/ca/fr/downloads/ds504448</a></p>
  
  <p>The goal is to update the docking station's firmware.</p>
  
  <p>The EXACT same script is ran (simply <code>ThinkPad_Hybrid_Dock_TVSU_FW.exe /all /silent</code>):</p>
  
  <p>1-In SYSTEM session (via sccm or scheduled task) it ALWAYS fails with:</p>
  
  <pre><code> Update fail.
  
   Failed to update the Device Firmware.
   Restart this program and try again.
  
   RC:60931
  </code></pre>
  
  <p>2-In a logged on user session, running the EXACT same script in the EXACT same way, it ALWAYS works:</p>
  
  <pre><code> Update success.
  
   Success to update the Device Firmware.
  
  
   RC:0
  </code></pre>
  
  <p>Any idea if this is by design? What could prevent it from running in the SYSTEM account? This destroys the purpose of having a /silent switch. The goal is to deploy the firmware update via SCCM overnight when it's safe to do so. Having to log in and run the command defeats all automation possibilities. We have hundreds of docking stations to update...Right now, we would have to do it manually by logging in and running the script...This is a nightmare.</p>
  
  <p>Also, if I test running the command within a logged on session, let's say userX, it works.</p>
  
  <p>If I run the exact same script with the exact same userX credential but from a Scheduled Task or as a Windows Service, it doesn't work!</p>
  
  <p>It seems there is something in the tool preventing it to run anywhere except from within a logged on session....?</p>
  
  <p>After running PROCMON, something strange is happening. Ran successfully in a user session the log is 61 346 events. There are 14 entries of the software creating and querying it's result file:</p>
  
  <p><a href="https://i.imgur.com/BGcQdTe.png" rel="nofollow noreferrer">https://i.imgur.com/BGcQdTe.png</a></p>
  
  <p>However, in the failed attempt running the same command as SYSTEM, there are a staggering 1 315 989 events (92% of the log) of the application seemingly trying to create that result txt file and failing (the CreateFile operation), i suspect ultimately it times out after trying, oh just over a million times.</p>
  
  <p>Do you have any idea why it could be happening? The SYSTEM account has complete control on that folder's security rights.</p>