This worked for me. Other solutions I tried, including other Power Shell suggestions did not. If you use this, give it time, It will run for several minutes. You will know it is finished when you are presented with the command line prompt C:\WINDOWS\system32>
"You'll need a new app to open this windowsdefender link" fix
Hi this post is to help people with windows 10 and 11 windows security not working
On windows 11 do this
- launch powershell as an admin
- Set-ExecutionPolicy Unrestricted
- Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
- Set-ExecutionPolicy restricted
IGNORE THE ERRORS
on windows 10 do this
- launch powershell as an admin}
- run get-AppxPackage Microsoft.SecHealthUI -AllUsers | Reset-AppxPackage
- if it doesn't work do this
4) run Add-AppxPackage -Register -DisableDevelopmentMode "C:\Windows\SystemApps\Microsoft.Windows.SecHealthUI_cw5n1h2txyewy\AppXManifest.xml" - run get-AppxPackage Microsoft.SecHealthUI -AllUsers | Reset-AppxPackage
Windows for home | Windows 11 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
98 answers
Sort by: Oldest
-
Anonymous
2022-04-02T11:42:25+00:00 -
Anonymous
2022-04-10T17:43:25+00:00 Windows 11 step 3 get significant number of errors that include both
"because this package depends on a framework that could not be found.
and
"could not be installed because resources it modifies are currently in use"
Windows security and microsoft store both fail to run
-
Anonymous
2022-04-12T09:25:27+00:00 Thanks it works fine!
-
Anonymous
2022-04-12T12:47:51+00:00 Thank you! Your solution for Windows 11 solved the problem for me.
-
Anonymous
2022-04-16T13:53:53+00:00 I had this same problem. Admin account and standard account on the PC - logged in as standard user, running powershell as admin. The above instructions did not work. No change.
I turned my standard user account into an admin (computer management, users & groups, users, user account's properties, "member of" tab, added Administrators). Restarted and reran the above instructions while logged in as that user who is now an admin. That worked.
I haven't removed the user from the admin group yet, but I'm hoping the fix will continue to work.