search

microsoft / PowerToys

Windows system utilities to maximize productivity
MIT License
109.02k stars 6.43k forks source link

Cannot launch Zone Editor at all #2431

Closed jzelinskie closed 4 years ago

jzelinskie commented 4 years ago

Apologies if this is a duplicate -- I search the issues for Zone Editor and could not find anything comparable.

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.815] PowerToys version: 0.16.1, 0.16.0, 0.15.2 PowerToys module: Fancy Zones Zone Settings: {"app-zone-history":[],"devices":[],"custom-zone-sets":[]}

Steps to reproduce

  1. Install Power Toys
  2. Enable Fancy Zones
  3. Navigate to Settings > Fancy Zones > Edit Zones or press Win + `

I've tried all combinations of the PowerToys versions listed above along with running as Administrator, rebooting, using the msi or msix installers, and also deleting the zone settings.

Potentially unrelated: the Window Walk also only works for a few seconds at startup before the hotkey does nothing.

Expected behavior

The Zone Editor window is displayed allowing me to interactively configure what will become the Zone settings JSON file.

Actual behavior

Cursor gets a loading spinner while in Task Manager a process named Windows Problem Reporting appears briefly. The PowerToys Settings does not crash and remains functioning normally.

Are there logs or something that I can provide that contain the result of the crash?

enricogior commented 4 years ago

Hi @jzelinskie right after trying to open the editor, open Event Viewer go to Windows Log -> Applications and search for an event reporting an error by FancyZonesEditor.exe.

enricogior commented 4 years ago

Also, go to C:\Program Files\PowerToys\modules and double click on FancyZonesEditor.exe it should cause this dialog to appear: image If it doesn't there might be a problem with the .Net runtime.

jzelinskie commented 4 years ago

Thanks @enricogior for all of the suggestions!

When I run C:\Program Files\PowerToys\modules\FancyZonesEditor.exe, I correctly get that window and path error message.

Here's an example of one of the crashes from the Event Viewer:

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: FancyZonesEditor.exe
P2: 0.16.0.0
P3: 5e7e9542
P4: d3d9.dll
P5: 10.0.18362.387
P6: c808fce5
P7: c0000005
P8: 00000000000ac44e
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER23D9.tmp.WERInternalMetadata.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FancyZonesEditor_6679b17261cceb62bb28c4d904ea907dc87b3b_ea7261d5_718a6c2a-46ff-4c2c-b1e8-3a2526c4ee7f

Analysis symbol: 
Rechecking for solution: 0
Report Id: 22e6d268-747b-49e9-91c8-e6a73e166be4
Report Status: 100
Hashed bucket: 
Cab Guid: 0

The contents of WER23D9.tmp.WERInternalMetadata.xml

<?xml version="2.0" encoding="UTF-16"?>
<WERReportMetadata>
    <OSVersionInformation>
        <WindowsNTVersion>10.0</WindowsNTVersion>
        <Build>18363</Build>
        <Product>(0x30): Windows 10 Pro</Product>
        <Edition>Professional</Edition>
        <BuildString>18362.815.amd64fre.19h1_release.190318-1202</BuildString>
        <Revision>815</Revision>
        <Flavor>Multiprocessor Free</Flavor>
        <Architecture>X64</Architecture>
        <LCID>1033</LCID>
    </OSVersionInformation>
    <ProblemSignatures>
        <EventType>APPCRASH</EventType>
        <Parameter0>FancyZonesEditor.exe</Parameter0>
        <Parameter1>0.16.0.0</Parameter1>
        <Parameter2>5e7e9542</Parameter2>
        <Parameter3>d3d9.dll</Parameter3>
        <Parameter4>10.0.18362.387</Parameter4>
        <Parameter5>c808fce5</Parameter5>
        <Parameter6>c0000005</Parameter6>
        <Parameter7>00000000000ac44e</Parameter7>
    </ProblemSignatures>
    <DynamicSignatures>
        <Parameter1>10.0.18363.2.0.0.256.48</Parameter1>
        <Parameter2>1033</Parameter2>
        <Parameter22>e811</Parameter22>
        <Parameter23>e811a2a492680b03a1a1def5192ef72c</Parameter23>
        <Parameter24>15a0</Parameter24>
        <Parameter25>15a0ed5ce903c2d17199a1bd93960291</Parameter25>
    </DynamicSignatures>
    <SystemInformation>
        <MID>C2D4AEDF-0F05-450C-9882-E6068C465271</MID>
        <SystemManufacturer>Micro-Star International Co., Ltd.</SystemManufacturer>
        <SystemProductName>MS-7A40</SystemProductName>
        <BIOSVersion>A.A0</BIOSVersion>
        <OSInstallDate>1564839747</OSInstallDate>
        <OSInstallTime>2019-08-03T13:42:27Z</OSInstallTime>
        <TimeZoneBias>05:00</TimeZoneBias>
    </SystemInformation>
    <SecureBootState>
        <UEFISecureBootEnabled>0</UEFISecureBootEnabled>
    </SecureBootState>
    <ReportInformation>
        <Guid>718a6c2a-46ff-4c2c-b1e8-3a2526c4ee7f</Guid>
        <CreationTime>2020-04-28T02:02:01Z</CreationTime>
    </ReportInformation>
</WERReportMetadata>

and finally the contents of AppCrashFancyZonesEditor$UUID:

Version=1
EventType=APPCRASH
EventTime=132325129207011134
ReportType=2
Consent=1
UploadTime=132325494851035418
ReportStatus=100
ReportIdentifier=718a6c2a-46ff-4c2c-b1e8-3a2526c4ee7f
IntegratorReportIdentifier=22e6d268-747b-49e9-91c8-e6a73e166be4
Wow64Host=34404
NsAppName=FancyZonesEditor.exe
OriginalFilename=FancyZonesEditor.exe
AppSessionGuid=0000398c-0001-0049-db13-0e01011dd601
TargetAppId=W:0006eb9b0fed29cc12f5c7484dd12786045b00000000!000006b86328588a0f6927da1a142dbfd7bea60816c6!FancyZonesEditor.exe
TargetAppVer=2020//03//28:00:07:30!2add1!FancyZonesEditor.exe
BootId=4294967295
ServiceSplit=2564096
TargetAsId=819
IsFatal=1
EtwNonCollectReason=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=FancyZonesEditor.exe
Sig[1].Name=Application Version
Sig[1].Value=0.16.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=5e7e9542
Sig[3].Name=Fault Module Name
Sig[3].Value=d3d9.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.18362.387
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=c808fce5
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00000000000ac44e
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.18363.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=e811
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=e811a2a492680b03a1a1def5192ef72c
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=15a0
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=15a0ed5ce903c2d17199a1bd93960291
UI[2]=C:\Program Files\PowerToys\modules\FancyZonesEditor.exe
LoadedModule[0]=C:\Program Files\PowerToys\modules\FancyZonesEditor.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\Windows\System32\KERNEL32.dll
LoadedModule[4]=C:\Windows\System32\KERNELBASE.dll
LoadedModule[5]=C:\Windows\System32\ADVAPI32.dll
LoadedModule[6]=C:\Windows\System32\msvcrt.dll
LoadedModule[7]=C:\Windows\System32\sechost.dll
LoadedModule[8]=C:\Windows\System32\RPCRT4.dll
LoadedModule[9]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[10]=C:\Windows\System32\SHLWAPI.dll
LoadedModule[11]=C:\Windows\System32\combase.dll
LoadedModule[12]=C:\Windows\System32\ucrtbase.dll
LoadedModule[13]=C:\Windows\System32\bcryptPrimitives.dll
LoadedModule[14]=C:\Windows\System32\GDI32.dll
LoadedModule[15]=C:\Windows\System32\win32u.dll
LoadedModule[16]=C:\Windows\System32\gdi32full.dll
LoadedModule[17]=C:\Windows\System32\msvcp_win.dll
LoadedModule[18]=C:\Windows\System32\USER32.dll
LoadedModule[19]=C:\Windows\System32\IMM32.DLL
LoadedModule[20]=C:\Windows\System32\kernel.appcore.dll
LoadedModule[21]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[22]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
LoadedModule[23]=C:\Windows\SYSTEM32\ucrtbase_clr0400.dll
LoadedModule[24]=C:\Windows\SYSTEM32\VCRUNTIME140_CLR0400.dll
LoadedModule[25]=C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\cea8b8fbc469dcbc6224d523a578e4b3\mscorlib.ni.dll
LoadedModule[26]=C:\Windows\System32\ole32.dll
LoadedModule[27]=C:\Windows\system32\uxtheme.dll
LoadedModule[28]=C:\Program Files (x86)\RivaTuner Statistics Server\RTSSHooks64.dll
LoadedModule[29]=C:\Windows\SYSTEM32\WINMM.dll
LoadedModule[30]=C:\Windows\SYSTEM32\winmmbase.dll
LoadedModule[31]=C:\Windows\System32\cfgmgr32.dll
LoadedModule[32]=C:\Windows\System32\CRYPTSP.dll
LoadedModule[33]=C:\Windows\system32\rsaenh.dll
LoadedModule[34]=C:\Windows\System32\bcrypt.dll
LoadedModule[35]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[36]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System\08f69c55e9284eaab92075159503c897\System.ni.dll
LoadedModule[37]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Core\c9243edb149eb78c5309c103df69d594\System.Core.ni.dll
LoadedModule[38]=C:\Windows\assembly\NativeImages_v4.0.30319_64\FancyZonesEditor\fac02db2dce8c17f954e00eb56cbbffa\FancyZonesEditor.ni.exe
LoadedModule[39]=C:\Windows\assembly\NativeImages_v4.0.30319_64\WindowsBase\4b1919317b8017e84ec44122b5b51adf\WindowsBase.ni.dll
LoadedModule[40]=C:\Windows\assembly\NativeImages_v4.0.30319_64\PresentationCore\f80cf74f6d7c21b493fbce27230bd83b\PresentationCore.ni.dll
LoadedModule[41]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Presentatio5ae0f00f#\4abe2047e7a3f0e33459880ba5b95e3a\PresentationFramework.ni.dll
LoadedModule[42]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xaml\b812c8a0807ea063510a3855c48f871d\System.Xaml.ni.dll
LoadedModule[43]=C:\Windows\SYSTEM32\dwrite.dll
LoadedModule[44]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\wpfgfx_v0400.dll
LoadedModule[45]=C:\Windows\System32\OLEAUT32.dll
LoadedModule[46]=C:\Windows\SYSTEM32\MSVCP140_CLR0400.dll
LoadedModule[47]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\PresentationNative_v0400.dll
LoadedModule[48]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Configuration\36d0bbf456e19171162fb117487d13e6\System.Configuration.ni.dll
LoadedModule[49]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml\e2507c6929371fa69b5e96a6e097ee69\System.Xml.ni.dll
LoadedModule[50]=C:\Windows\System32\shell32.dll
LoadedModule[51]=C:\Windows\System32\shcore.dll
LoadedModule[52]=C:\Windows\System32\windows.storage.dll
LoadedModule[53]=C:\Windows\System32\profapi.dll
LoadedModule[54]=C:\Windows\System32\powrprof.dll
LoadedModule[55]=C:\Windows\System32\UMPDC.dll
LoadedModule[56]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Text.Json\7f30133b2a0d5bbdf5195d5c27d36889\System.Text.Json.ni.dll
LoadedModule[57]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Memory\50dc0a76feaf49c66fb9aa4500ca01f2\System.Memory.ni.dll
LoadedModule[58]=C:\Windows\assembly\NativeImages_v4.0.30319_64\netstandard\2ad4eed78c939ff697182ffb7fac1d2c\netstandard.ni.dll
LoadedModule[59]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Buffers\6fea0c8956e546aaf260e7323214ef34\System.Buffers.ni.dll
LoadedModule[60]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Runtea61dfd5#\ad74a0bb134ac91478d7c80e17b09bcb\System.Runtime.CompilerServices.Unsafe.ni.dll
LoadedModule[61]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
LoadedModule[62]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Numeb60ee252#\cf9523bd3d15f9f04fdb775b7d340703\System.Numerics.Vectors.ni.dll
LoadedModule[63]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.ValueTuple\19d013549b662b05205d1851f72fbf31\System.ValueTuple.ni.dll
LoadedModule[64]=C:\Windows\assembly\NativeImages_v4.0.30319_64\MahApps.Metro\3928672cf569c54349ff28e0c4755362\MahApps.Metro.ni.dll
LoadedModule[65]=C:\Windows\System32\MSCTF.dll
LoadedModule[66]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Presentatioaec034ca#\49fd7f160080030d6769eb7ee2496166\PresentationFramework.Aero2.ni.dll
LoadedModule[67]=C:\Windows\assembly\NativeImages_v4.0.30319_64\ControlzEx\a306294dd874eb90ab7a0254c731e9d8\ControlzEx.ni.dll
LoadedModule[68]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Runtime\ecf16dcbbc95961331f8ec542cb7c3d9\System.Runtime.ni.dll
LoadedModule[69]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.X53480ad6#\ae4833fc4035bba686a0803a1b5c2483\Microsoft.Xaml.Behaviors.ni.dll
LoadedModule[70]=C:\Windows\SYSTEM32\DWMAPI.dll
LoadedModule[71]=C:\Windows\SYSTEM32\d3d9.dll
LoadedModule[72]=C:\Windows\SYSTEM32\dxcore.dll
LoadedModule[73]=C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9952681a7bb1dfac\nvldumdx.dll
LoadedModule[74]=C:\Windows\System32\crypt32.dll
LoadedModule[75]=C:\Windows\System32\MSASN1.dll
LoadedModule[76]=C:\Windows\SYSTEM32\cryptnet.dll
LoadedModule[77]=C:\Windows\System32\WINTRUST.DLL
LoadedModule[78]=C:\Windows\System32\imagehlp.dll
LoadedModule[79]=C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9952681a7bb1dfac\nvd3dumx.dll
LoadedModule[80]=C:\Windows\SYSTEM32\urlmon.dll
LoadedModule[81]=C:\Windows\SYSTEM32\iertutil.dll
LoadedModule[82]=C:\Windows\SYSTEM32\WindowsCodecs.dll
LoadedModule[83]=C:\Windows\SYSTEM32\wtsapi32.dll
LoadedModule[84]=C:\Windows\SYSTEM32\WINSTA.dll
LoadedModule[85]=C:\Windows\System32\clbcatq.dll
LoadedModule[86]=C:\Windows\system32\dataexchange.dll
LoadedModule[87]=C:\Windows\system32\d3d11.dll
LoadedModule[88]=C:\Windows\system32\dcomp.dll
LoadedModule[89]=C:\Windows\system32\dxgi.dll
LoadedModule[90]=C:\Windows\system32\twinapi.appcore.dll
LoadedModule[91]=C:\Windows\system32\RMCLIENT.dll
LoadedModule[92]=C:\Windows\system32\nvspcap64.dll
LoadedModule[93]=C:\Windows\SYSTEM32\ntmarta.dll
LoadedModule[94]=C:\Windows\SYSTEM32\gpapi.dll
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=18363
OsInfo[3].Key=ubr
OsInfo[3].Value=815
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=244
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=386659
OsInfo[15].Key=osinsty
OsInfo[15].Value=2
OsInfo[16].Key=iever
OsInfo[16].Value=11.778.18362.0-11.0.185
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=32718
OsInfo[19].Key=svolsz
OsInfo[19].Value=953
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=190318
OsInfo[22].Key=bldtm
OsInfo[22].Value=1202
OsInfo[23].Key=bldbrch
OsInfo[23].Value=19h1_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.18362.815.amd64fre.19h1_release.190318-1202
OsInfo[30].Key=buildflightid
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
File[0].CabName=WERInternalMetadata.xml
File[0].Path=WER23D9.tmp.WERInternalMetadata.xml
File[0].Flags=327682
File[0].Type=5
File[0].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER23D9.tmp.WERInternalMetadata.xml
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=FancyZonesEditor
AppPath=C:\Program Files\PowerToys\modules\FancyZonesEditor.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=5874D351A35EA2938CE2927AA2A99152
MetadataHash=545017281
enricogior commented 4 years ago

@jzelinskie can you please upload this file:

C:\Users\%USERNAME%\AppData\Local\Microsoft\PowerToys\FancyZones\zones-settings.json

Be aware it contains the app history section (is the list of apps that you have zoned), feel free to edit the file to remove the app history section for privacy reasons. When you upload it, change the extension to .txt or zip it otherwise GittHub will not accept it. Thank you.

jzelinskie commented 4 years ago

@enricogior I actually included that in my first post under Zone Settings. It's always that empty JSON object. I've tried deleting it entirely and attempting to let it be recreated, too.

Just to reiterate:

{"app-zone-history":[],"devices":[],"custom-zone-sets":[]}
enricogior commented 4 years ago

OK, so please try these steps:

jzelinskie commented 4 years ago

The registry key was not present, and after following the rest of the steps, there was no difference in behavior.

The newly generated directory looks like:

PowerToys
├── FancyZones
│  └── zones-settings.json
├── File Explorer
├── Shortcut Guide
└── update_state.json

zone-settings.json:

{"app-zone-history":[],"devices":[],"custom-zone-sets":[]}

update_state.json:

{"github_update_last_checked_date":"1588116428"}
enricogior commented 4 years ago

Can you try installing v0.17 and see if the problem still persists? https://github.com/microsoft/PowerToys/releases

jzelinskie commented 4 years ago

I've actually figured it out! It happens only when MSI Afterburner is open. I use this to program to keep my GPU undervolt applied, so I cannot really use PowerToys until this is fixed. Afterburner is a generic tool and can be used for any GPU, so you can test this locally even without any MSI products (my GPU is manufactured by EVGA).

EDIT: When I close Afterburner and play with it, it looks like this doesn't support multiple displays either?

enricogior commented 4 years ago

@jzelinskie thanks for the investigation.

it looks like this doesn't support multiple displays either

FancyZones does support multi monitor, it's the UI that is not ideal for it and we will change it. You can find information on how to use it on multi monitor here: https://github.com/microsoft/PowerToys/blob/master/src/modules/fancyzones/README.md

enricogior commented 4 years ago

Closing this as dup of https://github.com/microsoft/PowerToys/issues/707 We should add it to the readme or to a pinned "known issue" tracker.