May
20
23 hours ago
Activity icon
issue

palenshus issue microsoft/PowerToys

palenshus
palenshus

PowerToys Run should provide a mechanism to disable plugins if they're missing dependencies

Description of the new feature / enhancement

The VS Code plugin can be toggled on even if you don't have VS Code installed. IMO, it should be disabled and grayed out in the settings page, with a message indicating why.

This could be accomplished by a new interface in Wox.Plugin which plugins could implement to report back a status saying whether they can be enabled or not, and if not a string saying why.

Scenario when this would be used?

For the VS Code plugin, and other plugins that depend on the presence of various dependencies. For example, a OneNote plugin would require OneNote installed, the Everything plugin depends on Everything, a Graph plugin would require an MSA logged in, etc.

Supporting information

No response

started
started time in 55 minutes ago
started
started time in 1 hour ago
Activity icon
issue

dend issue comment microsoft/PowerToys

dend
dend

Awake "Keep Screen On" does not work Win11

Microsoft PowerToys version

0.53.1

Running as admin

  • Yes

Area(s) with issue?

Awake

Steps to reproduce

I upgraded to Win 11 Pro from Win 10 Pro and the Keep Screen On function failed to work! Stay awake works just fine. I performed a 'Clean Install' of Win 11 Pro and I still have the same problem, Stay Awake works but Keep Screen On does not. I have reinstalled the app and tried old version 0.47 and it is still the same (back on v0.53.1 now)

✔️ Expected Behavior

Power Plan is set to turn off screen after 10 minutes, but some apps keep the system up while they are running. I expected the Screen to stay on like it did with Windows 10 after 10 minutes unless the PC goes to sleep.

❌ Actual Behavior

Screen stays on according to Power Plan settings

Other Software

No response

dend
dend

@BobbyBare can you please provide your logs, along with some details on your current Awake settings that you've configured?

Activity icon
issue

rjpaulsen issue comment microsoft/PowerToys

rjpaulsen
rjpaulsen

⭐Feature Request: Ability to export & import all the settings.

Description of the new feature / enhancement

Export a file that have the current settings of PowerToys & could be imported to PowerToys to assign those settings.

Scenario when this would be used?

When you are trying to backup your settings, transfer settings between pc, or trying to reinstall the app due to some problems

Supporting information

Using JSON or Dat files would be a great idea to export

rjpaulsen
rjpaulsen

The following folder contains a sub-folder for each utility (like \FancyZones):

C:\Users\XXXX\AppData\Local\Microsoft\PowerToys

Each of these folders has a json settings file for the utility (like \FancyZones\custom-layouts.json).

These files can be backed up, restored, transferred and modified.

Activity icon
issue

rjpaulsen issue comment microsoft/PowerToys

rjpaulsen
rjpaulsen

FancyZones and Microsoft Teams Notification Issue

Microsoft PowerToys version

.58

Running as admin

  • Yes

Area(s) with issue?

FancyZones

Steps to reproduce

  1. Start Microsoft Teams
  2. Snap Microsoft Teams to a Zone
  3. Minimize Microsoft Teams
  4. Wait for an incoming Microsoft Teams message. This will generate a "toaster" style notification.

✔️ Expected Behavior

The "toaster" style notification should appear in the lower-right corner of the screen,

❌ Actual Behavior

The "toaster" style notification appears in the upper-left corner of the zone that Teams was snapped to,

BONUS: If you then use a hot-key to change layouts, a blank "toaster" style notification box moves to the upper-left corner of the newly selected zone. This is on top of all windows, even the edit-zone UI (As shown here...)

image

Other Software

No response

rjpaulsen
rjpaulsen

I see you flagged this as FancyZone-Settings. It's not actually an issue with Settings (It's the main app itself). I used that screenshot because it showed where my zones are. Thanks!

Activity icon
issue

crazy4ever issue comment microsoft/PowerToys

crazy4ever
crazy4ever

App runs in system tray, but not opening

Microsoft PowerToys version

0.58.0

Running as admin

  • Yes

Area(s) with issue?

General, System tray interaction

Steps to reproduce

Installed. Set to run as admin. Worked fine until rebooted. Since then won't open. Reinstalled. Still won't open.

✔️ Expected Behavior

Expected The GUI to appear.

❌ Actual Behavior

PowerToys remains in the system tray. GUI doesn't appear.

Other Software

PowerToysReport_2022-05-20-20-33-25.zip

crazy4ever
crazy4ever

Same here, unable to open 0.58.0, restarting pc/closing powertoys with taskmanager and restarting doesn't work.

PowerToysReport_2022-05-20-21-32-29.zip

Activity icon
issue

DizWARE issue comment microsoft/PowerToys

DizWARE
DizWARE

FancyZones uses Layout of main Display on all Monitors.

Microsoft PowerToys version

0..58.0

Running as admin

  • Yes

Area(s) with issue?

FancyZones

Steps to reproduce

No Matter what Layouts i chose, all my 3 Monitos get the Layout of the primary Display. Worked fine till 0.58.0

