The Windows sandbox status panel loads its data more directly, with less flicker-prone wiring.
What's wrong with this entry?
The Windows sandbox status component takes a statusPromise and unwraps it with React's use, replacing the local state plus effect probe.
- dependency checking moved behind helpers that return an early result rather than re-seeding sandbox config inline
- Windows sandbox UI only
statusPromise
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Windows policy helpers can be PowerShell scripts
Both mention window
-
v2.1.234
Windows sandbox refusals now say why an exclusion did not apply
Both mention window
-
v2.1.234
Terminal is restored on Ctrl+Break on Windows
Both mention window