Powertoys: FancyZones not working at all in 0.15.1

[dixonte]

Environment

Windows build number: 10.0.18363.592
PowerToys version: 0.15.1
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce

1. Start from v0.14.1
2. Set up FancyZones to your liking
3. Install 0.15 over the top, FancyZones stop working
4. Install 0.15.1 over the top, FancyZones still not working
5. Uninstall 0.15.1
6. Install 0.15.1, FancyZones still not working

Expected behavior

• The Edit Zones button in PowerToys Settings should bring up the zone editor
• Pressing the zone editor hotkey should bring up the zone editor hotkey
• Dragging windows with the shift key should show zones into which the window can be docked

Actual behavior

None of the above

Screenshots

[enricogior]

Hi @dixonte

EDIT: for other users that may have the same problem: before deleting the registry key, can you please save the key and posted here?
Also open the Event Viewer and and search in Windows Logs -> Application for an entry for PowerToys.exe or FancyZonesEditor.exe and report it here?

Try a full cleanup of all PowerToys settings:

• quit PowerToys
• open the Registry Editor and delete the key Computer\HKEY_CURRENT_USER\Software\SuperFancyZones
• go to C:\Users\%USERNAME%\AppData\Local\Microsoft and delete the folder PowerToys
• restart PowerToys

[scrobbleme]

Same here, the workaround from @enricogior worked.
Unfortunately this also removes all settings.

[dixonte]

This worked for me.

[crutkas]

Increasing severity of bug

[jccraig]

Fix did not work for me. I uninstalled 15.1 (as well as original 14.1, several times each), then deleted the folder and the key as suggested above. I would think all traces of Power Toy should have been off my system, but starting fresh install of 15.1 showed the "repair or remove" dialog. I tried remove yet again. Checked folder and key, still gone. Then tried fresh install again of 15.1. This time install proceeded as expected, but Win+` doesn't work, and opening settings and clicking on [Edit Zone] in FancyZones settings does nothing. Must still be something in my system hidden away somewhere. What else can I delete, reset, or whatever? BTW, rebooting several times during all this hasn't helped. I'm stuck, and I really liked FancyZones! Ideas? How can I completely remove all traces of Power Toys so I can start over?

[enricogior]

@jccraig
there should be only two things in the system that can effect the FZ editor.
It is possible that the fist time you deleted the registry key and the settings folder, FZ was still running and the registry key or the folder were recreated.
Just follow the steps again. quit PowerToys and make sure it's not running and then proceed with the reg key and folder deletion.
This should work.

[enricogior]

@dixonte @scrobbleme @jccraig
can you please open the Event Viewer, go to Windows Logs -> Application and search for an error for FancyZonesEditor.exe?
Thanks.

[scrobbleme]

I'm not sure if this is the right log, but I can't find anything related to FanzyZones

[enricogior]

@scrobbleme
yes that is the right log, in your case you couldn't run PowerToys before cleaning up the settings, or was the FancyZones editor that did not open?

[scrobbleme]

@scrobbleme
yes that is the right log, in your case you couldn't run PowerToys before cleaning up the settings, or was the FancyZones editor that did not open?

• I was using FanzyZones before (installed via Chocolatey, started using it at version 0.13.0)
• After the update (from 0.14.1)
  
  
  
  • PowerToys was running and I was able to configure it
  
  
  • But I wasn't able to drop windows into my configured zones anymore
  
  
  • restarting Windows/PowerToys didn't helped, only your workaround
  
  

[enricogior]

PowerToys was running and I was able to configure it

Just to make sure, were you able to open the FancyZones editor?

[scrobbleme]

PowerToys was running and I was able to configure it

Just to make sure, were you able to open the FancyZones editor?

Yes, this worked.

[jccraig]

Today I gave it another try, while jotting down each step...

1. Exited from Power Toys
2. Control Panel - uninstall Power Toys, worked okay
3. Ran Microsoft's repair tool, file name is…
   MicrosoftProgram_Install_and_Uninstall.meta.diagcab
   This program checks for uninstall issues, and it did find
   "PowerToys (Preview)" which I selected and let it uninstall further.
   It reported making changes okay for problems it detected removing PowerToys.
4. Ran regedit. Did not find \HKEY_CURRENT_USER\Software\SuperFancyZones
   (I did remove this yesterday before reinstalling vs. 15.1)
5. Deleted folder at c:\Users{me}\AppData\Local\MicrosoftPowerToys
   (Unlike the registry key, this folder was there again, so I deleted it)
6. Rebooted system
7. Double checked registry and files. No sign of PowerToys anywhere suggested.
8. Checked Task Manager, no sign of PowerToys process.
9. Ran Microsoft's repair program again, no sign of PowerToys.
10. re-downloaded latest PowerToysSetup-0.15.1-x64.msi
11. Installed PowerToys 15.1 using default options
12. Opened PowerToys Settings, selected FancyZones, clicked [Edit Zones]
13. Nothing happens. Same with [Win+`], nothing happens.

