Notepads
Notepads copied to clipboard
Notepads process "suspended" after reboot [Win 10 2004]
I started noticing that after a reboot, when I start Notepads for the first time, I get the message "This is a shadow window of Notepads...". Looking at the task manager after a reboot, even before running Notepads, the process under "Processes" has a green leef next to it (suspended). I can fix the issue by ending the process after a reboot, or stopping the app from running in the background. I was wondering if this is normal behavior.
Issue-Label Bot is automatically applying the label bug
to this issue, with a confidence of 0.65. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
I can't verify this with a normal reboot on 2004. Did you maybe mean standby mode?
Please see below. I enabled Notepads to run in the background and rebooted. This is right after. Again, when I open Notepads, I get the message "shadow window...". Note that I did a fresh OS install a few days ago. I only installed a few programs, but I don't think anything I have could do this.
If you open the app, it should get get status "running". This is a feature from Store apps. Nothing wrong with
The status does become "Running" when I open it. The problem is that when I open it, I can't change the settings. It always opens as a shadow window, unless I manually end the process in Task Manager before opening it. As I mentioned, a workaround that I'm ok with is to prevent the app from running in the background.
Did you enable windows 10 hibernation? I knew some people might encounter it now and then but it is super rare and I do not know why this is happening. We might be able to fix it with proper handling logic in suspended call back but I do not know how. However, we have a PR to actually fix the "shadow window" issue in your case: https://github.com/JasonStein/Notepads/pull/621 @soumyamahunt FYI.
I see. Good to know. And yes, I have hibernation enabled.
For what it's worth I have the exact same problem. The only way to open a non-shadow instance is to kill the process manually and then run it regardless of power state. Win10 21H2 build 19044.1889