System.Runtime.InteropServices.COMException: Windows Explorer (explorer.exe) just crashed and this caused the virtual desktop service to fail! FancyWM received the following error message: The group or resource is not in the correct state to perform the requested operation. (0x8007139F)

[SleuthChromiumUser]

Describe the bug
Observing the following error:

System.Runtime.InteropServices.COMException (0x80004005): Windows Explorer (explorer.exe) just crashed and this caused the virtual desktop service to fail! FancyWM received the following error message: The group or resource is not in the correct state to perform the requested operation. (0x8007139F)
 ---> System.Runtime.InteropServices.COMException (0x8007139F): The group or resource is not in the correct state to perform the requested operation. (0x8007139F)
   at WinMan.Windows.Com.IComVirtualDesktopManager.IsWindowOnCurrentVirtualDesktop(IntPtr topLevelWindow)
   at WinMan.Windows.FaultTolerantWin32VirtualDesktopService.ExecuteWithRetry[T](Func`1 func)
   at WinMan.Windows.Win32VirtualDesktopManager.WinMan.Windows.IWin32VirtualDesktopManagerInternal.IsNotOnCurrentDesktop(IntPtr hwnd)
   at WinMan.Windows.Win32Window.<GetIsTopLevelVisible>g__CheckCloaked|122_0(<>c__DisplayClass122_0&)
   at WinMan.Windows.Win32Window.GetIsTopLevelVisible(IWorkspace workspace, IntPtr hwnd)
   at WinMan.Windows.Win32Workspace.GetVisibility(Win32WindowHandle window)
   at WinMan.Windows.Win32Workspace.CheckVisibilityChanges(Win32WindowHandle window)
   at WinMan.Windows.Win32Workspace.<RefreshConfiguration>b__64_0()
   at WinMan.Windows.Utilities.EventLoop.Run()
--- End of stack trace from previous location ---
   at FancyWM.Utilities.Dispatchers.<>c__DisplayClass4_0.<RethrowOnDispatcher>b__0()
   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 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 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 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.Application.RunDispatcher(Object ignore)
   at System.Windows.Application.RunInternal(Window window)
   at FancyWM.Startup.AppMain(String[] args)
   at FancyWM.Startup.Main(String[] args)

To Reproduce
Steps to reproduce the behavior:

1. Open '...'
2. Resize '....'
3. Enable '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Desktop (please complete the following information):

• OS: Microsoft Windows NT 10.0.22621.0
• FancyWM Version: 2.14.0.0

Additional context
Add any other context about the problem here.

[veselink1]

As the message says, this is due to Windows Explorer crashing. FancyWM will try to wait for Windows Explorer to recover in certain cases, but that is not always possible. Also, if Windows Explorer does not restart in a timely fashion, there is nothing FancyWM can do other than error out.