A successful CreateProcessW call using the documented LPAC attribute combination is the supported creation mechanism; current public documentation does not provide a separate, supported Win32 query that independently attests the suspended child’s LPAC state.
Class 46 on build 26300.9457
TokenIsLessPrivilegedAppContainer appears in the Win32 TOKEN_INFORMATION_CLASS enumeration, and the Win32 page explains that LPAC excludes access granted through ALL_APPLICATION_PACKAGES. However, unlike TokenIsAppContainer, it does not define the class-46 output buffer, size, interpretation, minimum supported build, or class-specific errors ^1^.
The DWORD/nonzero description comes from the WDK ntifs.h documentation for native/kernel token-query interfaces. That documentation does not establish that the same payload contract applies to user-mode GetTokenInformation ^2^.
The general GetTokenInformation contract establishes only that:
- Classes other than
TokenSourcerequireTOKEN_QUERY. - Buffer lengths are expressed in bytes.
- A successful call returns nonzero.
- A failed call returns zero, after which
GetLastErrorsupplies the error ^3^.
It does not fill in the missing class-46 contract. Therefore:
- No documented additional access right, architecture restriction, or buffer requirement can be identified for class 46.
-
ERROR_INVALID_PARAMETERdoes not, by itself, prove malformed storage or insufficient token access. - The output
DWORDandReturnLengthmust not be consumed after failure. - Replacing the SDK enum with the literal value
46does not make the query supported.
Testing reported for nearby Windows 11 build 26200 found that both GetTokenInformation and the underlying native query rejected class 46 across multiple token types and buffer sizes, including an LPAC token. The native result was consistent with STATUS_INVALID_INFO_CLASS, which maps to Win32 error 87 ^4^. That is strong corroboration for your result, but it is not an official compatibility statement specifically for build 26300.9457.
Documented LPAC creation guarantee
Your creation sequence matches the documented LPAC mechanism:
- Supply
PROC_THREAD_ATTRIBUTE_SECURITY_CAPABILITIESwith the AppContainer SID and selected capabilities. - Supply
PROC_THREAD_ATTRIBUTE_ALL_APPLICATION_PACKAGES_POLICYwithPROCESS_CREATION_ALL_APPLICATION_PACKAGES_OPT_OUT. - Pass the attribute list through
STARTUPINFOEX. - Call
CreateProcessWwithEXTENDED_STARTUPINFO_PRESENT.
Microsoft’s launch documentation states that opting out of All Application Packages specifies that the new process is an LPAC and that the process-creation attributes create the AppContainer environment, including its token and object namespace ^5^.
Accordingly, the documented fail-closed boundary is the return from CreateProcessW, not a subsequent class-46 query:
if (!CreateProcessW(appPath, commandLine, nullptr, nullptr, FALSE,
EXTENDED_STARTUPINFO_PRESENT | CREATE_SUSPENDED,
environment, currentDirectory,
&startupInfo.StartupInfo, &processInfo)) {
return GetLastError(); // No child to trust or resume.
}
// LPAC was requested through the documented creation contract.
ResumeThread(processInfo.hThread);
Continue querying TokenIsAppContainer if independently confirming the broader AppContainer property is useful, but a successful result distinguishes only AppContainer from non-AppContainer—not LPAC from ordinary AppContainer.
If independent post-creation attestation is mandatory
The public Windows API documentation does not currently establish any of these as a supported LPAC discriminator:
-
GetTokenInformationclass 46 with a defined Win32 retrieval contract; - another purpose-built Win32 token query;
- a token security-attribute inspection technique;
- an access check that proves the general LPAC property.
An access check against a particular object can validate access to that object, but it is not documented as attesting the token’s LPAC classification. The broader review of available APIs reached the same conclusion: no separately documented user-mode method currently establishes that an existing token is LPAC ^6^.
If policy requires independent attestation rather than reliance on the documented creation contract, retaining the suspended child and terminating it when class 46 fails is fail-closed, but there is no documented public API path to make that verification succeed. A Windows developer support case is required for a formal build-specific ruling or a supported alternative; include the exact build, architecture, SDK version, native status if captured, and a minimal reproducer.
References
- TOKEN_INFORMATION_CLASS enumeration (winnt.h)
- TOKEN_INFORMATION_CLASS enumeration (ntifs.h)
- GetTokenInformation function (securitybaseapi.h)
- GetTokenInformation: supported contract for TokenIsLessPrivilegedAppContainer (class 46) - Microsoft Q&A
- Launch an AppContainer
- Supported user-mode method to distinguish an LPAC token from an ordinary AppContainer token - Microsoft Q&A