Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Settings Screen is blank #243

Closed
MrIncUK opened this issue Sep 6, 2019 · 236 comments
Closed

Settings Screen is blank #243

MrIncUK opened this issue Sep 6, 2019 · 236 comments
Assignees
Labels
Issue-Bug Something isn't working Product-Settings The standalone PowerToys Settings application Resolution-Fix Committed Fix is checked in, but it might be 3-4 weeks until a release.
Milestone

Comments

@MrIncUK
Copy link

MrIncUK commented Sep 6, 2019

Environment

W10 Pro V1903 Build 18362.295
PowerToys: 0.11.0
Settings Screen

Windows build number: [run "ver" at a command prompt]
PowerToys version: 
PowerToy module for which you are reporting the bug (if applicable):

Steps to reproduce

Just installed and attempted to open settings. Screen is totally blank/empty.
I 'repaired - same issue.
Uninstalled, reboot and reinstall - same issue.

Expected behavior

Expect to see config options

Actual behavior

Blank window.

Screenshots

https://i.imgur.com/a7oWKgp.png

@enricogior enricogior added Product-Settings The standalone PowerToys Settings application Issue-Bug Something isn't working labels Sep 6, 2019
@enricogior
Copy link
Contributor

Hi @MrIncUK
thank you for reporting the issue, I'll follow-up ASAP.

@enricogior
Copy link
Contributor

@MrIncUK, @rkent57, @tjdraper, @Syuein
thanks again for reporting the issue, hopefully we will find what it's causing it.

It may be caused by the way PowerToys runs when executed with elevated privileges.
If the user belongs to the Administrator group, PowerToys asks the user to be granted permission to run with elevated privileges (in order to interact with other windows that may also be running with elevated privileges), but the Settings window (that is executed in a different binary) has to run without elevated privileges. If it happens that the Settings is also running with elevated privileges, it will show a blank screen.

It would help to know in your case how do you run PowerToys:

  • the Windows account you are using has admin privileges?
  • if you quit and run again PowerToys, does it prompt the UAC dialog?
    UAC

Let's start from here to see if there is a common ground for this bug.

@MrIncUK
Copy link
Author

MrIncUK commented Sep 6, 2019

Yes, my account is in the Administrators group.
Yes, I get the UAC dialog.

HTH!

@enricogior
Copy link
Contributor

OK, so now can you please:

  • open the Task Manager
  • go to the Details tab
  • right click on a column title (a popup menu appears)
  • open Select columns
  • scroll towards the bottom searching for Elevated, select it and close the dialog

now in the Task Manager you should see in the Elevated column if PowerToysSettings.exe is running with elevated privileges or not:

taskmanager

@MrIncUK
Copy link
Author

MrIncUK commented Sep 6, 2019

It is set to 'Not Allowed'

https://i.imgur.com/hZlzFfs.png

FYI, FYI, I logged in under another 'Standard' user account on the same PC, and the Settings screen opened/displayed OK.

@eagleEggs
Copy link

eagleEggs commented Sep 6, 2019

Also seeing 'Not allowed.' And also verified standard user can see the settings fine.
Elevated is 'Yes' for both.

10.0.17763 Build 17763

@enricogior
Copy link
Contributor

@MrIncUK
Not Allowed is in the UAC Virtualization column, but I see Yes that I suppose is the value for the Elevated column, if that is the case there is something wrong since PowerToysSettings.exe is not supposed to run elevated.
Do you run the regular Windows Explorer or do you run a third party Windows shell/desktop?

@enricogior
Copy link
Contributor

@eagleEggs
same question that I asked to @MrIncUK: do you run the regular Windows Explorer or do you run a third party Windows shell/desktop?

@MrIncUK
Copy link
Author

MrIncUK commented Sep 6, 2019

I run Classic Shell and Stardock Fences.

@enricogior
Copy link
Contributor

I assume Classic Shell runs elevated and because of that PowerToysSettings.exe also runs elevated.
We will have to fix our code to support this scenario.
Thanks for your help tracking this down, really appreciated!

@MrIncUK
Copy link
Author

MrIncUK commented Sep 6, 2019

No problem.

FYI, I exited Classic shell, uninstalled Powertoys, reinstalled, and I get the same problem. Not sure if that helps or not!

@eagleEggs
Copy link

eagleEggs commented Sep 6, 2019

@enricogior I do not run custom shells. It's vanilla. I do have some group policies applied that perhaps is affecting the way the process is being handled?

Not sure how far you want to support that kind of setup (Enterprise policies and such). But I know there are some policies regarding Administrative token handling that perhaps your code isn't working well with. I'll release the policies and see if that clears it up. If so, I'd be happy to share them with you if you do decide. We'll see...

@enricogior
Copy link
Contributor

@MrIncUK it may be that you actually need to uninstall Classic Shell and not just quit, but it's a wild guess, I have to test it.

@eagleEggs can you please check in TaskManager the Elevated column, it can have only two values Yes or No, the 'Not allowed value is for the UAC Virtualization column. Thank you.

