You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit cc05937
Browse filesBrowse the repository at this point in the historyBrowse files
Fix: Neighbor Table runspace cached after a failed start
A failed start of the PowerShell runspace (e.g. Import-Module NetTCPIP) was cached
by Lazy<T> until the application was restarted. Create it on demand inside the
existing RunspaceLock and recreate it if it is not open.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: Website/docs/changelog/next-release.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -115,6 +115,10 @@ Release date: **xx.xx.2026**
115
115
116
116
- Fixed errors when changing the network configuration (e.g. missing permissions) not being shown — the change was reported as successful although it failed. The error message of Windows is now shown. [#3606](https://github.com/BornToBeRoot/NETworkManager/issues/3606)
117
117
118
+
**Neighbor Table**
119
+
120
+
- Fixed adding and deleting entries not working until the application was restarted if loading the PowerShell module `NetTCPIP` failed once.
121
+
118
122
**Dashboard**
119
123
120
124
- Fixed the **Network Connection** widget running a full connection check on every application startup, even if the Status Window or Dashboard was never opened. It now only checks when actually shown - via the tray icon, on a network change, or when the Dashboard tab is opened. [#3553](https://github.com/BornToBeRoot/NETworkManager/pull/3553)
0 commit comments