You’re offline. This is a read only version of the page.
Hi There: I tried uninstalling power desktop and reinstalling. Running windows 11.
Keep getting this error:
Message = Could not load file or assembly 'Microsoft.Flow.RPA.Desktop.Robin.SDK, Version=2.12.234.21216, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Error = System.IO.FileLoadException
Full text = System.IO.FileLoadException: Could not load file or assembly 'Microsoft.Flow.RPA.Desktop.Robin.SDK, Version=2.12.234.21216, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Microsoft.Flow.RPA.Desktop.Robin.SDK, Version=2.12.234.21216, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
at System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly, ObjectHandleOnStack retTypes)
at System.Reflection.RuntimeAssembly.GetExportedTypes()
at Microsoft.Flow.RPA.Desktop.Robin.Engine.ModuleLoader.Module.IsModuleAssembly(Assembly assembly)
at Microsoft.Flow.RPA.Desktop.Robin.Engine.ModuleLoader.ModuleLoader.LoadModuleAssemblies(IList`1 modulePathsToLoad)
at Microsoft.Flow.RPA.Desktop.Shared.Logging.LoggerTraceOperationExtensions.TraceOperation[T](ILogger`1 logger, String methodName, Action logEventAction, Action func, Func`1 getSuccessMessage, Func`2 getFailureMessage, LogData[] data)
at Microsoft.Flow.RPA.Desktop.Console.Host.MainViewModel.<InitializeAsync>b__124_2()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Flow.RPA.Desktop.Console.Host.MainViewModel.<<InitializeAsync>g__InitializeAsyncInternal|124_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Flow.RPA.Desktop.Shared.Logging.LoggerTraceOperationExtensions.<TraceOperationAsync>d__12`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Flow.RPA.Desktop.Console.Host.MainViewModel.<InitializeAsync>d__124.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Flow.RPA.Desktop.Shared.Common.Extensions.TaskExtensions.<FireAndForget>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
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)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Hi,
It doesen't appear that PAD supports Windows 11 yet as per the system requirments: https://docs.microsoft.com/en-us/power-automate/desktop-flows/setup
So unfortunately you will have to wait it seems. I would imagine that even if you get it workign vi a a work around, it can't be relied upon as it's not a supported system so it may be a headache you don't need.
I would recommend using it on a Win 10 Vm if you cant downgrade to Win 10.
Share
Report
All responses (
Answers (
72
