This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 3%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAT%3C/text%3E%3C/svg%3E)
i have visual studio 2022 community and i downloaded themes from the store, theyre not showing up. ive completely turned off my pc and it still isnt there, ive looked up solutions and all of the microsoft help solutions for other people were just marked as complete with no answer given.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 10%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAX%3C/text%3E%3C/svg%3E)
Hello, do you mean that you download the extension from the Visual Studio Marketplace? Can you tell us the full name of this theme extension?
i got the extensions from the in app marketplace, ive tried onedark, cyberpunk, visual studio theme pack, and visual studio color theme designer 2022, none of which have worked.
it seems to work after using admin privileges on "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Platform" even though that makes no sense. fixed.
for more clarification if anyone else has this problem, copy a file to the above location, it will say you need to use admin powers so click confirm. delete copied file after
Thanks for your sharing!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 51%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELU%3C/text%3E%3C/svg%3E)
It didnt work for me
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 72%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
The issue is somewhere in user profile and/or privileges of Visual Studio config folders.
Fix: run VS as admin and install some extensions from its manager, restart VS, confirm that it works. Wooosh, now it works outside admin as well.
In my case it was broken on freshly installed W11 with freshly installed VS2022C, but Windows went through obligatory debloating and user was recreated as local admin. I have only tried Theme extensions, but from what I know of vsix extensions after writing some all extensions should have the same stupid issue as it appears to be loading error caused by folder privileges.
On DeveloperVM it works perfectly fine on local user, so that alone should not be an issue.
It is not the first time such issue has occurred, with same run-once-as-admin fix. Years ago TFS needed same treatment on first run on every computer my team used. It was back on VS ~2010 on Win7/8, but extensions system has hardly changed since then.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 16%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EX%3C/text%3E%3C/svg%3E)
For me, the issue was that at some point VS had disabled all of my themes as extensions.
Run VS as admin, open the extension manager, and you should be able to see the themes installed, just disabled. You can then re-enable them and they will appear like they're supposed to.
You will need to restart VS for changes to apply.