@eagleEggs
Copy link

Oh yes I updated the comment, Elevated is 'Yes' for both, and 'Not Allowed' for both.

@enricogior
Copy link
Contributor

@eagleEggs OK thanks.
Since we cannot create a credential token from scratch, we ask the shell that started PowerToys.exe to get a valid token to be used for PowerToysSettings.exe, in your case we get an elevated token and the consequence is the blank screen.
We will have to find a workaround for these scenarios where we get an elevated token.
In your specific case, as you said, there might be some particular policy that is causing the problem.

@rkent57
Copy link

rkent57 commented Sep 6, 2019

See my screen shots...I do NOT run any special privelages but I DO have UAC disabled...hate the damn thing...annoying...I am the admin but only use the rights for special instances. I use the normal explorer also.

PT DropMenu
PowerTools

@MrIncUK
Copy link
Author

MrIncUK commented Sep 6, 2019

@MrIncUK
Not Allowed is in the UAC Virtualization column, but I see Yes that I suppose is the value for the Elevated column, if that is the case there is something wrong since PowerToysSettings.exe is not supposed to run elevated.
Do you run the regular Windows Explorer or do you run a third party Windows shell/desktop?

Just realised that I looked at PowerToys.exe and gave a screenshot of that line - it doesn't show the settings one. So just opened the blank settings and got the screenshot of PowerToolSettings.exe

https://i.imgur.com/0wSM80c.png

Shows it's not running elevated. Not sure if that makes any difference or not. Needed to mention it though!

@ghost
Copy link

ghost commented Sep 7, 2019

Having the same issue both powertoys.exe and powertoyssettings.exe aren't running elevated, but settings screen is blank.
image

@tjsuominen
Copy link

+1 so here too. I'm running Classic Start as Windows shell.

@MikeMeeseeks
Copy link

Microsoft Windows [Version 10.0.18362.295]
PowerToys: 0.11.0
Settings Screen

+1 as well, vanilla install.
PowerToys.exe running as elevated but UAC virtualization disabled.

Also disabled antivirus (Vipre Endpoint) to test, no avail.

I'm leaning more towards GP causing this as our company uses quite a lot.

@vbarrancos
Copy link

I'm experiencing the same thing. PowerToys.exe is running elevated, and PowerToysSettings.exe is not elevated. I haven't set any group policies, nor am I using any shell/start menu/explorer replacement. This is a vanilla install on my personal PC, so there shouldn't be any enterprise config affecting things. My user account is a member of the administrators group.

image

@eagleEggs
Copy link

@vbarrancos what version of Windows are you on? Interesting that your Settings is not elevated but mine does - While we see the same issue.

image

@p3trus
Copy link

p3trus commented Sep 10, 2019

Hi, I observe the same issue as @eagleEggs : Blank Settings Page.

Both PowerToysSettings.exe and PowerToys.exe run elevated. UAC not allowed

@jcbcn
Copy link

jcbcn commented Sep 10, 2019

I was having the same issue. This is definately linked to having UAC turned off (in my case from a debloat win10 script). I went to the UAC settings and reapplied the "Never notify" setting and then restarted. The settings window now works correctly.

@sethretig
Copy link

sethretig commented Sep 10, 2019 via email

@enricogior
Copy link
Contributor

enricogior commented Sep 10, 2019

Thanks for all the reports, please keep updating the issue if you find a workaround for your specific case, like reapplying the UAC settings if you had it turned off.

There are different scenarios where this bug shows up, I would like to understand if anyone is experiencing the blank screen when:

  • you are using the default UAC settings (you see the UAC screen when starting PowerToys manually)
  • PowerToys.exe runs Elevated "Yes" and PowerToysSetting.exe runs Elevated "No"

Thanks.

@jberent
Copy link

jberent commented May 19, 2020

fresh 0.18 install on vanilla 1909 18363.836, contents of settings briefly visible, but then empties (side menu, then "General" label). UAC disabled and not Elevated for both processes. Any work arounds, or previous version?? (Text is white-on-black, before it disappears -- dark-mode?)

@crutkas
Copy link
Member

crutkas commented May 19, 2020

@BeecherNetworks the fix requires 1903 until WinUI 3 is in a state we can adopt it to downlevel to 1803

@jberent
Copy link

jberent commented May 19, 2020

(SOLVED?) 0.18 settings seems to work fine if RunAsAdministrator -- sorry if this was documented somewhere. I know there are options in "Settings", but, ahem...

@crutkas
Copy link
Member

crutkas commented May 19, 2020

@jberent shouldn't need to run as admin, can you send a screenshot?

@jberent
Copy link

jberent commented May 19, 2020

RunAsAdmin: (normal)
image

and when just run normal:
image
(text is briefly visible)

P.S. If I can blindly find the [restart as admin] and click it, then settings works again.

@crutkas
Copy link
Member

crutkas commented May 19, 2020

@jberent, lets roll this into a new issue. @laviusmotileng-ms for vis here.

@catherdersoftware
Copy link

