@Laurie-Stearn said in Hibernation Wakeup: UNC File Removed:
triggers a clean boot out of the S4 state, which necessitates the relaunching of N++
With this info, I already have an idea of what might be going on. The clean boot means that all the N++ process data, previously saved by the hibernation process to the Windows file “C:\hiberfil.sys”, is thrown away. So no previously opened files/tabs buffers in N++ available, N++ will start from the scratch with opening its files according to its session.xml file. Unfortunately N++ is updating its session.xml file content only at its regular exit (I was once considering the session.xml update after every successful file opening, but that was rejected for good reasons), not continuously right when a file is opened. So then the N++, after its re-launch, does not have the actual info needed for the opening of all your previous N++ files…
@Laurie-Stearn said in Hibernation Wakeup: UNC File Removed:
Even in this scenario, all local files are still loaded with the relaunch
It will depend on the previous state of your session.xml file. Simple test - if every time you finish work and are about to hibernate, you first exit the N++ and then re-launch it before the Windows hibernation itself - I bet that the session.xml will contain the complete information about your session files and there will not be your described issue…
You can also use the N++ menu > File > Save Session… to always have a fresh backup for your session.
@mkupper said in Hibernation Wakeup: UNC File Removed:
nppLogNetworkDriveIssue.xml
That logging trigger is intended for something else (detection of the last write timestamps for network files), it will not help us here.