Recently I upgraded my Windows to version 2004. After the update, Explorer.exe would restart repeatedly when I started my PC. In my task manager, I discovered wsappx was consuming a lot of CPU. I ended its task and everything returned to normal. However, this issue still occurs every time I turn on my computer, and I’m unsure why it’s happening. It appears wsappx is related to the Windows Store, but I don’t understand its purpose. If anyone knows what might be causing this or how to resolve it, please let me know. Thank you.
I encountered the same problem this morning. The issue seems linked to faulty Windows Store app data, as mentioned in the discussion: https://answers.microsoft.com/en-us/wind...cbd?page=4 You can resolve it by setting up a new user profile or by deleting and reinstalling all store applications as outlined: Run powershell as administrator Export a list of your currently installed apps and then uninstall them Get-AppxPackage -User {{Affected_user_name}} > $env:SystemDrive\temp\apps-removed.log Get-AppxPackage -User {{Affected_user_name}} | Remove-AppxPackage Perform a system repair (optional) sfc /scannow dism /online /cleanup-image /restorehealth Create another administrator user and log in as that user Rename the affected packages folder. (Windows will rebuild the bair minimum on the next login) Rename-Item $env:SystemDrive\Users\{{Affected_user_name}}\AppData\Local\Packages $env:SystemDrive\Users\{{Affected_user_name}}\AppData\Local\Packages.old Log in as your original user again Reinstall the provisioned apps Get-AppxProvisionedPackage -Online | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)"}
The error occurs because you're trying to evaluate a parameter named 'User' that isn't properly defined or passed in the script block. Ensure the variable is correctly declared and included before using it. Adjust the syntax so the script block receives the expected input.