Hi @Karen3D — one more angle worth checking, specific to the Windows 11 update scenario: session.xml is only written when Notepad++ exits cleanly. Windows updates are notorious for restarting the machine and killing running apps before they can save, so the session file can end up out of date or empty even with “Remember current session for next launch” ticked.
A couple of quick checks that fit an IT-managed work laptop:
Close Notepad++ yourself before restarting or shutting down, and confirm in Task Manager that no notepad++.exe process is left hanging around. A leftover process can hold on to the old session.
Open a couple of files, close Notepad++ normally, then check the timestamp on session.xml in %AppData%\Notepad++. If it has not been updated, the write itself is being blocked — roaming profiles or redirected folders on corporate machines are a classic cause.
If your files live on network drives, make sure the drive mappings are unchanged after the update. Notepad++ quietly skips files it cannot find at start-up.
Worth ruling these out before going any deeper.