none
Visual Studio Installer crashing RRS feed

  • Question

  • I'm suddenly having weird issues with the visual studio installer. (including VS 2019)

    I have tried completely removing it many times including system checks (sfc & dism), reinstalling .NET framework in the windows features and checking for windows updates and driver updates.

    These errors mainly get logged in temp after the installer extracts itself, but doesn't start:

    2019-09-01T04:47:30 : Verbose : Visual Studio Installer (2.2.3085.814 : release) ["C:\\Program Files (x86)\\Microsoft Visual Studio\\Installer\\vs_installershell.exe","/finalizeInstall","install","--in","C:\\ProgramData\\Microsoft\\VisualStudio\\Packages\\_bootstrapper\\vs_setup_bootstrapper_201909010447165331.json","--locale","de-DE","--activityId","23a8ff99-8876-4c7a-8e52-9023eb54c854","--pipe","c7695306-ca7d-4eaa-9158-9ab30e870932"]
    2019-09-01T04:47:30 : Verbose : Received the application ready notification
    2019-09-01T04:47:30 : Verbose : ProgressBarService listening to ipc channel: progress-bar
    2019-09-01T04:47:30 : Verbose : LoggerIpcRpcService listening to ipc channel: LoggerService
    2019-09-01T04:47:30 : Verbose : LoggerIpcRpcService listening to ipc channel: LoggerService
    2019-09-01T04:47:30 : Verbose : Telemetry Session ID: 50c7b8d7-5f71-45f4-a66a-1a8b57cb86fe
    2019-09-01T04:47:30 : Verbose : Starting ServiceHub Remote Settings client.
    2019-09-01T04:47:30 : Verbose : Creating VS Telemetry Survey
    2019-09-01T04:47:30 : Verbose : Creating commonError Service
    2019-09-01T04:47:30 : Verbose : starting rpc process for common error
    2019-09-01T04:47:30 : Verbose : RPC Factory: Get common error config provider
    2019-09-01T04:47:30 : Verbose : Creating helpLink Service
    2019-09-01T04:47:30 : Verbose : starting rpc process for help link
    2019-09-01T04:47:30 : Verbose : FeaturesIpcRpcService listening to ipc channel: FeaturesProxy
    2019-09-01T04:47:30 : Verbose : FeaturesIpcRpcService listening to ipc channel: FeaturesProxy
    2019-09-01T04:47:30 : Verbose : Starting the installer service.
    2019-09-01T04:47:30 : Verbose : Installation finalized successfully.
    2019-09-01T04:47:31 : Verbose : FeedbackIpcRpcService listening to ipc channel: FeedbackProxy
    2019-09-01T04:47:31 : Verbose : Window ready
    2019-09-01T04:47:31 : Verbose : Calling RemoteSettingsProviderService.Initialize(initializer) initializer: {"ClientName":"vs-xsetup","ClientVersion":"2.2.3085.814","RemoteSettingsFileName":"RemoteSettings_Installer.json","SerializedTelemetrySession":"{\"IsOptedIn\":true,\"Id\":\"50c7b8d7-5f71-45f4-a66a-1a8b57cb86fe\",\"HostName\":\"Dev14\",\"AppInsightsInstrumentationKey\":\"f144292e-e3b2-4011-ac90-20e5c03fbce5\",\"AsimovInstrumentationKey\":\"aif-312cbd79-9dbb-4c48-a7da-3cc2a931cb70\",\"ProcessStartTime\":637029028508540000}","ChannelOrProductId":"VS Installer","AppIdGuid":"42123B45-5471-4B16-81E7-5404CD93BCF1","ClientLocale":"de-DE","Flights":[]}}
    2019-09-01T04:47:31 : Verbose : ServiceHub Remote Settings client started.
    2019-09-01T04:47:31 : Verbose : RPC Factory: Get help link provider
    2019-09-01T04:47:31 : Verbose : Getting the survey rules
    2019-09-01T04:47:31 : Verbose : Calling RemoteSettingsProviderService.GetActionsAsync(actionPath), actionPath: vs\installer\surveyactions
    2019-09-01T04:47:31 : Verbose : Calling RemoteSettingsProviderService.GetBooleanValue(collectionPath, key, defaultValue) collectionPath: Installer\Features\, key: WelcomePane, defaultValue: false
    2019-09-01T04:47:31 : Verbose : Calling RemoteSettingsProviderService.GetBooleanValue(collectionPath, key, defaultValue) collectionPath: Installer\Features\, key: DownloadThenUpdate, defaultValue: false
    2019-09-01T04:47:31 : Verbose : Calling RemoteSettingsProviderService.GetBooleanValue(collectionPath, key, defaultValue) collectionPath: Installer\Features\, key: ProblemsDlgButtons, defaultValue: false
    2019-09-01T04:47:31 : Verbose : Calling RemoteSettingsProviderService.GetBooleanValue(collectionPath, key, defaultValue) collectionPath: Installer\Features\, key: CommonError, defaultValue: false
    2019-09-01T04:47:31 : Verbose : Calling RemoteSettingsProviderService.GetBooleanValue(collectionPath, key, defaultValue) collectionPath: Installer\Features\, key: ProblemsDlgRetry, defaultValue: false
    2019-09-01T04:47:31 : Verbose : Calling RemoteSettingsProviderService.GetBooleanValue(collectionPath, key, defaultValue) collectionPath: Installer\Features\, key: InstallationOptionsPageKS, defaultValue: false
    2019-09-01T04:47:31 : Verbose : Calling RemoteSettingsProviderService.GetBooleanValue(collectionPath, key, defaultValue) collectionPath: Installer\Features\, key: ShowBitrate, defaultValue: false
    2019-09-01T04:47:31 : Verbose : Calling RemoteSettingsProviderService.GetBooleanValue(collectionPath, key, defaultValue) collectionPath: Installer\Features\, key: RecommendSel, defaultValue: false
    2019-09-01T04:47:31 : Verbose : Calling RemoteSettingsProviderService.GetBooleanValue(collectionPath, key, defaultValue) collectionPath: Installer\Features\, key: Surveys, defaultValue: false
    2019-09-01T04:47:31 : Verbose : Calling SetupEngine.Installer.Initialize. [locale: de-DE]
    2019-09-01T04:47:31 : Verbose : Connected to Hub Controller's client watch 'net.pipe://8AA6146E7BB317C941490D6977B6BBB1'
    2019-09-01T04:47:33 : Verbose : [ServiceHubRemoteSettingsClient]: Rpc connection was closed.
    2019-09-01T04:47:33 : Verbose : [InstallerImpl]: Rpc connection was closed.
    2019-09-01T04:47:33 : Error : SetupEngine.Installer.Initialize failed. [locale: de-DE, error: Cannot execute 'Initialize'. The underlying stream has closed. at Error: Cannot execute 'Initialize'. The underlying stream has closed.
        at Function.JsonRpcConnection.createStreamClosedError (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\microsoft-servicehub\jsonRpc.js:127:22)
        at JsonRpcConnection.cancelPendingRequests (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\microsoft-servicehub\jsonRpc.js:101:69)
        at JsonRpcConnection.onConnectionClosed (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\microsoft-servicehub\jsonRpc.js:123:14)
        at CallbackList.invoke (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\events.js:103:39)
        at Emitter.fire (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\events.js:167:36)
        at closeHandler (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\main.js:70:26)
        at CallbackList.invoke (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\events.js:103:39)
        at Emitter.fire (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\events.js:167:36)
        at StreamMessageWriter.AbstractMessageWriter.fireClose (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\messageWriter.js:38:27)
        at Socket.<anonymous> (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\messageWriter.js:61:62)
        at emitOne (events.js:121:20)
        at Socket.emit (events.js:211:7)
        at Pipe._handle.close [as _onclose] (net.js:554:12)
    From previous event:
        at Function.defer (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:582:19)
        at JsonRpcConnection.sendRequest (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\microsoft-servicehub\jsonRpc.js:45:28)
        at InstallerImpl.ServiceHubClient.invoke (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\main\StubMain.js:4:136597)
        at C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\main\StubMain.js:4:758593
        at new Promise (<anonymous>)
        at InstallerImpl.initialize (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\main\StubMain.js:4:758501)
        at C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\main\StubMain.js:4:772968
        at _fulfilled (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:834:54)
        at self.promiseDispatch.done (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:863:30)
        at Promise.promise.promiseDispatch (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:796:13)
        at C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:604:44
        at runSingle (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:137:13)
        at flush (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:125:13)
        at _combinedTickCallback (internal/process/next_tick.js:131:7)
        at process._tickCallback (internal/process/next_tick.js:180:9)]
    2019-09-01T04:47:33 : Error : Failed to start the installer service. error: Cannot execute 'Initialize'. The underlying stream has closed. at Error: Cannot execute 'Initialize'. The underlying stream has closed.
        at Function.JsonRpcConnection.createStreamClosedError (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\microsoft-servicehub\jsonRpc.js:127:22)
        at JsonRpcConnection.cancelPendingRequests (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\microsoft-servicehub\jsonRpc.js:101:69)
        at JsonRpcConnection.onConnectionClosed (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\microsoft-servicehub\jsonRpc.js:123:14)
        at CallbackList.invoke (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\events.js:103:39)
        at Emitter.fire (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\events.js:167:36)
        at closeHandler (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\main.js:70:26)
        at CallbackList.invoke (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\events.js:103:39)
        at Emitter.fire (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\events.js:167:36)
        at StreamMessageWriter.AbstractMessageWriter.fireClose (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\messageWriter.js:38:27)
        at Socket.<anonymous> (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\messageWriter.js:61:62)
        at emitOne (events.js:121:20)
        at Socket.emit (events.js:211:7)
        at Pipe._handle.close [as _onclose] (net.js:554:12)
    From previous event:
        at Function.defer (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:582:19)
        at JsonRpcConnection.sendRequest (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\microsoft-servicehub\jsonRpc.js:45:28)
        at InstallerImpl.ServiceHubClient.invoke (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\main\StubMain.js:4:136597)
        at C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\main\StubMain.js:4:758593
        at new Promise (<anonymous>)
        at InstallerImpl.initialize (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\main\StubMain.js:4:758501)
        at C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\main\StubMain.js:4:772968
        at _fulfilled (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:834:54)
        at self.promiseDispatch.done (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:863:30)
        at Promise.promise.promiseDispatch (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:796:13)
        at C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:604:44
        at runSingle (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:137:13)
        at flush (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:125:13)
        at _combinedTickCallback (internal/process/next_tick.js:131:7)
        at process._tickCallback (internal/process/next_tick.js:180:9)
    2019-09-01T04:47:33 : Error : Failed to initialize the app services. [error: Cannot execute 'Initialize'. The underlying stream has closed. at Error: Cannot execute 'Initialize'. The underlying stream has closed.
        at Function.JsonRpcConnection.createStreamClosedError (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\microsoft-servicehub\jsonRpc.js:127:22)
        at JsonRpcConnection.cancelPendingRequests (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\microsoft-servicehub\jsonRpc.js:101:69)
        at JsonRpcConnection.onConnectionClosed (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\microsoft-servicehub\jsonRpc.js:123:14)
        at CallbackList.invoke (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\events.js:103:39)
        at Emitter.fire (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\events.js:167:36)
        at closeHandler (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\main.js:70:26)
        at CallbackList.invoke (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\events.js:103:39)
        at Emitter.fire (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\events.js:167:36)
        at StreamMessageWriter.AbstractMessageWriter.fireClose (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\messageWriter.js:38:27)
        at Socket.<anonymous> (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\vscode-jsonrpc\lib\messageWriter.js:61:62)
        at emitOne (events.js:121:20)
        at Socket.emit (events.js:211:7)
        at Pipe._handle.close [as _onclose] (net.js:554:12)
    From previous event:
        at Function.defer (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:582:19)
        at JsonRpcConnection.sendRequest (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\microsoft-servicehub\jsonRpc.js:45:28)
        at InstallerImpl.ServiceHubClient.invoke (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\main\StubMain.js:4:136597)
        at C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\main\StubMain.js:4:758593
        at new Promise (<anonymous>)
        at InstallerImpl.initialize (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\main\StubMain.js:4:758501)
        at C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\main\StubMain.js:4:772968
        at _fulfilled (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:834:54)
        at self.promiseDispatch.done (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:863:30)
        at Promise.promise.promiseDispatch (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:796:13)
        at C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:604:44
        at runSingle (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:137:13)
        at flush (C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\node_modules\q\q.js:125:13)
        at _combinedTickCallback (internal/process/next_tick.js:131:7)
        at process._tickCallback (internal/process/next_tick.js:180:9)]

    Taking a look in the event viewer gives me a bunch of .NET runtime & Application errors for Microsoft.ServiceHub.Controller.exe with either an System.Runtime.InteropServices.SEHException or System.AccessViolationException. I already checked my memory for issues and ran chkdsk, but no errors.

    It first occured when opening Visual Studio Installer for the first time after a brief time to check for any updates and itself behaving weird. In some occasions it didn't start, in some it threw me a bunch of errors.. I never had these problems ever before.

    Since I had Visual Studio installed, I tried running that, but it behaved the same and often crashed upon starting.


    Thanks in advance.

    Further logs:

    Windows cannot access the "" file for one of the following reasons: There is a problem with the network connection, the disk that contains the saved file or storage drivers installed on your computer, or the disk is missing. The Microsoft ServiceHub Controller program was closed by Windows because of this error.
    
    Program: Microsoft.ServiceHub.Controller
    File: 
    
    The error value is listed in the "Additional Files" section.
    User action
    Open the file again. This situation may be a temporary problem that will be fixed automatically when the program is run again.
    2. if you still cannot access the file, and
        - If the server is on the network, the network administrator should ensure that there is no network problem and that a connection to the server can be established.
        - If the server is on a removable disk, such as a floppy disk or CD, check that the disk is properly inserted in the computer.
    Check and repair the file system by running CHKDSK. To do this, click Run in the Start menu, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
    Restore the file from a backup if the problem persists.
    Check to see if other files can be opened on the same disk. If this is not possible, the disk may be damaged.  Contact the administrator or the manufacturer of the computer hardware for further assistance if it is a hard disk.
    
    Additional Data
    Error value: 74523D50
    Data carrier type: 0
    
    Translated with www.DeepL.com/Translator
    
    
    -- ORIGINAL (German) --
    
    Aus einem der folgenden Gründe kann Windows nicht auf die Datei "" zugreifen: Es besteht ein Problem mit der Netzwerkverbindung, dem Datenträger mit der gespeicherten Datei bzw. den auf dem Computer installierten Speichertreibern, oder der Datenträger fehlt. Das Programm Microsoft.ServiceHub.Controller wurde von Windows wegen dieses Fehlers geschlossen.
    
    Programm: Microsoft.ServiceHub.Controller
    Datei: 
    
    Der Fehlerwert ist im Abschnitt "Zusätzliche Dateien" aufgelistet.
    User action
    1. Öffnen Sie die Datei erneut. Diese Situation ist eventuell ein temporäres Problem, das selbstständig behoben wird, wenn das Programm erneut ausgeführt wird.
    2. Wenn Sie weiterhin nicht auf die Datei zugreifen können und
    	- diese sich im Netzwerk befindet,  dann sollte der Netzwerkadministrator sicherstellen, dass kein Netzwerkproblem besteht und dass eine Verbindung mit dem Server hergestellt werden kann.
    	- diese sich auf einem Wechseldatenträger, wie z. B. einer Diskette oder einer CD, befindet, überprüfen Sie, ob der Datenträger richtig in den Computer eingelegt ist.
    3. Überprüfen und reparieren Sie das Dateisystem, indem Sie CHKDSK ausführen. Klicken Sie dazu im Startmenü auf "Ausführen", geben Sie CMD ein, und klicken Sie auf "OK". Geben Sie an der Eingabeaufforderung CHKDSK /F ein, und drücken Sie die EINGABETASTE.
    4. Stellen Sie die Datei von einer Sicherungskopie wieder her, wenn das Problem weiterhin besteht.
    5. Überprüfen Sie, ob andere Dateien auf demselben Datenträger geöffnet werden können. Falls dies nicht möglich ist, ist der Datenträger eventuell beschädigt.  Wenden Sie sich an den Administrator oder den Hersteller der Computerhardware, um weitere Unterstützung zu erhalten, wenn es sich um eine Festplatte handelt.
    
    Zusätzliche Daten
    Fehlerwert: 74523D50
    Datenträgertyp: 0
    09/01/2019 20:29:41 : Information : Log configuration: $SERVICEHUBTRACELEVEL=""
    09/01/2019 20:29:41 : Error : Hub controller process exited with exit code 3221225477.
    09/01/2019 20:29:43 : Error : Hub controller process exited with exit code 3221225477.
    09/01/2019 20:29:44 : Error : HubController PID 4852 stderr: 
    Unbehandelte Ausnahme: 
    09/01/2019 20:29:44 : Error : HubController PID 4852 stderr: System.AccessViolationException: Es wurde versucht, im gesch�tzten Speicher zu lesen oder zu schreiben. Dies ist h�ufig ein Hinweis darauf, dass anderer Speicher besch�digt ist.
       bei Newtonsoft.Json.Linq.JContainer.ValidateToken(JToken o, JToken existing)
       bei Newtonsoft.Json.Linq.JContainer.InsertItem(Int32 index, JToken item, Boolean skipParentCheck)
       bei Newtonsoft.Json.Linq.JContainer.AddInternal(Int32 index, Object content, Boolean skipParentCheck)
       bei Newtonsoft.Json.Linq.JTokenWriter.AddValue(JValue value, JsonToken token)
       bei Newtonsoft.Json.Linq.JTokenWriter.WriteValue(String value)
       bei Newtonsoft.Json.JsonWriter.WriteToken(JsonToken token, Object value)
       bei Newtonsoft.Json.JsonWriter.WriteToken(JsonReader reader, Boolean writeChildren, Boolean writeDateConstructorAsDate, Boolean writeComments)
       bei Newtonsoft.Json.JsonWriter.WriteToken(JsonReader reader, Boolean writeChildren)
       bei Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateJToken(JsonReader reader, JsonContract contract)
       bei Newtonsoft.Json.Serialization.JsonSerializerInternalReader.SetPropertyValue(JsonProperty property, JsonConverter propertyConverter, JsonContainerContract containerContract, JsonProperty containerProperty, JsonReader reader, Object target)
       bei Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject(Object newObject, JsonReader reader, JsonObjectContract contract, JsonProperty member, String id)
       bei Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)
       bei Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
       bei Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
       bei Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
       bei Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
       bei StreamJsonRpc.JsonRpc.<HandleRpcAsync>d__98.MoveNext()
       bei System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
       bei StreamJsonRpc.JsonRpc.HandleRpcAsync(String json)
       bei StreamJsonRpc.JsonRpc.<ReadAndHandleRequestsAsync>d__97.MoveNext()
       bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Runtime.CompilerServices.AsyncMethodBuilderCore.MoveNextRunner.Run()
       bei System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(Action action, Boolean allowInlining, Task& currentTask)
       bei System.Threading.Tasks.Task.FinishContinuations()
       bei System.Threading.Tasks.Task`1.TrySetResult(TResult result)
       bei System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.SetResult(TResult result)
       bei StreamJsonRpc.DelimitedMessageHandler.<ReadAsync>d__22.MoveNext()
       bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Runtime.CompilerServices.AsyncMethodBuilderCore.MoveNextRunner.Run()
       bei System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(Action action, Boolean allowInlining, Task& currentTask)
       bei System.Threading.Tasks.Task.FinishContinuations()
       bei System.Threading.Tasks.Task`1.TrySetResult(TResult result)
       bei System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.SetResult(TResult result)
       bei StreamJsonRpc.HeaderDelimitedMessageHandler.<ReadCoreAsync>d__20.MoveNext()
       bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Runtime.CompilerServices.AsyncMethodBuilderCore.MoveNextRunner.Run()
       bei System.Threading.ThreadPoolWorkQueue.Dispatch()
    
    09/01/2019 20:29:45 : Error : Hub controller process exited with exit code 3221225477.
    09/01/2019 20:29:47 : Error : Hub controller process exited with exit code 3221225477.
    09/01/2019 20:29:41 : Information : Log configuration: $SERVICEHUBTRACELEVEL=""
    09/01/2019 20:29:41 : Error : Hub controller process exited with exit code 3221225477.
    09/01/2019 20:29:43 : Error : HubController PID 3828 stderr: 
    Unbehandelte Ausnahme: 
    09/01/2019 20:29:43 : Error : HubController PID 3828 stderr: System.Runtime.InteropServices.SEHException: Eine externe Komponente hat eine Ausnahme ausgel�st.
       bei System.Collections.Immutable.SecurePooledObject`1..ctor(T newValue)
       bei System.Collections.Immutable.SecureObjectPool`2.PrepNew(TCaller caller, T newValue)
       bei System.Collections.Immutable.ImmutableList`1.Enumerator..ctor(Node root, Builder builder, Int32 startIndex, Int32 count, Boolean reversed)
       bei System.Collections.Immutable.ImmutableList`1.Node.IndexOf(T item, Int32 index, Int32 count, IEqualityComparer`1 equalityComparer)
       bei System.Collections.Immutable.ImmutableList.IndexOf[T](IImmutableList`1 list, T item, IEqualityComparer`1 equalityComparer)
       bei Microsoft.ServiceHub.Controller.LocationService.IsExternalClient(ClientInfo clientInfo)
       bei Microsoft.ServiceHub.Controller.LocationService.<LocateAsync>d__32.MoveNext()
       bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Runtime.CompilerServices.AsyncMethodBuilderCore.MoveNextRunner.Run()
       bei System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(Action action, Boolean allowInlining, Task& currentTask)
       bei System.Threading.Tasks.Task.FinishContinuations()
       bei System.Threading.Tasks.Task`1.TrySetResult(TResult result)
       bei System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.SetResult(TResult result)
       bei Microsoft.ServiceHub.Controller.LocationService.<GetHostedServiceLocationAsync>d__63.MoveNext()
       bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Runtime.CompilerServices.AsyncMethodBuilderCore.MoveNextRunner.Run()
       bei System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(Action action, Boolean allowInlining, Task& currentTask)
       bei System.Threading.Tasks.Task.FinishContinuations()
       bei System.Threading.Tasks.Task`1.TrySetResult(TResult result)
       bei System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.SetResult(TResult result)
       bei Microsoft.ServiceHub.Controller.LocationService.<StartServiceAsync>d__47.MoveNext()
       bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Runtime.CompilerServices.AsyncMethodBuilderCore.MoveNextRunner.Run()
       bei System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(Action action, Boolean allowInlining, Task& currentTask)
       bei System.Threading.Tasks.Task.FinishContinuations()
       bei System.Threading.Tasks.Task`1.TrySetResult(TResult result)
       bei System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.SetResult(TResult result)
       bei StreamJsonRpc.JsonRpc.<InvokeCoreAsync>d__88`1.MoveNext()
       bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Runtime.CompilerServices.AsyncMethodBuilderCore.MoveNextRunner.Run()
       bei System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(Action action, Boolean allowInlining, Task& currentTask)
       bei System.Threading.Tasks.Task.FinishContinuations()
       bei System.Threading.Tasks.Task`1.TrySetResult(TResult result)
       bei System.Threading.Tasks.TaskCompletionSource`1.TrySetResult(TResult result)
       bei StreamJsonRpc.JsonRpc.<>c__DisplayClass88_1`1.<InvokeCoreAsync>b__0(JsonRpcMessage response)
       bei StreamJsonRpc.JsonRpc.<HandleRpcAsync>d__98.MoveNext()
       bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Runtime.CompilerServices.AsyncMethodBuilderCore.MoveNextRunner.Run()
       bei System.Threading.Tasks.Task.Execute()
       bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot)
       bei System.Threading.Tasks.Task.ExecuteEntry(Boolean bPreventDoubleExecution)
       bei System.Threading.ThreadPoolWorkQueue.Dispatch()
    
    09/01/2019 20:29:44 : Error : Hub controller process exited with exit code 3221225477.
    09/01/2019 20:29:45 : Error : Hub controller process exited with exit code 3221225477.
    09/01/2019 20:29:49 : Error : Hub controller process exited with exit code 3221225477.
    Sunday, September 1, 2019 7:00 PM

