Skip to content

Commit d5866ba

Browse files
Update nf-netfw-networkisolationenumappcontainers.md
We had a software vendor ask about this, and it isn't clear to me from the current doc description what to do. Looking at our current implementation, it appears that NetworkIsolationFreeAppContainers would be the correct call for freeing the memory. Not freeing it in any way results in a memory leak.
1 parent f6ac37c commit d5866ba

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

sdk-api-src/content/netfw/nf-netfw-networkisolationenumappcontainers.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -88,12 +88,12 @@ ERROR_OUTOFMEMORY will be returned if memory is unavailable.
8888

8989
## -remarks
9090

91-
If no app containers are installed on the system, ERROR_SUCCESS will still be returned (and <i>ppPublicAppCs</i> will be empty).
91+
If no app containers are installed on the system, ERROR_SUCCESS will still be returned (and <i>ppPublicAppCs</i> will be empty). If ppPublicAppCs is not empty, <a href="https://docs.microsoft.com/en-us/windows/win32/api/netfw/nf-netfw-networkisolationfreeappcontainers">NetworkIsolationFreeAppContainers</a> should be used to free the memory when you are done using it.
9292

9393
## -see-also
9494

9595
<a href="/windows/desktop/api/netfw/ns-netfw-inet_firewall_app_container">INET_FIREWALL_APP_CONTAINER</a>
9696

9797

9898

99-
<a href="/previous-versions/windows/desktop/api/netfw/ne-netfw-netiso_flag">NETISO_FLAG</a>
99+
<a href="/previous-versions/windows/desktop/api/netfw/ne-netfw-netiso_flag">NETISO_FLAG</a>

0 commit comments

Comments
 (0)