✔️ Expected Behavior

Keep own Layout for each Display.

❌ Actual Behavior

All Display get Layout of primary Display.

Other Software

No response

DizWARE
DizWARE

I also have the same issue. 3 monitors, different sizes, one of them portrait and I am using remote desktop; I personally couldn't even get fancy zones to activate when pressing shift, both mouse keys, or using Windows + arrows. It was also refusing to set my custom layouts on the different monitors. It would set my left monitor to None, and the other two monitors to Priority Grid, and wouldn't persist any changes I would make to each of the monitors; Just bounce back to those settings.

Following @danielsamuels suggestion of selecting "Allow zones to span across monitors" reenabled the ability to use Fancy zones but the interaction was so broken across my 3 screens, it just wasn't a feasible solution to work with.

I've uninstalled 0.58.0 and installed 0.57.2, which has fixed my fancy zones interactions completely. I can share a bug report, but I'd have to reinstall the version, so I guess if you need that let me know.

Activity icon
issue

Theo-user issue comment microsoft/PowerToys

Theo-user
Theo-user

Update to version 0.58.0 failure and error.

Microsoft PowerToys version

Version 0.57.0

Running as admin

  • Yes

Area(s) with issue?

General, Installer

Steps to reproduce

Click on "try again to download and install" and then the bug appears. image The progress bar goes almost halfway through, then just completely stops, and the window closes after a second.

✔️ Expected Behavior

Update and installation of update v0.58.0

❌ Actual Behavior

Failed to update and install update v0.58.0

Other Software

No response

Theo-user
Theo-user

Could you try downloading and installing WinAppSDK manually: https://aka.ms/windowsappsdk/1.0/1.0.3/windowsappruntimeinstall-1.0.3-x64.exe

Try running this exe from elevated command prompt and see if some error is returned. /needinfo

Installing license: WAR_MAINPACKAGE_LICENSE Install result : 0x0 Deploying package: Microsoft.WindowsAppRuntime.1.0_3.469.1654.0_x64__8wekyb3d8bbwe Package deployment result : 0x0 Deploying package: Microsoft.WindowsAppRuntime.1.0_3.469.1654.0_x86__8wekyb3d8bbwe Package deployment result : 0x0 Deploying package: MicrosoftCorporationII.WindowsAppRuntime.Main.1.0_3.469.1654.0_x64__8wekyb3d8bbwe Package deployment result : 0x80073d0a The package could not be installed because the Windows Firewall service is not running. Enable the Windows Firewall service and try again. One or more install operations failed. Result: 0x80073d0a

[process exited with code 2147958026]

Activity icon
issue

noga-dev issue comment microsoft/PowerToys

noga-dev
noga-dev

App runs in system tray, but not opening

Microsoft PowerToys version

0.58.0

Running as admin

  • Yes

Area(s) with issue?

General, System tray interaction

Steps to reproduce

Installed. Set to run as admin. Worked fine until rebooted. Since then won't open. Reinstalled. Still won't open.

✔️ Expected Behavior

Expected The GUI to appear.

❌ Actual Behavior

PowerToys remains in the system tray. GUI doesn't appear.

Other Software

PowerToysReport_2022-05-20-20-33-25.zip

noga-dev
noga-dev
Fault bucket 1529761800786741046, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: PowerToys.Settings.exe
P2: 0.58.0.0
P3: 622f78e0
P4: Microsoft.WindowsAppRuntime.Bootstrap.dll
P5: 0.0.0.0
P6: 622fc69c
P7: 000000000000124d
P8: c0000409
P9: 0000000000000007
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.eb06391c-17c6-40cd-94ec-8146c50c2659.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.373c3743-0eb5-4e40-a40e-a24cf522613c.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e44f24ed-b604-4f01-9979-197c1546e5f5.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.8d2a772e-a3e2-4ff5-8ca6-87551580ffac.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9673cccf-11c0-4f0a-88fa-84a31c6d9ba1.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_PowerToys.Settin_cb47c1da40953d6ad37afff39f83ff4c215c5bb4_d6b46307_f1c4ab4d-e7df-4d43-aadd-b999bf6b7307

Analysis symbol: 
Rechecking for solution: 0
Report Id: d31fd648-a2b7-4e78-a876-3fb0a114ae71
Report Status: 268435456
Hashed bucket: fbf3700a1bed9b64f53ace40b6db0736
Cab Guid: 0

