Apps hang after resume from hibernation

Apps that have files open over the network hang after a resume from hibernation, even though the server has been up the whole time. It might even affect apps that simply try to access the network over a connection that no longer exists, including possibly explorer.

Presumably, this is due to the handles becoming stale.

Is there a way to force all apps to renew their file handles upon resume from hibernation, or otherwise fix this?

Unfortunately, many apps have the philosophy that they need to keep files open all the time, not just when they want to write or read them.

This is on a Dell xps15 9500 winver 20h2 19042.804

Thanks.

--peter

I assume by "Apps" you're referring to MS store apps and not to Win32 desktop programs?

If so head to:
Settings -> Accounts -> Sign in options

Here toggle ON option:
Automatically save my restartable apps when I sign out and restart them after I sign in.

zebal said:

I assume by "Apps" you're referring to MS store apps and not to Win32 desktop programs?

If so head to:
Settings -> Accounts -> Sign in options

Here toggle ON option:
Automatically save my restartable apps when I sign out and restart them after I sign in.

Sorry, I was referring to desktop programs, i.e. application programs, i.e. apps, but not those from MS Store. Maybe in the future, I should refer to them as progs, not apps.

yes, desktop programs are those "normal" programs and apps are store apps (even though MS is pushing people to call them both "apps" which is ofc. wrong)

AFAIK you can't force programs to renew handles except to restart them.
programs are supposed to check if the handle is valid and create a new one if not, also programs are supposed to reopen network socket as well, at least well written programs should do that or at least prompt for user action.

Programs can handle handle OS power events, but you can't do it externally if the program was not designed so or if at least does not provide user options to configure this.

It could help if you share what kind of programs are you talking about, because there are options related to desktop programs in Windows that control their behavior as well, maybe you turned off some of these.

You can find them under "privacy" in Settings app.

Thanks. The info about what progs are supposed to do when returning from a power state is very helpful.

Well, a number of programs, for example:

gnu emacs 26 ( which usually doesn't keep files open as far as I know, but saves checkpoints periodically)
turbotax
foxit pdf viewer
explorer (!)

Sometimes it's hard to know whether a program is hung, or just taking an hour in "not responding" state.

As far as privacy settings, the top level ones are ads and language list off, track app launches and settings suggestions on. These seem to all relate to browsers.

I did notice in event viewer that Office 365 was generating some license errors on resume. Since I have no use for that app/prog/spyware/virus, I have since uninstalled it. I was not running it, but I guess it normally has some service always going.

Oh, Edge browser was running at the time, and had no problem resuming, as did several other progs such as process explorer, process hacker, task manager. Those of course have no need for network files.

I'm sorry but don't know whether the issue is with programs or network.

Sometimes it's hard to know whether a program is hung, or just taking an hour in "not responding" state.

sounds like "network resource not available"

As far as privacy settings, the top level ones are ads and language list off, track app launches and settings suggestions on. These seem to all relate to browsers.

These relate to store apps, for desktop programs there are only 2 options under "microphone" and "location", MS Edge (desktop program) is configurable in "location" section, this options are new and 99% of desktop program are not aware of these options yet.

I think you can try to confirm whether network works during resume of OS, if it does network programs should handle the issue, at least most MS services and built in software does this.

Thanks.

Yeah, probably the network. I think that one thing that happens is it can take inexorably long for the network connections to re-authenticate. I've noticed in the past that if I manually establish a connection at the server to the client, then the client can establish a connection the other way faster or at all. The fact that I have at least one network drive mapped to a drive letter seems to also cause problems when reconnecting, even though or maybe because it is configured to reconnect at logon and/or startup (I forget which). Doesn't seem to matter whether I have set it up from the 'map network drive' ui, or using net use at the cmd line. Presumably, they do the same thing, but with windows ya never know.

Unfortunately, I have always found windows network configuration an opaque mystery, the main problems being just exactly how authentication is done, especially when the server and client are different versions of windows. There is also the issue that I have multiple machines on my network, some of which are asleep at random times, and it's never clear which one is supposed to be the 'browser master', whose function I don't really understand.