I have a Dell Intel i7-8700 cpu @ 3.20 GHz
16 GB ram, 15.8 usable
64-bit op sys, x64-based processor
Windows 10 Home, Vs. 1909, OS build 18363.657
NOTE: I do have two monitors.

[enricogior]

@jaccz
you should not run Microsoft's repair program after deleting the AppData\Local\Microsoft\PowerToys folder and the SuperFancyZones reg key.

There are only four steps to do, you don't need to uninstall/reinstall or reboot:

• make sure PowerToys is not running
• delete AppData\Local\Microsoft\PowerToys
• delete the SuperFancyZones reg key (at this point it shouldn't exist anymore, but make sure)
• restart PowerToys

If the problem persists, open the Event Viewer, go to Windows Logs -> Application and search for an error with source .NET Runtime that has Application: FancyZonesEditor.exe has first line in General tab, copy the entire content and post it here, that will allow to understand what is causing the error.
Thanks.

[jccraig]

Hi Enrico,

I exited PowerToys, deleted the folder, and checked the registry.
Restarting PowerToys still resulted in the same problems with FancyZones.
I then checked into Event Viewer and found a sequence of errors all
mentioning FancyZones. I copied them in chronological order to create a PDF
file for review. I'll attach that PDF.

Thanks for checking into this situation. In recent months have found FancyZones to be a
great productivity tool. I do hope to be able to use it again!
-John

On Fri, Mar 6, 2020 at 11:40 AM Enrico Giordani [e-mail]
wrote:

@jaccz https://github.com/jaccz
you should not run Microsoft's repair program after deleting the
AppData\Local\MicrosoftPowerToys folder and the SuperFancyZones reg key.

There are only four steps to do, you don't need to uninstall/reinstall or
reboot:

• make sure PowerToys is not running
• delete AppData\Local\MicrosoftPowerToys
• delete the SuperFancyZones reg key (at this point it shouldn't exist
  anymore, but make sure)
• restart PowerToys

If the problem persists, open the Event Viewer, go to Windows Logs ->
Application and search for an error with source .NET Runtime that has Application:
FancyZonesEditor.exe has first line in General tab, copy the entire
content and post it here, that will allow to understand what is causing the
error.
Thanks.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/1451?email_source=notifications&email_token=AA7RAOJ3X7P3V6CHH4W2INDRGE7RFA5CNFSM4LB34RDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOCMNAI#issuecomment-595904129,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA7RAOK4ZKRDGCRGDDXIUKTRGE7RFANCNFSM4LB34RDA
.

[DominicJ2]

EDIT: for other users that may have the same problem: before deleting the registry key, can you please save the key and posted here?

@enricogior You want Everything under \HKCU\Software\SuperFancyZones? Do you want it just attached to the post?

Here are the 2 errors and 1 windows error reporting message I see in my Event log when I tried to save my zone layout

1: (I fixed the formatting on this one because it was just one very long line)

 <System>
  <Provider Name=".NET Runtime" /> 
  <EventID Qualifiers="0">1026</EventID> 
  <Level>2</Level> 
  <Task>0</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2020-03-06T23:25:05.303745600Z" /> 
  <EventRecordID>1048337</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>XXXXXXXXXXXXXXXXXXXXXXXXX</Computer> 
  <Security /> 
  </System>
<EventData>
  <Data>Application: FancyZonesEditor.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IOException
   at System.IO.__Error.WinIOError(Int32, System.String)
   at System.IO.FileStream.Init(System.String, System.IO.FileMode, System.IO.FileAccess, Int32, Boolean, System.IO.FileShare, Int32, System.IO.FileOptions, SECURITY_ATTRIBUTES, System.String, Boolean, Boolean, Boolean)
   at System.IO.FileStream..ctor(System.String, System.IO.FileMode, System.IO.FileAccess, System.IO.FileShare)
   at FancyZonesEditor.Models.LayoutModel.Apply(System.Windows.Int32Rect[])
   at FancyZonesEditor.MainWindow.Apply_Click(System.Object, System.Windows.RoutedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
   at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
   at System.Windows.Controls.Primitives.ButtonBase.OnClick()
   at System.Windows.Controls.Button.OnClick()
   at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(System.Windows.Input.MouseButtonEventArgs)
   at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
   at System.Windows.UIElement.ReRaiseEventAs(System.Windows.DependencyObject, System.Windows.RoutedEventArgs, System.Windows.RoutedEvent)
   at System.Windows.UIElement.OnMouseUpThunk(System.Object, System.Windows.Input.MouseButtonEventArgs)
   at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
   at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
   at System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs)
   at System.Windows.Input.InputManager.ProcessStagingArea()
   at System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs)
   at System.Windows.Input.InputProviderSite.ReportInput(System.Windows.Input.InputReport)
   at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32)
   at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef)
   at System.Windows.Interop.HwndSource.InputFilterMessage(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()
</Data> 
  </EventData>
  </Event>

2:

 <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2020-03-06T23:25:06.011747900Z" /> 
  <EventRecordID>1048338</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>XXXXXXXXXXXXXXXXXXXXXXXXX</Computer> 
  <Security /> 
  </System>
 <EventData>
  <Data>FancyZonesEditor.exe</Data> 
  <Data>0.15.1.0</Data> 
  <Data>5e5ed077</Data> 
  <Data>KERNELBASE.dll</Data> 
  <Data>10.0.18362.628</Data> 
  <Data>f96f12ee</Data> 
  <Data>e0434352</Data> 
  <Data>000000000003a839</Data> 
  <Data>69e0</Data> 
  <Data>01d5f40e6fdd8bbe</Data> 
  <Data>C:\Program Files\PowerToys\modules\FancyZonesEditor.exe</Data> 
  <Data>C:\WINDOWS\System32\KERNELBASE.dll</Data> 
  <Data>01f81653-33cb-4d03-a55a-78856ad54691</Data> 
  <Data /> 
  <Data /> 
  </EventData>
  </Event>

3: (I fixed the formatting here some too)

 <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
 <System>
  <Provider Name="Windows Error Reporting" /> 
  <EventID Qualifiers="0">1001</EventID> 
  <Level>4</Level> 
  <Task>0</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2020-03-06T23:25:16.415827100Z" /> 
  <EventRecordID>1048339</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>XXXXXXXXXXXXXXXXXXXXXXXXX</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data /> 
  <Data>0</Data> 
  <Data>CLR20r3</Data> 
  <Data>Not available</Data> 
  <Data>0</Data> 
  <Data>FancyZonesEditor.exe</Data> 
  <Data>0.15.1.0</Data> 
  <Data>5e5ed077</Data> 
  <Data>mscorlib</Data> 
  <Data>4.8.4121.0</Data> 
  <Data>5deabc55</Data> 
  <Data>1693</Data> 
  <Data>1d8</Data> 
  <Data>System.IO.IOException</Data> 
  <Data /> 
  <Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7580.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER791B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7939.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7988.tmp.txt
\\?\C:\Users\XXXXXX\AppData\Local\Temp\WER79F8.tmp.appcompat.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FancyZonesEditor_b0657530dffe471e1593cbd5ec85435e49f420b2_ce57187d_cab_ce35bab3-d12a-4010-b89a-63aaa8938d0c\memory.hdmp
WERGenerationLog.txt
</Data> 
  <Data /> 
  <Data /> 
  <Data>0</Data> 
  <Data>01f81653-33cb-4d03-a55a-78856ad54691</Data> 
  <Data>2164260864</Data> 
  <Data /> 
  <Data>0</Data> 
  </EventData>
  </Event>

I did keep the memory dump if you want that.

[enricogior]

@jccraig

I copied them in chronological order to create a PDF file for review. I'll attach that PDF.

If you reply by email, github will strip the attached files.
I only need the most recent error that starts with Application: FancyZonesEditor.exe, you can just copy and past it as regular text and it will show up in the github comment.
Thanks.

[enricogior]

Hi @DominicJ2

You want Everything under \HKCU\SoftwareSuperFancyZones? Do you want it just attached to the post?

Yes and yes. Right-click on the SuperFancyZones key and select "Export" from the context menu.
It will generate a single .reg file that you can zip and upload here.

Here are the 2 errors

Perfect, the first one is the one that give us the important information.
Thanks.

[jccraig]

Here's the first of the 6 error messages from my event log that happened during one attempt to run Power Toys and then Edit Zones...

Application: FancyZonesEditor.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentNullException
at System.IO.FileStream.Init(System.String, System.IO.FileMode, System.IO.FileAccess,
Int32, Boolean, System.IO.FileShare, Int32, System.IO.FileOptions, SECURITY_ATTRIBUTES,
System.String, Boolean, Boolean, Boolean)
at System.IO.FileStream..ctor(System.String, System.IO.FileMode, System.IO.FileAccess,
System.IO.FileShare)
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.CulturePreservingExecutionC
ontext, 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.Dispatc
herPriority, 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.Dispatche
rFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at FancyZonesEditor.App.Main()

[enricogior]

We have a fix for this. We will release 0.15.2.

[enricogior]

Fix available in v0.15.2