The process of installing, configuring, and customizing Visual Studio to support development workflows across languages, platforms, and workloads.
Generate a Visual Studio startup log first, then remove the per-user identity cache only if the log or dialog reports access denied under .IdentityService; a normal reinstall does not necessarily address that user-specific state.
1. Capture the actual startup failure
Open Command Prompt and run:
cd /d "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE"
devenv.exe /log "%USERPROFILE%\Desktop\VS-ActivityLog.xml"
The /Log switch records Visual Studio startup activity and supports a custom output path.^1^
After Visual Studio fails:
- Open
VS-ActivityLog.xmlfrom the desktop. - Search for:
-
ServiceHub.IdentityHost -
.IdentityService -
Access denied -
Error
-
- Also open Event Viewer → Windows Logs → Application and check the matching
ServiceHub.IdentityHost.exefailure for the exception and faulting module.
ServiceHub.IdentityHost.exe is one of Visual Studio’s out-of-process components. If it terminates unexpectedly, Visual Studio functionality or stability can be affected.^2^
2. If the error names .IdentityService and says access is denied
Close Visual Studio and Visual Studio Installer. In File Explorer, enter:
%LOCALAPPDATA%
Before deleting anything:
- Right-click
.IdentityService→ Properties → Security. - Record or screenshot the permissions in case the issue must be reported.
- Delete the particular file or the
.IdentityServicedirectory named by the error. - Start Visual Studio again.
Microsoft documents deleting the named identity file or directory specifically for first-launch errors such as:
Access to the path 'C:\Users\<UserName>\AppData\Local\.IdentityService\...' is denied.
Do not apply this deletion merely because ServiceHub.IdentityHost.exe appears in the message; use it when the error identifies .IdentityService or its permissions.
3. Repair the installation
Since uninstalling and reinstalling did not help, use the Installer’s repair operation rather than repeating the same reinstall:
- Open Start → Visual Studio Installer.
- Locate Visual Studio Community 2022 under Installed.
- Select More → Repair.
- Restart Windows after repair, then test Visual Studio.
Repair reacquires required installation files, but it resets Visual Studio settings and some per-user customizations.^4^
4. If killing the updater left the Installer itself damaged
For an update-related Installer failure:
- Close Visual Studio Installer.
- Delete:
C:\Program Files (x86)\Microsoft Visual Studio\Installer
- Run a newly downloaded Visual Studio 2022 Community bootstrapper.
- Let it reinstall the Installer metadata, then run Repair or reinstall Community.
Microsoft documents this Installer-folder reset for update failures.^5^
5. Last resort: clean version 17 installation state
Only use this after repair and the Installer reset fail. It removes Visual Studio installation records and files and can affect other Visual Studio installations.
Close the Installer, open Command Prompt as administrator, and run:
"C:\Program Files (x86)\Microsoft Visual Studio\Installer\InstallCleanup.exe" -i 17
Then reinstall Visual Studio 2022 Community. The -i 17 option removes version 17 product information while retaining the intended path of reinstalling that Visual Studio version.^6^
If the failure remains, collect setup and ServiceHub logs before reporting it:
- Setup collection output:
%TEMP%\vslogs.zip - ServiceHub logs:
%TEMP%\servicehub\logs - Visual Studio Installer → Report a problem
For a reproducible out-of-process failure, Microsoft recommends collecting ServiceHub logs and attaching vslogs.zip to the report.^7^
References
- /Log (devenv.exe)
- Visual Studio unrecoverable process error
- Sign in to Visual Studio with accounts that require multifactor authentication (MFA)
- Repair your Visual Studio installation | Microsoft Learn
- Troubleshoot Visual Studio installation and upgrade issues
- Uninstall or remove Visual Studio
- Increase the chances of a performance issue being fixed