Windows Companion v2026.7.1-4: pending DACL recovery on Google Drive prevents validation on local NTFS

I need a supported procedure for resolving a pending DACL recovery entry associated with a Google Drive virtual volume, without accessing that volume or changing its permissions or contents.

Environment

• OpenClaw Companion: v2026.7.1-4. The updater reports that it is up to date.
• Local Gateway: v2026.6.34, running through WSL.
• Windows: 25H2, build 26200.9168.
• Executor: mxc-direct-appc, configuration schema 0.7.0-alpha.
• Detected isolation tier: appcontainer-dacl, needsDaclAugmentation=True.
• Companion runs under my Windows account, without administrator elevation.

Sequence of events

1. Initially, the following Google Drive virtual folder was granted sandbox access:
   H:\My Drive\SISTEMA EMPRESARIAL IA\AI_HUB
2. The execution test failed while applying DACL permissions.
3. H: was removed from the authorized folders. Only C:\AI_HUB was then configured, with Read & write access.
4. Subsequent execution attempts still tried to recover pending permissions on H:, even though the requested commands referenced only C:.
5. Those attempts also reported missing WRITE_DAC permission on C:\AI_HUB.
6. My Windows account was subsequently granted an explicit Allow: Change permissions entry on C:\AI_HUB, applying to the folder, subfolders, and files. Inheritance was verified on FINAL.
7. No OpenClaw execution test has run since that permission change. The agent declined to launch another test because it could not guarantee that the executor would avoid automatic recovery on H:.

Observed errors

DACL recovery: 1 file(s), 0 ACE(s) restored, 0 pruned (missing), 1 error(s)

restore \\?\H:\My Drive\SISTEMA EMPRESARIAL IA\AI_HUB:
SetNamedSecurityInfoW: WIN32_ERROR(87)

BaseContainer is unavailable; DACL fallback requires write-DAC
permission on 'C:\AI_HUB', which the current user lacks
(ERROR_ACCESS_DENIED (WRITE_DAC not granted)).

The WRITE_DAC error occurred before the explicit permission was added. Whether it persists is unverified.

Current state

• Node mode is disabled; the Gateway remains intact.
• The Sandbox remains enabled.
• The only authorized custom folder is C:\AI_HUB, with Read & write access.
• Documents, Downloads, and Desktop remain blocked.
• Internet access is disabled; clipboard access is None.
• C:\AI_HUB resides on NTFS and contains the eight intended subfolders.
• A manual TXT create/read/delete test completed successfully.
• No recovery records have been deleted, identities reset, or components reinstalled.

Assistance requested

1. Where and how does this version persist pending DACL recovery state?
2. Is there a supported way to inspect that state without triggering recovery or accessing H:?
3. Can only the H: recovery entry be removed or quarantined, with a backup and a reversible procedure?
4. Is there a published release that fixes this behavior? Please specify the exact version and Windows requirements.
5. How should isolated execution restricted to C:\AI_HUB be verified afterward?

The solution must preserve the Gateway, pairing, files, and sandbox isolation. Accessing H:, running the application permanently as administrator, or disabling the Sandbox is not authorized.

Available evidence

An openclaw-tray.log copy containing entries through September 7, 2026, at 11:36 AM, America/New_York. The last recorded execution attempts ended around 11:06 AM, before the permission adjustment. Screenshots of the errors and configuration are also available.

Start by reviewing the supplied openclaw-tray.log and screenshots, focusing on the DACL recovery and WRITE_DAC errors and the recorded execution attempts. Determine where this version persists pending recovery state and whether it can be inspected or safely quarantined without accessing H:. Done means documenting a supported, reversible procedure, any fixed release and Windows requirements, and verification that execution is restricted to C:\AI_HUB while preserving the Gateway and Sandbox.