Powertoys: FancyZonesEditor crashes on start (0.15)

[seritools]

Environment

Windows build number: current Insider Fast, 19569
PowerToys version: 0.15
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce

Click either on the "Edit Zones" button or press the zone editor hotkey.

Expected behavior

The editor should open.

Actual behavior

FancyZoneEditor.exe crashes, with the following entries in Eventvwr. The issue persists even after deleting my config in %localappdata%\Microsoft\Powertoys

Application: FancyZonesEditor.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.FormatException
   at System.Guid+GuidResult.SetFailure(ParseFailureKind, System.String, System.Object, System.String, System.Exception)
   at System.Guid.TryParseGuidWithNoStyle(System.String, GuidResult ByRef)
   at System.Guid.TryParseGuid(System.String, GuidStyles, GuidResult ByRef)
   at System.Guid.Parse(System.String)
   at FancyZonesEditor.Models.LayoutModel.LoadCustomModels()
   at FancyZonesEditor.Settings.get_CustomModels()
   at FancyZonesEditor.MainWindow.SetSelectedItem()
   at System.Windows.FrameworkElement.RaiseInitialized(System.Windows.EventPrivateKey, System.EventArgs)
   at System.Windows.FrameworkElement.TryFireInitialized()
   at MS.Internal.Xaml.Runtime.ClrObjectRuntime.InitializationGuard(System.Xaml.XamlType, System.Object, Boolean)

Exception Info: System.Windows.Markup.XamlParseException
   at System.Windows.Markup.XamlReader.RewrapException(System.Exception, System.Xaml.IXamlLineInfo, System.Uri)
   at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri)
   at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri)
   at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean)
   at FancyZonesEditor.EditorOverlay..ctor()
   at FancyZonesEditor.App.OnStartup(System.Object, System.Windows.StartupEventArgs)
   at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
   at System.Windows.Application.<.ctor>b__1_0(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(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.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Application.RunDispatcher(System.Object)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at FancyZonesEditor.App.Main()

Faulting application name: FancyZonesEditor.exe, version: 0.15.0.0, time stamp: 0x5e5d4fcc
Faulting module name: KERNELBASE.dll, version: 10.0.19569.1000, time stamp: 0xa6e2770a
Exception code: 0xe0434352
Fault offset: 0x000000000003a599
Faulting process id: 0x3a44
Faulting application start time: 0x01d5f193e002b8b9
Faulting application path: C:\Program Files\PowerToys\modules\FancyZonesEditor.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 9e52ee9a-ea90-4126-a1dc-ca47eb6726dd
Faulting package full name: 
Faulting package-relative application ID: 



md5-2cb9b6d5f00662e3e008605861c914a1



```plain
Faulting application name: FancyZonesEditor.exe, version: 0.15.0.0, time stamp: 0x5e5d4fcc
Faulting module name: FancyZonesEditor.ni.exe, version: 0.15.0.0, time stamp: 0x5e5d4fcc
Exception code: 0xc0000094
Fault offset: 0x000000000003e3f7
Faulting process id: 0x3294
Faulting application start time: 0x01d5f19355fe1a14
Faulting application path: C:\Program Files\PowerToys\modules\FancyZonesEditor.exe
Faulting module path: C:\Windows\assembly\NativeImages_v4.0.30319_64\FancyZonesEditor\70d63239e0e74ea77f56ba5b7e076b43\FancyZonesEditor.ni.exe
Report Id: d32a30dc-2ef3-4a72-8ad9-8355086b3999
Faulting package full name: 
Faulting package-relative application ID: 

Screenshots

[crutkas]

@enricogior can we get someone to look at this ASAP?

[crutkas]

We may want to hot fix this

[enricogior]

I know what it is, the fix will be ready in a few minutes.

[seritools]

OK, I found the problem. Somehow, this was my zones-settings.json after deleting %appdata%\Microsoft\PowerToys:
json { "app-zone-history": [], "devices": [], "custom-zone-sets": [ { "uuid": "{3AD62289-5C1E-470D-8EF8-61F09B3346E2}", "name": "Right monitor", "type": "canvas", "info": { "ref-width": 2560, "ref-height": 1400, "zones": [{ "X": 0, "Y": 0, "width": 1013, "height": 1400 }] } }, { "uuid": "2", "name": "Middle", "type": "canvas", "info": { "ref-width": 2048, "ref-height": 1112, "zones": [] } } ] }

The 2 UUID is obviously broken, and I'm sure I've deleted the full config once (even restarted my system).
After just emptying the file instead of deleting and restarting PowerToys/FancyZones it seems to work fine again.

[enricogior]

Also got this one in-between multiple starts once (but only once):

Fix under testing for this one.

For the other issue, the 2 UUID, that is related to this one, is work in progress.

[enricogior]

@seritools
you didn't delete the SuperFancyZones reg key, right?
If not, would you be willing to test 0.15.1 to see if the problem is fixed for you?
It will simply require to uninstall 0.15.0, delete the %appdata%\Microsoft\PowerToys folder and install 0.15.1 that will re-import the old settings from the registry key.
Thanks.

[seritools]

Sure, no problem! Will test it once the DL is available (or did I miss it somewhere already :O)

Didn't delete the registry keys yet, no.

[enricogior]

OK I'll let you know as soon as the new build is ready. Thank you!

[crutkas]

Doing a build right now. @seritools can you email me and i'll give you a private drop for testing?

[stefansjfw]

Sorry. Closed it by accident

[crutkas]

0.15.1 has been released. https://github.com/microsoft/PowerToys/releases/tag/v0.15.1