The Windows "files may not sync back" warning no longer appears when sync was never armed.
What's wrong with this entry?
The one-shot Windows warning that files may not sync back from a cloud session is now suppressed when directory sync reports itself as not armed, not just when it is switched off.
- Not-armed reasons include
no_container_origin,detached_headandprobe_failed.
not_armed
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.236
Windows sandbox runtime now installs machine-wide
Both mention window
-
v2.1.239
PowerShell path checks distinguish a timeout from an error
Both mention window
-
v2.1.239
Windows pipe names no longer mangled by locale-specific lowercasing
Both mention window