==================== Type: Bug Overview: Must kill Discovery Launcher and then open it in order to use it in a Fast Startup boot on Windows 10 Pro ====================
In a Fast Startup boot on Windows 10 Pro, the Discovery Launcher must be opened, killed on Task Manager, and then opened again so it becomes usable. On the first launch, the program's process gets stuck somewhere with 13~16 MB of allocated memory, consistently. This doesn't happen on the second and further launches of the program.
In a Fresh boot, the Launcher works on its first try. Many programs on Windows 10 have similar problems because of this Fast Startup feature - for example, reFX Nexus refuses to load files after a few Fast Startup cycles and only starts to work again on a fresh boot. I don't know if this also happens with Windows 8's Fast Startup.
How to replicate from an existing Windows 10 Pro installation with Discovery installed:
1. Boot from a Fast Startup.
2. Try to open the Discovery Launcher. The icon may or may not appear on the tray for a split second, and the process will be stuck on the Task Manager.
Current workarounds:
-Restart the computer either by cutting its power, or Restarting through the start menu, or with "shutdown /s /f /t 0".
OR
-Kill the process then open the Launcher again.
OR
-Disable Fast Startup. This can be very annoying for people like me who have slow PCs without a SSD.
I spent a while looking into Fast Boot / Fast Startup; even tested it on my own machine a little. It's riddled with issues, and DSLauncher isn't the only one that has a problem with it. I couldn't say for certain what causes it, but I don't think it's my code directly responsible. Most likely a framework issue. It's out of my hands from what I can tell. ~Laz
