Visual studio 2019 community edition crashing

Question

Hello Devs, Arranging the tabs in the visual studio 2019 community edition causing crashing. Event viewer shows below errors. Hope this will be addressed in the future releases. Faulting application name: devenv.exe, version: 16.8.30804.86, time stamp: 0x5fcaa7fa Faulting module name: PresentationCore.ni.dll, version: 4.8.4320.0, time stamp: 0x5fc81198 Exception code: 0xc0000005 Fault offset: 0x0076c044 Faulting process id: 0x3ad8 Faulting application start time: 0x01d70ddd4cedbb91 Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\devenv.exe Faulting module path: C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\PresentationCore\083c71054d41aa078ff981247f747677\PresentationCore.ni.dll Report Id: 754fce1f-0032-42ab-bf5c-977980457349 Faulting package full name: Faulting package-relative application ID: --------------------------------------------------------------------------------------------------------------------------- Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied. . This is often caused by incorrect security settings in either the writer or requestor process. Operation: Gathering Writer Data Context: Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Name: System Writer Writer Instance ID: {a5a9bcc8-c15e-4b6b-aa2d-1691d4cf3ae0}

Answer 1

Two suggestions.

Do a repair on Visual Studio 2019 and it could not hurt to update to latest version if you are not already on it.

If the repair / install newer version does not work open the directory with your solution in it and delete the hidden .vs folder (visual studio probably needs to be closed to do it). It will forget what files you had open when you open solution and you will have to set startup projects again.

Answer 2

See https://www.bleepingcomputer.com/news/microsoft/recent-windows-10-updates-cause-visual-studio-wpf-app-crashes/

Answer 3

Hi SrikanthPolineni,

You can have a try following workarounds:

• Clear the cache in C:\Users\userName\AppData\Local\Microsoft\VisualStudio\16.0_{versionNumber}\ComponentModelCache
• Run VS in safe mode

Best Regards,
Dylan

---

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our **documentation to enable e-mail notifications if you want to receive the related email notification for this thread.**