Windows 10 Persistent Gray Overlay in Windows Metro After NVIDIA Driver Update: Need Help

Bear

Well-Known Member
Joined
Sep 29, 2016
Messages
128
Ok, idk what in the world is going on but suddenly yesterday or day before the entire metro thing looks weird..
it's like there is a gray skin cast over the area.. It started about the same time as the faulty nvidia driver update.
the tiles got stuck flashing and then I restarted and that problem went away but had other issues with programs.. upgraded nvidia again last night.. other issues fixed but not this.
Any clue?
 
Last edited by a moderator:
Solution
You can try the following. I'd recommend running the following code as a script because the first two commands need to run pretty quick together
First open a elevated powershell prompt and type Set-ExecutionPolicy -Scope LocalMachine this will allow scripts to be run.

Copy the following code into a file and name it whatever.ps1
Code: 
Stop-Process -Name "ShellExperienceHost"
Rename-Item "$($env:USERPROFILE)\Appdata\local\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy" "$($env:USERPROFILE)\Appdata\local\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy.old"
Add-AppxPackage -Path "C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\AppxManifest.xml" -Register -DisableDevelopmentMode

Then run it from the...
Sort by date Sort by votes
Hi

That looks like it's applying transparency to one of the layers and showing what's behind it.
Have you messed around with the color setting to see if it changes, maybe try a different theme and then switch back etc.

See of there's someplace to switch off transparency.

Mike

There is a place to turn transparency on and off under "Colors", see if that helps.
 
Last edited:
Upvote 0 Downvote
I have seen the flashing titles before, but not the hazy look. The start menu is handled by the ShellExperieceHost.exe process. You can try killing this process and see if that temporarily resolves the issue. It should automatically respawn.
 
Upvote 0 Downvote
Hmm I think I have discovered how to fix broken start menus in the process, I will write up a tutorial for it tonight.
 
Upvote 0 Downvote
yeah, didn't help.. was strange is change just happened... if you notice all the icons have heavy overlay
 
Upvote 0 Downvote
You can try the following. I'd recommend running the following code as a script because the first two commands need to run pretty quick together
First open a elevated powershell prompt and type Set-ExecutionPolicy -Scope LocalMachine this will allow scripts to be run.

Copy the following code into a file and name it whatever.ps1
Code: 
Stop-Process -Name "ShellExperienceHost"
Rename-Item "$($env:USERPROFILE)\Appdata\local\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy" "$($env:USERPROFILE)\Appdata\local\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy.old"
Add-AppxPackage -Path "C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\AppxManifest.xml" -Register -DisableDevelopmentMode

Then run it from the elevated powershell prompt C:\...pathtpwhatever.sp1

This should reset the Start Menu
 
Upvote 0 Downvote
Solution
Code: 
Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32> Set-ExecutionPolicy -Scope LocalMachine

cmdlet Set-ExecutionPolicy at command pipeline position 1
Supply values for the following parameters:
ExecutionPolicy:
Set-ExecutionPolicy : Cannot bind parameter 'ExecutionPolicy'. Cannot convert value "" to type
"Microsoft.PowerShell.ExecutionPolicy". Error: "The identifier name  cannot be processed because it is either too
similar or identical to the following enumerator names: Unrestricted, RemoteSigned, AllSigned, Restricted, Default,
Bypass, Undefined. Use a more specific identifier name."
At line:1 char:1
+ Set-ExecutionPolicy -Scope LocalMachine
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Set-ExecutionPolicy], ParameterBindingException
    + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.SetExecutionPolicyCommand

PS C:\WINDOWS\system32> Set-ExecutionPolicy -Scope LocalMachine

cmdlet Set-ExecutionPolicy at command pipeline position 1
Supply values for the following parameters:
ExecutionPolicy: c:\reset-startmenu.ps1
Set-ExecutionPolicy : Cannot bind parameter 'ExecutionPolicy'. Cannot convert value "c:\reset-startmenu.ps1" to type
"Microsoft.PowerShell.ExecutionPolicy". Error: "Unable to match the identifier name c:\reset-startmenu.ps1 to a valid
enumerator name. Specify one of the following enumerator names and try again:
Unrestricted, RemoteSigned, AllSigned, Restricted, Default, Bypass, Undefined"
At line:1 char:1
+ Set-ExecutionPolicy -Scope LocalMachine
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Set-ExecutionPolicy], ParameterBindingException
    + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.SetExecutionPolicyCommand

PS C:\WINDOWS\system32> Set-ExecutionPolicy -Scope LocalMachine
it was asking for a policy..
 
Upvote 0 Downvote
wait, actually even though it errored, it fixed it.. when I entered the first command it asked if I wanted to allow for all or what.. I chose all, do I need to change that now that its fixed?
 
Last edited by a moderator:
Upvote 0 Downvote
The shell experience process probably still had a handle to the folder and that is why it errored. I think just re-registering the process resolved it which works.
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

  • Article Article
Troubleshooting Print Screen Overlay in Windows: Snipping Tool Issues
Replies
0
Views
23
ChatGPT
S
  • Solved
Windows 7 Missing Programs in Accessories Menu After Windows 7 Beta Update: Need Help!
Replies
2
Views
4K
reghakr