Resolved for me. Many thanks for all your hard work!

@enricogior
Copy link
Contributor

0.18 introduces a new Settings app that resolves the problem on Windows 10 version 1903 and later https://github.com/microsoft/PowerToys/releases

@Githubber616
Copy link

@Githubber616 what version of Windows are you running? The new Settings apps requires Windows 10 1903 or later.

That might be the issue 1809 I don't intent to change that. ... well maybe I upgrade to 1903 if I ever find out how (cause 1903 is finally fairly stable by now ... I would run the latest if MS would not regularly fork it up)

@roncerr
Copy link

roncerr commented May 24, 2020

RE: "0.18 introduces a new Settings app that resolves the problem on Windows 10 version 1903 and later https://github.com/microsoft/PowerToys/releases"
I installed the latest version, rebooted, opened the settings window from the tray. Settings window is blank. Also I don't see any menu or listing of any Powertoys. Running 1909 Home as admin. UAC set to "don't notify".

@jthoward64
Copy link
Contributor

RE: "0.18 introduces a new Settings app that resolves the problem on Windows 10 version 1903 and later https://github.com/microsoft/PowerToys/releases"
I installed the latest version, rebooted, opened the settings window from the tray. Settings window is blank. Also I don't see any menu or listing of any Powertoys. Running 1909 Home as admin. UAC set to "don't notify".

If that’s the case then I would open a new ticket as this one is tied to problems with the old web view.

@BeecherNetworks
Copy link

@BeecherNetworks the fix requires 1903 until WinUI 3 is in a state we can adopt it to downlevel to 1803

I meant to ask, is there a timeline for this? I won't be upgrading Windows any time soon. Thanks.

@riverar
Copy link
Contributor

riverar commented Jun 16, 2020

@BeecherNetworks 1803 is EOL for consumers and soon EOL for enterprise (November 10, 2020), so, you may want to consider upgrading soon as PowerToys will drop support.

@crutkas
Copy link
Member

crutkas commented Jun 16, 2020

for WinUI3, hopefully by 2020 Q4. They need to be have a few more things ironed out before we take a dependency

@riverar
Copy link
Contributor

riverar commented Jun 17, 2020

@crutkas By 2020 Q4, there will be zero support for 1803 and this issue be moot.

@crutkas
Copy link
Member

crutkas commented Jun 17, 2020

@crutkas By 2020 Q4, there will be zero support for 1803 and this issue be moot.

still need 1809 support :)

@BeecherNetworks
Copy link

@BeecherNetworks 1803 is EOL for consumers and soon EOL for enterprise (November 10, 2020), so, you may want to consider upgrading soon as PowerToys will drop support.

I'm on LTSC / 1809, dunno where 1803 came from.

@bitemarcz
Copy link

Was there ever a fix to this? Still seeing the failed to create webview control. I am on Windows Build 17763.1282

@jthoward64
Copy link
Contributor

jthoward64 commented Jul 7, 2020

Was there ever a fix to this? Still seeing the failed to create webview control. I am on Windows Build 17763.1282

As far as I'm aware 0.18 fixes this on windows 10 version 1903 and above, I think that build is 1809, which is not supported by the new settings menu.

@crutkas stated

the fix requires 1903 until WinUI 3 is in a state we can adopt it to downlevel to 1803

@bitemarcz
Copy link

@tajetaje Thank you! Sounds like I will need to ask the endpoint team to push an update out to my computer.

@BeecherNetworks
Copy link

Is this a WONTFIX or will it come eventually I wonder?

@jthoward64
Copy link
Contributor

jthoward64 commented Sep 30, 2020

Is this a WONTFIX or will it come eventually I wonder?

@BeecherNetworks The issue has been fixed for 1903+. If you are asking if it will be backported: so far the latest is that it will, but only after WinUI 3 is in the proper condition.

See my previous comment:

Was there ever a fix to this? Still seeing the failed to create webview control. I am on Windows Build 17763.1282

As far as I'm aware 0.18 fixes this on windows 10 version 1903 and above, I think that build is 1809, which is not supported by the new settings menu.

@crutkas stated

the fix requires 1903 until WinUI 3 is in a state we can adopt it to downlevel to 1803

@BeecherNetworks
Copy link

Sorry, I should have specified again, I'm on LTSC which is 1809. I don't know anything about WinUI 3, is there any kind of timeline for that?

@jthoward64
Copy link
Contributor

Sorry, I should have specified again, I'm on LTSC which is 1809. I don't know anything about WinUI 3, is there any kind of timeline for that?

@BeecherNetworks Yes, take a look at that link. It is the roadmap and current timeline for WinUI 3.

@BeecherNetworks
Copy link

Yes, I was just hoping for something a little better than "2021". Ah well, I'm flying blind this long, I guess another 2-14 months won't kill me. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug Something isn't working Product-Settings The standalone PowerToys Settings application Resolution-Fix Committed Fix is checked in, but it might be 3-4 weeks until a release.
Projects
No open projects
0.18 release
  
Done
Development

No branches or pull requests