您的位置: 首页  >  技术问答  >  Visual Studio 2015 社区版在启动时崩溃

Visual Studio 2015 社区版在启动时崩溃

分类: 技术问答 • 2022-04-16 19:45:39
问题描述：

前几天我正在清理我的文档文件夹，一定是不小心删除了下面的这个特定文件.Visual Studio 启动后显示以下消息，然后单击确定后崩溃.

I was cleaning my documents folder the other day and must have accidentally deleted this particular file below. Visual Studio shows the message below after starting and then crashes after clicking ok.

我重新加载了社区版 3 次，安装了 Express 版(有效).重新加载 SQL 和 .NET 4.6.我确实有一个活动日志，但无法理解它想告诉我什么.

I've reloaded the commuunity edition three times, installed the Express edition (which works). Reloaded SQL and .NET 4.6. I do have an activity log, but can't understand what it's trying to tell me.

我下载了 Visual Studio 安装清理工具，它擦除了 160 个项目，重新安装，但仍然发生同样的问题.我在命令行尝试过 devenv.exe/resetsettings 选项.没有运气...

I downloaded the Visual Studio Install cleanup tool which wiped 160 items, reinstalled and still the same issue happens. I've tried devenv.exe /resetsettings option at command line. No Luck...

我发现活动日志包含多个错误，这些只是其中的几个.

I found the activity log to contain multiple errors these are just a few.

如果这只是缺少 vssettings 文件的问题，为什么新安装不创建一个?

If this is just a matter of a missing vssettings file why doesn't the new install create one?

更新 06-22:在 Anders 之后请提供一个新的 vssettings 文件.它启动到这一点，然后下降.

Update 06-22: After Anders kindly provide a new vssettings file. It booted to this point and then went down.

答

我花了三天时间耐心地尝试纠正 Visual Studio 无法工作的事实，因为我不小心删除了 vssettings.settings 文件.当我获得该文件的副本时，它会走得更远，但每次启动时都会崩溃.

I spent three days patiently trying to correct the fact Visual Studio wasn't working because I had deleted the vssettings.settings file accidentally. When I was given a copy of that file it went farther but it would crash each time it started.

所以我反复重新安装和删除 VS2015，每次都以不同的结果启动 VS2015...几乎就好像安装程序不知道如果系统上有残留的 VS 内容时如何进行全新安装.

So I repeatedly reinstalled and removed VS2015 with different results each time all failing to start VS2015... Almost as if the installer doesn't know how to do a completely fresh install if there is residual VS content on the system.

查看应用程序事件日志

然后我在应用程序事件查看器中找到了这个.找不到 Coloader80"

I then found this in the application event viewer. "Coloader80 could not be found"

我在网上找了一个帖子，有人发现你不仅要卸载VS2015；但需要删除 APPDATA 本地和远程以及程序文件中的所有 VS 文件夹.我什至删除了visualstudiocommon 文件夹.然后我通过添加删除 pgms 摆脱了所有重复"的 C++ 安装.

I scoured the internet and found a post that someone discovered that you have to not only uninstall VS2015; but need to remove all VS folders in APPDATA local and remote as well as in Program files. I even went as far are removing the visualstudiocommon folder. I then got rid of all "duplicate" C++ installs via add remove pgms.

解决方案

  1. 卸载机器上的所有 VS 版本.社区、快递等
  2. 通过添加/删除 pgms 删除所有 C++ 安装.
  3. 手动删除 Program Files Visual Studio 10、12 和 14.0 文件夹.
  4. 手动删除 Microsoft 文件夹中的所有 AppData 本地和远程文件夹，对 VisualStudio 有任何引用，注意这包括 VisualStudio.Common，它位于它自己的文件夹中
  5. 重新安装 VS2015
  6. 如果你这次有不同的错误，修复" VS2015 花了很长时间才完成.它经历了整个重新安装.
  7. 重新启动机器并启动 VS... MEF 组件已加载，显示主菜单需要很长时间.
  8. 等了大约 5 分钟或更长时间让一切安定下来
  9. 创建了一个新的 UWP 应用，其 NUGET 作业下载 DLLS 需要大约 5 分钟.
  1. Uninstall all VS versions on the machine. Community, Express etc.
  2. Get rid of all C++ installations via Add/remove pgms.
  3. Manually delete Program Files Visual Studio 10,12 and 14.0 folders.
  4. Manually delete all AppData local and remote folders in Microsoft folder that have any reference to VisualStudio, note this included VisualStudio.Common which was in it's own folder
  5. Reinstall VS2015
  6. If you have different error this time, "Repair" VS2015 which took an extraordinary long time to do. It goes through entire reinstall.
  7. Rebooted the machine and started up VS... MEF components loaded and it took a long time to show the main menu.
  8. Waited about 5 minutes or more to let everything settle down
  9. Created a new UWP app of which the NUGET job to download DLLS took about 5 minutes.
  1. 能够构建和运行新的 UWP！是的……终于……

我不知道整个情况的根本原因，但发现了两个截然不同的问题:1) coloader80.dll 丢失和 2) Visual Studio 会在尝试启动时崩溃.应用程序事件日志告诉我 .net 正在抛出未处理的异常.

I do not know the root cause of this whole situation, but found two distinct different issues 1) The coloader80.dll missing and 2) Visual Studio would just crash attempting to start. And the application event log was telling me .net was throwing unhandled exceptions.

Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Xml.XmlException
   at System.Xml.XmlTextReaderImpl.Throw(System.Exception)
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Xml.XmlTextReaderImpl.Read()
   at System.Xml.XmlTextReader.Read()
   at System.Configuration.XmlUtil..ctor(System.IO.Stream, System.String, Boolean, System.Configuration.ConfigurationSchemaErrors)
   at System.Configuration.BaseConfigurationRecord.InitConfigFromFile()

Exception Info: System.Configuration.ConfigurationErrorsException
   at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean)
   at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(System.Configuration.ConfigurationSchemaErrors)
   at System.Configuration.BaseConfigurationRecord.ThrowIfInitErrors()
   at System.Configuration.ClientConfigurationSystem.OnConfigRemoved(System.Object, System.Configuration.Internal.InternalConfigEventArgs)
   at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(System.Exception)

Exception Info: System.Configuration.ConfigurationErrorsException
   at Microsoft.VisualStudio.Services.VsTask.InternalGetResult(Boolean)
   at Microsoft.VisualStudio.Services.VsTask.GetResult()
   at Microsoft.VisualStudio.Shell.Connected.ConnectedUser.ConnectedUserManager+<ResolveFWLinkThroughVsWebProxy>d__79.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at Microsoft.VisualStudio.Shell.Connected.ConnectedUser.ConnectedUserManager+<ResolveFWLinkAsync>d__47.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at Microsoft.VisualStudio.Shell.Connected.ConnectedUser.BaseUserContext+<PrepareToConnectAndComputeCodeMarker>d__57.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at Microsoft.VisualStudio.Shell.Connected.ConnectedUser.BaseUserSession+<ConnectAsyncImpl>d__48.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at Microsoft.VisualStudio.Shell.Connected.ConnectedUser.BaseUserSession+<ConnectAsync>d__37.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at Microsoft.VisualStudio.Shell.Connected.ConnectedUser.BaseUserSession+<PollConnectAsync>d__49.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at Microsoft.VisualStudio.Shell.Connected.ConnectedUser.Poller+<PollAsync>d__13.MoveNext()
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__6_1(System.Object)
   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

我希望这对未来的人有所帮助...

I hope this helps someone in the future...

相关推荐