You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the root, run node build/lib/policies (or node build/lib/policies win32 if this PR is merged)
Note that the files generated in .build/policies/win32/<some-locale> for AllowedExtensions have a description of "No extensions are allowed".
That string is coming from here, and what should be selected is apparently this string - the more friendly:
"Specify a list of extensions that are allowed to use. This helps maintain a secure and consistent development environment by restricting the use of unauthorized extensions. For more information on how to configure this setting, please visit the Configure Allowed Extensions section."
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.98.1. Please try upgrading to the latest version and checking whether this issue remains.
Does this issue occur when all extensions are disabled?: Yes
Some descriptions fetched in the policy generating script are incorrect.
Steps to Reproduce (in OSS):
cd build && npm run watch
node build/lib/policies
(ornode build/lib/policies win32
if this PR is merged).build/policies/win32/<some-locale>
for AllowedExtensions have a description of "No extensions are allowed".That string is coming from here, and what should be selected is apparently this string - the more friendly:
From the local group policy editor
related to #148942
The text was updated successfully, but these errors were encountered: