sleepmode BigBox Sleep shuts down my PC (possibly Hibernate?)

[NatEl]

When I'm in Big Box, if I choose Sleep, it shuts down my Windows 10 machine.   [Correction: it might be hibernating, not sleeping]. 

I can not wake with keyboard or mouse.   I followed normal instructions, and set it so that the mouse and keyboard can Wake the system, in Device Manager, but it doesn't make any difference.

When I use Sleep directly from Windows, it works fine.  (I can wake it with my mouse).  This makes me think that there's something different about how Sleep works when I do it directly from Windows versus what happens when I choose Sleep mode in BigBox?

This is annoying, because, if I choose Sleep mode through Big Box, I can't wake the machine without opening my Laptop and hitting the power button.  

The only way I can use Sleep Mode is to completely shut down BigBox, then use Windows to tell the machine to sleep.  THEN, it goes into a property Sleep mode, and I can wake it via a USB mouse.  This is not an ideal solution for an arcade build, because I'd need to use the mouse to click back into BigBox every time.

Any ideas on how to troubleshoot this?   I tried same steps on another laptop and it worked fine.

BigBox version: 13.0

windows 10 (fully updated as of 11/25/2022)

Event Viewer shows

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" /> 
  <EventID>187</EventID> 
  <Version>0</Version> 
  <Level>4</Level> 
  <Task>243</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000400000000404</Keywords> 
  <TimeCreated SystemTime="2022-11-25T23:11:38.2645300Z" /> 
  <EventRecordID>18950</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="8928" ThreadID="7624" /> 
  <Channel>System</Channel> 
  <Computer>DESKTOP-HOHLCJ3</Computer> 
  <Security UserID="S-1-5-21-4090141023-304028169-1425888792-1002" /> 
  </System>
- <EventData>
  <Data Name="ApiCallerNameLength">69</Data> 
  <Data Name="ApiCallerName">\Device\HarddiskVolume3\Users\MY_USER_NAME\Desktop\LaunchBox\Core\BigBox.exe</Data> 
  <Data Name="SystemAction">2</Data> 
  <Data Name="LightestSystemState">2</Data> 
  </EventData>
  </Event>
  
  - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" /> 
  <EventID>42</EventID> 
  <Version>3</Version> 
  <Level>4</Level> 
  <Task>64</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000404</Keywords> 
  <TimeCreated SystemTime="2022-11-25T23:11:40.2864996Z" /> 
  <EventRecordID>18951</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="4" ThreadID="220" /> 
  <Channel>System</Channel> 
  <Computer>DESKTOP-HOHLCJ3</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data Name="TargetState">5</Data> 
  <Data Name="EffectiveState">5</Data> 
  <Data Name="Reason">4</Data> 
  <Data Name="Flags">0</Data> 
  <Data Name="TransitionsToOn">9</Data> 
  </EventData>
  </Event>
  
  - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" /> 
  <EventID>107</EventID> 
  <Version>1</Version> 
  <Level>4</Level> 
  <Task>102</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000444</Keywords> 
  <TimeCreated SystemTime="2022-11-25T23:11:40.7898923Z" /> 
  <EventRecordID>18952</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="4" ThreadID="220" /> 
  <Channel>System</Channel> 
  <Computer>DESKTOP-HOHLCJ3</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data Name="TargetState">5</Data> 
  <Data Name="EffectiveState">5</Data> 
  <Data Name="WakeFromState">5</Data> 
  <Data Name="ProgrammedWakeTimeAc">0828-09-14T02:48:05.4775807Z</Data> 
  <Data Name="ProgrammedWakeTimeDc">1601-01-01T00:00:00.0000000Z</Data> 
  <Data Name="WakeRequesterTypeAc">1</Data> 
  <Data Name="WakeRequesterTypeDc">0</Data> 
  </EventData>
  </Event>

Edited November 26, 2022 by NatEl
Giving clarification on the issue.