microsoft / PowerToys

Windows system utilities to maximize productivity
MIT License
111.6k stars 6.57k forks source link

PowerToys control panel does not save any settings #35178

Open zyjj217 opened 1 month ago

zyjj217 commented 1 month ago

Microsoft PowerToys version

0.84.1

Installation method

GitHub

Running as admin

Yes

Area(s) with issue?

FancyZones

Steps to reproduce

It just says access denied. Same thing after running as admin.

✔️ Expected Behavior

Settings to save

❌ Actual Behavior

No setting seems to be saving, not just fancyzones, everything was not saving, had to edit the json file manually and it works.

Other Software

No response

jaimecbernardo commented 1 month ago

Hi, are you by any chance running PowerToys as admin with a different user? Anyway, the files having access denied is weird. It the file hidden or read-only by any chance? /needinfo

zyjj217 commented 1 month ago

Hi, are you by any chance running PowerToys as admin with a different user? Anyway, the files having access denied is weird. It the file hidden or read-only by any chance? /needinfo

Hello Sry for the late reply I did not have github notifications. I've tried running powertoys as user and as admin nothing seems to change. I have only one user for this windows, it's a personal device. Settings are located in the appdata file under users/myusername, and I went to check and found out my entire user directory does seem to be hidden. Is this normal for windows 11? Is that the cause of the issue? and yes the applied-layouts file is hidden as well.

This is not just a fancyzones issue, none of the settings in powertoys are saving at all, so I have been manually editing the json files to make changes. I just checked, all of these files seem to be hidden.

zyjj217 commented 1 month ago

So I found out that if I unhide these settings files the settings do save properly, so does the window placement of powertoys control panel itself (that didn't remember either earlier), are these files supposed to be hidden by default or caused by a bug? Because that's what was causing my access issue