(Can't upload report because github complains about unsupported file type.)

Contents of the report.wer file:

Version=1
EventType=BEX64
EventTime=132975432586187845
ReportType=2
Consent=1
UploadTime=132975432590167782
ReportStatus=268435456
ReportIdentifier=f1c4ab4d-e7df-4d43-aadd-b999bf6b7307
IntegratorReportIdentifier=d31fd648-a2b7-4e78-a876-3fb0a114ae71
Wow64Host=34404
NsAppName=PowerToys.Settings.exe
OriginalFilename=PowerToys.Settings.dll
AppSessionGuid=00002170-0001-0035-1b24-ca8e736cd801
TargetAppId=W:0000ea295907bb6b837a346993818e72abff00000904!00008d6e33505c4fc70560e1f73f136d592969d6059c!PowerToys.Settings.exe
TargetAppVer=2022//03//14:17:18:24!42332!PowerToys.Settings.exe
BootId=4294967295
ServiceSplit=472371977
TargetAsId=5649
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=fbf3700a1bed9b64f53ace40b6db0736
Response.BucketTable=5
Response.LegacyBucketId=1529761800786741046
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=PowerToys.Settings.exe
Sig[1].Name=Application Version
Sig[1].Value=0.58.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=622f78e0
Sig[3].Name=Fault Module Name
Sig[3].Value=Microsoft.WindowsAppRuntime.Bootstrap.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=622fc69c
Sig[6].Name=Exception Offset
Sig[6].Value=000000000000124d
Sig[7].Name=Exception Code
Sig[7].Value=c0000409
Sig[8].Name=Exception Data
Sig[8].Value=0000000000000007
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.22000.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=3bcc
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=3bccbf06853e4e91c33159fd25838a83
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=1644
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=16442038636bf0c8aa9671c9d6b71bf8
UI[2]=C:\Program Files\PowerToys\Settings\PowerToys.Settings.exe
LoadedModule[0]=C:\Program Files\PowerToys\Settings\PowerToys.Settings.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\System32\KERNEL32.DLL
LoadedModule[3]=C:\Windows\System32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\System32\USER32.dll
LoadedModule[5]=C:\Windows\System32\win32u.dll
LoadedModule[6]=C:\Windows\System32\GDI32.dll
LoadedModule[7]=C:\Windows\System32\gdi32full.dll
LoadedModule[8]=C:\Windows\System32\msvcp_win.dll
LoadedModule[9]=C:\Windows\System32\ucrtbase.dll
LoadedModule[10]=C:\Windows\System32\SHELL32.dll
LoadedModule[11]=C:\Windows\System32\ADVAPI32.dll
LoadedModule[12]=C:\Windows\System32\msvcrt.dll
LoadedModule[13]=C:\Windows\System32\sechost.dll
LoadedModule[14]=C:\Windows\System32\RPCRT4.dll
LoadedModule[15]=C:\Windows\System32\IMM32.DLL
LoadedModule[16]=C:\Program Files\dotnet\host\fxr\6.0.5\hostfxr.dll
LoadedModule[17]=C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.5\hostpolicy.dll
LoadedModule[18]=C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.5\coreclr.dll
LoadedModule[19]=C:\Windows\System32\ole32.dll
LoadedModule[20]=C:\Windows\System32\combase.dll
LoadedModule[21]=C:\Windows\System32\OLEAUT32.dll
LoadedModule[22]=C:\Windows\System32\bcryptPrimitives.dll
LoadedModule[23]=C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.5\System.Private.CoreLib.dll
LoadedModule[24]=C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.5\clrjit.dll
LoadedModule[25]=C:\Windows\SYSTEM32\kernel.appcore.dll
LoadedModule[26]=C:\Program Files\PowerToys\Settings\PowerToys.Settings.dll
LoadedModule[27]=C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.5\System.Runtime.dll
LoadedModule[28]=C:\Windows\system32\uxtheme.dll
LoadedModule[29]=C:\Program Files\PowerToys\Settings\Microsoft.WindowsAppRuntime.Bootstrap.Net.dll
LoadedModule[30]=C:\Program Files\PowerToys\Settings\Microsoft.WindowsAppRuntime.Bootstrap.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=22000
OsInfo[3].Key=ubr
OsInfo[3].Value=675
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=117
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=221622967
OsInfo[15].Key=osinsty
OsInfo[15].Value=2
OsInfo[16].Key=iever
OsInfo[16].Value=11.1.22000.0-11.0.1000
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=32173
OsInfo[19].Key=svolsz
OsInfo[19].Value=953
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=210604
OsInfo[22].Key=bldtm
OsInfo[22].Value=1628
OsInfo[23].Key=bldbrch
OsInfo[23].Value=co_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.22000.675.amd64fre.co_release.210604-1628
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[33].Value=FX:11C6E5C2,FX:11CC111C,FX:11DF5B12,FX:11DF5B75
OsInfo[34].Key=fconid
OsInfo[34].Value=18299130,0,2,0;23531064,2,2,0;23562335,2,2,1;23563673,2,2,1;24172318,0,2,1;25704915,1,2,1;27336672,0,1,1;35825666,0,1,1;37801696,0,1,1;37926348,0,1,0
OsInfo[35].Key=containerid
OsInfo[36].Key=containertype
OsInfo[37].Key=edu
OsInfo[37].Value=0
OsInfo[38].Key=servicinginprogress
OsInfo[38].Value=0
FriendlyEventName=Stopped working
ConsentKey=BEX64
AppName=PowerToys.Settings
AppPath=C:\Program Files\PowerToys\Settings\PowerToys.Settings.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=632894B4D225B5D550E8EE15E6867BA2
MetadataHash=800293027
Previous