Answers

  • This problem got solved. My CPU had a problem, causing to the error above. Sent it back, got a new one and it works fine now.

    • Marked as answer by Aarivex Saturday, October 19, 2019 8:36 PM
    Saturday, October 19, 2019 8:36 PM

All replies

  • Hi Aarivex,

    Welcome to the MSDN forum.

    According to your description, I suggest you take the following steps to see if it helps you:

    • Open Visual Studio Command Prompt, run it with Administrator privilege: right-click the program -> Run as administrator
    • Run devenv /Safemode to see if you can apply it correctly. This can eliminate the possibility that third party Add-ins or packages are causing problems.
    • Run devenv /resetskippkgs, it will clear all SkipLoading tags that have been added to VSPackages by users who want to avoid loading problem VSPackages.
    • Run devenv /Resetsettings to eliminate the cause of corrupted settings.

    If it still can't help you, please collect more detail information to troubleshoot this issue.

    • Run devenv /log <log path> in Command Prompt, the log files will be generated in the <log path>, we can enable Visual Studio logging to log all activity to the specified log path. Then check and analyze the log file to see if there are anything incorrect.

    Best Regards,

    Sara


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    • Proposed as answer by c_xyTopa Thursday, December 5, 2019 9:21 AM
    Monday, September 2, 2019 8:04 AM
    Moderator
  • Thanks for the answer.

    I removed VS2019 throughout the plenty reinstallations completely, so I think there is no devenv.


    • Edited by Aarivex Monday, September 2, 2019 5:36 PM
    Monday, September 2, 2019 5:36 PM
  • Hi Aarivex,

    Thanks for your update.

    How did you remove the VS 2019?

    We can clean up the installed VS like the following and re-install it:

    • See if you have this file on your machine: "%programfiles(x86)%\Microsoft Visual Studio\Installer\resources\app\layout\InstallCleanup.exe"
    • If so, please launch it from an admin command prompt with a -full param:

    InstallCleanup.exe -full

    • If not, please manually delete the "%programfiles(x86)%\Microsoft Visual Studio\Installer” folder
    • Relaunch the newly downloaded vs_enterprise.exe (or vs_professional.exe or vs_community.exe…)
    • Allow the first step to install the installer
    • Once the installer comes up and you can see workload choices (.net desktop and the like), close it
    • Go launch the same InstallCleanup.exe to clean up old build of VS
    • Then re-run the VS installer to install

    If the VS failed to install, I need your help to collect the installation log. Please download and run this collect.exetool, go to %temp% folder and find the vslogs.zip file, upload it to https://onedrive.live.com/and share the link in here.

    Best regards,

    Sara


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Tuesday, September 3, 2019 9:34 AM
    Moderator
  • Thanks for the answer.

    Visual Studio and VS Installer were exactly removed as shown. I ran InstallCleanup.exe /full in CMD.

    And now, after I download vs_commnity.exe and run it, it downloads and extracts data, but then after extracting it just closes itself and nothing happens. Earlier, it started but crashed immediately. Now, it doesn't even start. And after closing, it logs the errors I've pasted in the thread.

    Tuesday, September 3, 2019 1:48 PM
  • Hi Aarivex,

    Could you please clean up the %temp% folder and temporarily disable any antivirus software, run the vs_community.exe as administrator. After that, please collect the latest installation log files like I said in the previous reply and share the vslogs.zip file, thanks for your cooperation.

    Best regards,

    Sara


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Wednesday, September 4, 2019 7:31 AM
    Moderator
  • Hello.

    I've reinstalled windows 10 and I'm facing the same issues, plus another issue came right in between.

    First, the installer just opens and extracts some data, but then does not open the screen where the installer is being downloaded and installed. I managed to temporarily fix this (temporarily because it sometimes still happens) by opening the vs_installer.exe manually. But then, the same issues.

    The logs are for both scenarios (logs2.zip contains all the logs which this thread is about):

    https://1drv.ms/u/s!Ah1ey1Vs14BXg0wA8qKxc1DM1xvl?e=L1MwRb

    https://1drv.ms/u/s!Ah1ey1Vs14BXg01sPsfYI8VdrqEV?e=gpomUg

    Thanks for the reply and your time.

    Friday, September 6, 2019 3:05 PM
  • I also wanted to add that another application started behaving exactly the same as well.

    Taking a look into the Event Viewer gives the AccessViolationException exception as an crash fault.

    And AccessViolationException also occures in ServiceHubController.exe errors.

    I already ran memory tests and checked the correct settings (XMP 2.0, Timings..) in the BIOS, but still..


    • Marked as answer by Aarivex Friday, September 6, 2019 3:13 PM
    • Unmarked as answer by Aarivex Friday, September 6, 2019 3:13 PM
    • Edited by Aarivex Friday, September 6, 2019 3:13 PM
    Friday, September 6, 2019 3:12 PM
  • Hi Aarivex,

    Thanks for your detail information.

    I found the same error message about 'Access Violation', please make sure you run the VS installer as administrator and temporarily disable any antivirus software before the VS installation.

    Best regards,

    Sara


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Monday, September 9, 2019 8:53 AM
    Moderator
  • vs_installer already requires administrative privileges, so I can't run it without it and I tried to manually open it with administrative privileges, but that didn't help. Also I don't use any antivirus.
    • Edited by Aarivex Saturday, September 14, 2019 6:13 PM
    Friday, September 13, 2019 6:21 PM
  • I've uploaded all the logs that I collected in the time.

    https://1drv.ms/u/s!Ah1ey1Vs14BXg1Hr1AdGiB4fg9IR?e=kQLfns

    Monday, September 16, 2019 4:41 PM
  • Hi Aarivex,

    Sorry for the delay reply, please perform a clean boot: https://support.microsoft.com/en-sg/help/929135/how-to-perform-a-clean-boot-in-windows and re-run the VS installer as administrator.

    Best regards,

    Sara


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Wednesday, September 18, 2019 9:00 AM
    Moderator
  • Hello,

    I still face the same issues after an clean boot.

    Wednesday, September 18, 2019 1:40 PM
  • Faulting application name: Microsoft.ServiceHub.Controller.exe, version: 1.3.211.27930, time stamp: 0x9af4007e
    Faulting module name: clr.dll, version: 4.8.4018.0, teitstempel: 0x5d4a67fe
    Exception code: 0xc0000005
    Fault offset: 0x0000000000001fce
    Faulting process id: 0x2c38
    Faulting application start time: 0x01d57aca1289ebe9
    Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\ServiceHub\Controller\Microsoft.ServiceHub.Controller.exe
    Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
    Report Id: e4529198-7beb-4ebe-a8c7-30cf8ba83917
    Full name of faulting package:
    Application ID, that is relative to the faulting package:
    Friday, October 4, 2019 3:46 PM
  • This problem got solved. My CPU had a problem, causing to the error above. Sent it back, got a new one and it works fine now.

    • Marked as answer by Aarivex Saturday, October 19, 2019 8:36 PM
    Saturday, October 19, 2019 8:36 PM