Last update 2023.2 with error dont open Uipath Studio and disconected Assistant

Hi, my name is Camilo. Im developer UiPath for two years. Always update the version and dont have any problem.

But this morning (01/03/2023) UiPath community version requiered update with version 2023.2, now my UiPath Studio dont open, and assistant dont connect (i’ve black circle).

check with a two friend, and the same thing happens in this version. Does anyone else have this problem?

if i install the last version It’s work… (but I have to click all the time that it persists in the update 2023.2).

Same problem here.
Below the error log, this is happening only in a instance from a VM. My physical laptop has no problems.

How to solve this?
Thank you all.

23.2.0-beta.11986+Branch.release-v23.2.Sha.cf2c97d1d5fa33ec4991b279dbc0775c4eaed78d

Object reference not set to an instance of an object.

Error: System.NullReferenceException: Object reference not set to an instance of an object.
at UiPath.Studio.Shell.ShellApplication.StudioShellApplication.LoadPlugins(IProfile profile)
at UiPath.Studio.Core.StudioApplication.StudioApplication.PostLicenseInitAsync()
at UiPath.Studio.Shell.ShellApplication.StudioShellApplication.HandleAquireLicense()
at UiPath.Studio.Shell.ShellApplication.StudioShellApplication.OnTempWindowLoaded(Object sender, RoutedEventArgs e)
at System.Threading.Tasks.Task.<>c.b__128_0(Object state)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
— End of stack trace from previous location —
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.Run()
at System.Windows.Application.RunDispatcher(Object ignore)
at System.Windows.Application.RunInternal(Window window)
at System.Windows.Application.Run(Window window)
at UiPath.Studio.Shell.ShellApplication.StudioShellApplication.HandleBeforeLicensingInit()
at UiPath.Studio.Core.StudioApplication.StudioApplication.StartApplication()
at UiPath.Studio.Core.StudioApplication.StudioApplication.Start(String args), HResult -2147467261

Hi @Camilo_Sepulveda

Please click on the profile icon It means Preferences there you can see the Signin, Provide your existing credentials it will connect to assistant and studio as well as .

please try .

Hi @GANESH_BALAGAM

in profile, preference “Singing” when you do not have an account it represents it with gray color.

This is color “black” You can not disconnect “logout” or from studio (dont open) see the account.

Hi @gabrielvandrift same problem here, i hope get fixed

The Robot Command Line Interface (UiRobot.exe) is a console application which can request to start jobs, and waits for their output. It is a direct client of the Robot service, and communication is done through an IPC protocol.

To make use of the command line arguments supported by Robots, make sure that the UiPath Robot service is running. If not, start it from the Services Microsoft Management Console snap-in.

To make it easier for you to work with command line arguments, navigate to the directory in which the Robot is installed using the change directory command. For example, if you did not change the default location of the Robot, you can use the following: cd C:\Program Files (x86)\UiPath\Studio.

The services UiPath Robot dont exist, i try execute in my folder but dont running.

Look at my assistant,

I have a similar issue, Studio was updated to 2023.2 version, the assistant has no problem to connect to orchestrator, but i’m getting the object reference with studio. Any sugestion?

Note: With 2021.10 version i had no problems