Visual Studio 2022 Will Not Start

Miguel Grajeda 6

Visual Studio will not start. The issue began with a running version of Visual Studio Pro 2019. I couldn't get it to start, so I tried the following.

I cleared files in the following:
C:\Users\miguel.ELECTREX\AppData\Roaming\Microsoft\VisualStudio
C:\Users\miguel.ELECTREX\AppData\Local\Microsoft\VisualStudio
C:\Users\miguel.ELECTREX\AppData\Local\Temp

Uninstalled Visual Studio 2019 and Installed 2022, reboot many times.

Ran devenv /ResetSettings in the Developer command prompt.

Event Viewer:

Faulting application name: devenv.exe, version: 17.3.32901.215, time stamp: 0x63112d8a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x80131623
Fault offset: 0x00007ff8ebb2c767
Faulting process id: 0x4268
Faulting application start time: 0x01d8cd2bec962405
Faulting application path: C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe
Faulting module path: unknown
Report Id: f2e5d196-a762-4d3a-bdeb-eeb703db1124
Faulting package full name:
Faulting package-relative application ID:

Miguel Grajeda 6 Reputation points

2022-09-20T20:12:33.833+00:00

Other Error:
Cab Id: 0

Problem signature:
P1: devenv.exe
P2: 17.3.32901.215
P3: 63112d8a
P4: Microsoft.VisualStudio.Threading
P5: 17.3.44.61447
P6: dbf64a16
P7: 21c
P8: 18
P9: System.IO.FileNotFoundException
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B12.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2C8A.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2D65.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2DB3.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E41.tmp.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_devenv.exe_ebf85c283ce86e73623f6a1f91322a7466846a1_a7fccf21_9c2d693f-6f27-46e0-a2ca-84478e5dda63

Analysis symbol:
Rechecking for solution: 0
Report Id: f2e5d196-a762-4d3a-bdeb-eeb703db1124
Report Status: 268435456
Hashed bucket: b47b002a766cb069d9ee2ca9c6e0d9ab
Cab Guid: 0
Miguel Grajeda 6 Reputation points

2022-09-20T20:18:43.363+00:00

devenv /safemode also did not work.

Event Viewer:

Faulting application name: devenv.exe, version: 17.3.32901.215, time stamp: 0x63112d8a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x80131623
Fault offset: 0x00007ff8ebf17907
Faulting process id: 0x4d14
Faulting application start time: 0x01d8cd2dcd8b271f
Faulting application path: C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe
Faulting module path: unknown
Report Id: 43cc010a-e041-44eb-b470-67b4d778349b
Faulting package full name:
Faulting package-relative application ID:
Tianyu Sun-MSFT 27,356 Reputation points Microsoft Vendor

2022-10-05T08:45:10.347+00:00

Hi @Miguel Grajeda ,

Are you using any antivirus software maybe? If so, does disabling it temporarily and reboot your machine > restart VS work?

1 answer

Michael Taylor 48,576 Reputation points

2022-09-20T20:24:02.94+00:00

Seems like you have a corrupt install of something given that it is missing a file.

Run devenv.exe -log '<pathtotemp>\vslog.xml'. When VS crashes then go to the log file and take a look at it.

Given that it impacted both VS 2019 and VS 2022 my guess is it is a corrupt common component like .NET Framework, VC++ runtime or something. You could try repairing the VS install but if it is a common component it probably won't help. The next step would be to repair the .NET Framework and related components. But hopefully the log file will tell you what is wrong.

If the log doesn't provide any additional information then download and run procmon. Have it monitor the file calls. Then try to start VS. When it fails procmon should tell you what file(s) it was trying to open. Note that it is common for processes to attempt to open files that don't exist so you'll need to scan through the list looking for something that looks important.
Please sign in to rate this answer.
Miguel Grajeda 6 Reputation points

2022-09-20T20:43:03.207+00:00

I tried running the following commands but no log file generated.

I first tried the Temp no file generated, then I tried my Desktop and the Microsoft Visual Studio 2022 Splash Screen is stuck on my Desktop.

** Visual Studio 2022 Developer Command Prompt v17.3.4
** Copyright (c) 2022 Microsoft Corporation

C:\Program Files\Microsoft Visual Studio\2022\Professional>devenv.exe -log 'C:\Users\miguel.ELECTREX\AppData\Local\Temp\vslog.xml'

C:\Program Files\Microsoft Visual Studio\2022\Professional>devenv.exe -log 'C:\Users\miguel.FUNCO\Desktop\vslog.xml'

C:\Program Files\Microsoft Visual Studio\2022\Professional>

