What's wrong with this entry?
Windows sandbox commands now support per-exec denyRead and denyWrite path lists, matching Linux/macOS behavior.
- Previously, Windows sandbox was deny-listed only at the session level
- Now individual exec calls can pass
filesystem.denyReadandfilesystem.denyWritepath arrays filesystem.allowRead(re-allow within denyRead) is still not supported on Windows — remove entries or narrowdenyReadfilesystem.allowWriteis still not supported on Windows (Windows sandbox uses deny-list only)
Error messages (search for "Per-exec filesystem.allowRead (re-allow within denyRead) is not supported on Windows")
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.