Change:
const workspaceTrustEnablementService = new WorkspaceTrustEnablementService(configurationService, environmentService); serviceCollection.set(IWorkspaceTrustEnablementService, workspaceTrustEnablementService); <del> const workspaceTrustManagementService = new WorkspaceTrustManagementService(configurationService, remoteAuthorityResolverService, storageService, uriIdentityService, environmentService, configurationService, workspaceTrustEnablementService); </del> <ins> const workspaceTrustManagementService = new WorkspaceTrustManagementService(configurationService, remoteAuthorityResolverService, storageService, uriIdentityService, environmentService, configurationService, workspaceTrustEnablementService, fileService); </ins> serviceCollection.set(IWorkspaceTrustManagementService, workspaceTrustManagementService); // Update workspace trust so that configuration is updated accordingly

Discussion:
I have a window that should be trusted, but is in Restricted mode. When I click "Trust" on the workspace trust management page, nothing happens. Here's what I'm doing, not sure what is important Clone a the windows remote and open in remote-ssh from a mac Debug the extension, open some folder The folder is already in the trusted list: <img width="1427" alt="image" src="https://user-"But when I click "Trust Parent", that works
I've been hitting this quite regularly for the past few months, also with (Windows) SSH remotes. I haven't been able to nail down what triggers it but give me a few attempts at reopening the remote and it'll always get into the bad untrusted state. Clicking Trust does nothing. In order to "re-trust" the workspace, I need to delete one of the bolded entries and then click Trust. ! Windows 11, VS Code 1.72.1 (user).
Okay I could not reproduce this myself, but my hunch is that this is a drive letter capitalization issue. I do not know why this is inconsistent, however. are you able to reproduce the state still? If so, can you help debug this check
Yeah, it's a drive capitalization issue. My workspace has a capital C:, the trust info has lowercase
! I'm experiencing a similar issue with VScode. It's launching in the restricted mode all the time regardless of whether I hit <kbdTrust</kbdin the past or not. This have been happening over the last few monthes or so already. Event though it's convenient that the vscode is prevented from wasting cpu & i/o time upon launching (I've over 3 apps opened daily) by the trust-wall, I'm still considering this an issue.
are you also using remote ssh?
No, I don't. I don't think that the issue with remote SSH connection.
can you provide more information about your setup. e.g. which patch you have trusted and the path that is being considered "untrusted"
Basically every path I work with everyday. There is also a problem with various tabs that are getting opened everytime computer gets started up. These include "Get started" and "Git Lenses" pages. I have to close them everytime code is started.

<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!