Miguel Grajeda 6 Reputation points

2022-09-20T20:53:41.403+00:00

I also ran the tool Microsoft .NET Framework Repair Tool and it generated a lot of errors. Let me know where I can send these?

Michael Taylor 48,576 Reputation points

2022-09-20T20:57:32.133+00:00

If the repair tool fixed issues then you should try running VS again. You can post the errors here (or a subset).

Did you try running 'procmon' to see what file(s) it cannot find?

Miguel Grajeda 6 Reputation points

2022-09-20T21:19:09.833+00:00

I did run the procmon I'm really not sure which results I should be looking for since their is many for devenv.exe

I'm seeing some of these:
FAST IO DISALLOWED
C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\VERSION.dll

Also
FAST IO DISALLOWED
C:\Windows\System32\version.dll

And
FILE LOCKED WITH ONLY READERS
C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\msvcp140.dll

To many notifications to count

I have a FixDotNet20220920204832572.cab file but I can't seem to load it here.. It has 404 files.

Michael Taylor 48,576 Reputation points

2022-09-20T21:21:12.1+00:00

Those errors are fine. What you're looking for is one that is a FILE_NOT_FOUND (I think). That indicates that someone tried to open a file and it couldn't be located. This is what the original error you posted indicated I believe.

Miguel Grajeda 6 Reputation points

2022-09-20T21:38:10.057+00:00

I used my procmon filtering and did not see any FILE_NOT_FOUND, but I did get some

Result: NO MORE FILES
Path: C:\Windows\Microsoft.NET\Framework64

Result: NO MORE FILES
Path: C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.Vd43b287e#

Result: NO SUCH FILE
Path: C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.admin.pkgdef

Michael Taylor 48,576 Reputation points

2022-09-20T21:45:21.367+00:00

No more files is fine. That is triggered when you enumerate the files in a directory. devenv.admin.pkgdef is a package definition for an extension but I've never heard of it before. It should be harmless though.

Did you try running VS in safemode using /safemode?

Miguel Grajeda 6 Reputation points

2022-09-21T14:22:14.68+00:00

I ran it in safemode and the Microsoft Visual Studio 2022 Splash Screen
popped up for a few seconds and closed. It's also not running in task manager.

** Visual Studio 2022 Developer Command Prompt v17.3.4
** Copyright (c) 2022 Microsoft Corporation

C:\Program Files\Microsoft Visual Studio\2022\Professional>devenv.exe /safemode

C:\Program Files\Microsoft Visual Studio\2022\Professional>

Uninstalled:

Microsoft .NET Core Runtime - 2.1.30 (x64)

Microsoft .NET SDK 3.1.418 (x64)

Microsoft .NET SDK 5.0.103 (x64)

Microsoft .NET SDK 5.0.213 (x64)

Microsoft .NET SDK 5.0.407 (x64)

Microsoft .NET SDK 6.0.202 (x64)

Microsoft .NET SDK 6.0.401 (x64) from Visual

Microsoft Visual Studio Installer

I cleared files again:
C:\Users\miguel.ELECTREX\AppData\Roaming\Microsoft\VisualStudio
C:\Users\miguel.ELECTREX\AppData\Local\Microsoft\VisualStudio
C:\Users\miguel.ELECTREX\AppData\Local\Temp

Reboot.

Ran Windows Updates and Noticed:

2022-09 .NET core 3.1.29 Security Update for x64 CLient (KB890830)

2022-09 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for
Windows 10 Version 21H2 for X64 (KB5017500)

2022-05 .NET 5.0.17 Security Update for X64 Client (KB5014329)

Re installing Visual Studio
The Visual Studio Spash Screen pops up for a few seconds and closes.

Michael Taylor 48,576 Reputation points

2022-09-21T14:36:04.877+00:00

You shouldn't be wiping the AppData\Local\Temp directory. That is where all the logs go that would help diagnose install/uninstall problems. Without those logs there is no way to understand if something might have failed during install.

At this point I don't know how to proceed. Have you ever been able to get VS 2019/2022 to run? If so then something changed to break it but I have no idea what. If it has never run then I question your system configuration.

Can you try creating a new user profile, logging out of your existing account and into the new one. Then try to start VS again. If it fails then it is something at the system level. Unfortunately without the logs it could take a long time to figure out.

Your next step is to Report a Problem to MS and have a support engineer help you out. I've never seen VS fail to run after a reinstall and I've installed/reinstalled it hundreds of times. My gut instinct is something in your system is getting in the way like anti-virus or something. Or you (or an uninstaller) cleaned up something it shouldn't have and your system is in need of a repair.
Sign in to comment