Command Excuting error? (Windows 10)

[Kate-alt-69]

Checklist

• I have searched for existing issues/discussions and didn't find any similar ones.
• I haven't used any other scripts, tools or programs that might have caused this issue.

Windows version

Windows 10 HSL 22H2 Installed on 26-‎09-‎2025 OS Build 19045.7417

Script mode/options

custom mode

Describe the issue

                         ^
                        / \
                       /   \
                      /     \
                     / ===== \
                     |  ---  |
                     | ( O ) |
                     |  ---  |
                     |       |
                    /|       |\
                   / |       | \
                     |  '''  |    *
                       (''')    *  *
                       ( ' )   *

             Win11Debloat is launching...
                Keep this window open


Retrieving installed apps via winget...
<ERROR#2>
<ERROR#2>
Selected user mode: current user (Merge)
> Creating registry backup...
Backup successfully created: C:\Users\Merge\Downloads\Win11Debloat-master\Backups\Win11Debloat-RegistryBackup-20260625_223942.json

> Creating a system restore point...
Error: Unable to retrieve existing restore points: The term 'Get-ComputerRestorePoint' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Warning: Continuing without restore point

> Removing selected apps for all users...
9 apps selected for removal
Removing Microsoft.OutlookForWindows
<ERROR#1>
Removing Microsoft.MSPaint
<ERROR#1>
Removing Microsoft.YourPhone
<ERROR#1>
Removing Microsoft.Windows.Photos
<ERROR#1>
Removing Microsoft.SkypeApp
<ERROR#1>
Removing Microsoft.WindowsSoundRecorder
<ERROR#1>
Removing Microsoft.WindowsMaps
<ERROR#1>
Removing Microsoft.XboxApp
<ERROR#1>
Removing Microsoft.XboxSpeechToTextOverlay
<ERROR#1>
> Disabling telemetry and diagnostic data collection...
The operation completed successfully.

> Disabling telemetry scheduled tasks...

> Disabling tips & tricks on the lock screen...
The operation completed successfully.

> Preventing automatic restarts after updates while signed in...
The operation completed successfully.

> Hiding the chat icon from the taskbar...
The operation completed successfully.

> Enabling file extensions for known file types...
The operation completed successfully.

> Disabling the 'Windows Spotlight' desktop background option...
The operation completed successfully.

> Hiding the '3D objects' folder from the File Explorer navigation pane...
The operation completed successfully.

> Disabling Find My Device location tracking...
The operation completed successfully.

> Hiding 'Share' in the context menu...
The operation completed successfully.

> Disabling Windows location services and app location access...
The operation completed successfully.

> Hiding 'Include in library' in the context menu...
The operation completed successfully.

> Enabling dark mode for system and apps...
The operation completed successfully.

> Disabling transparency effects...
The operation completed successfully.

> Unhiding hidden files, folders and drives...
The operation completed successfully.

> Turning off Enhanced Pointer Precision...
The operation completed successfully.

> Disabling Bing web search & Copilot integration in Windows search...
The operation completed successfully.

Removing Microsoft.BingSearch
Write-Error: C:\Users\Merge\Downloads\Win11Debloat-master\Scripts\AppRemoval\RemoveApps.ps1:198

> Hiding the 'OneDrive' section from the File Explorer navigation pane...
The operation completed successfully.

> Disabling widgets on the taskbar & lock screen...
Removing Microsoft.StartExperiencesApp
Write-Error: C:\Users\Merge\Downloads\Win11Debloat-master\Scripts\AppRemoval\RemoveApps.ps1:198

Write-Error: C:\Users\Merge\Downloads\Win11Debloat-master\Scripts\AppRemoval\RemoveApps.ps1:198

Write-Error: C:\Users\Merge\Downloads\Win11Debloat-master\Scripts\AppRemoval\RemoveApps.ps1:198

All changes have been applied successfully!
Transcript stopped, output file is C:\Users\Merge\Downloads\Win11Debloat-master\Logs\Win11Debloat.log
PS C:\Users\Merge\Downloads\Win11Debloat-master>

Steps to reproduce

1. open script (i used PWS7 Admin)
2. custom mode (i used CM and continued )
3. errors in terminal

Error output

Command errors while doing tasks in the background PWS7 while retreving data and also while uninstalling stuff with the same error

Additional context

ERROR#2

Write-Error: C:\Users\Merge\Downloads\Win11Debloat-master\Scripts\GUI\MainWindow-AppSelection.ps1:333
Line |
 333 |          $rawAppData = Invoke-NonBlocking -ScriptBlock {
     |                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | The 'Get-AppxPackage' command was found in the module 'Appx', but the module could not be loaded due to the
     | following error: [Operation is not supported on this platform. (0x80131539)] For more information, run
     | 'Import-Module Appx'.

ERROR#1

Write-Error: C:\Users\Merge\Downloads\Win11Debloat-master\Scripts\AppRemoval\RemoveApps.ps1:198
Line |
 198 |                  Invoke-NonBlocking -ScriptBlock {
     |                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | The 'Get-AppxPackage' command was found in the module 'Appx', but the module could not be loaded due to the
     | following error: [Operation is not supported on this platform. (0x80131539)] For more information, run
     | 'Import-Module Appx'.

[Raphire]

Heya,

Thanks for reporting the issue. This seems to be an issue with powershell 7, I'll see if I can reproduce this myself.

In the mean time, could you try running the script with the regular Powershell (Powershell 5)?

[HetCreep]

Confirming @Raphire's read -- this is the known PowerShell 7 / Appx incompatibility. Get-AppxPackage / Remove-AppxPackage live in the Appx module, which can't load natively in PS7 (the 0x80131539 "Operation is not supported on this platform" is the tell -- a documented PowerShell limitation, not WD-specific: PowerShell/PowerShell#13138, #14057). Get-ComputerRestorePoint is also Windows-PowerShell-5.1-only, which is why the restore point was skipped too.

Fallbacks:

• Run via Windows PowerShell 5.1 (powershell.exe), not PS7 (pwsh.exe) -- everything works there.
• Or, if you must use PS7: Import-Module Appx -UseWindowsPowerShell first (loads it via the compat shim, PS 7.0.2+).

I've opened #676 to guard against this at startup -- it detects the Core edition (pwsh) before the admin check and exits with a clear "use powershell.exe" message instead of failing mid-run.

One thing worth flagging separately (not covered by #676): despite every app removal failing, the run still printed "All changes have been applied successfully!" (Show-ApplyModal.ps1 prints it unconditionally). The reporter was told it worked when nothing was removed -- that false success is arguably worse than the PS7 error itself, and it would also mask any other failure (AV blocks, permissions, etc.), not just PS7. Gating that message on whether removals/imports actually succeeded would help.

[Kate-alt-69]

Confirming @Raphire's read -- this is the known PowerShell 7 / Appx incompatibility. Get-AppxPackage / Remove-AppxPackage live in the Appx module, which can't load natively in PS7 (the 0x80131539 "Operation is not supported on this platform" is the tell -- a documented PowerShell limitation, not WD-specific: PowerShell/PowerShell#13138, #14057). Get-ComputerRestorePoint is also Windows-PowerShell-5.1-only, which is why the restore point was skipped too.

Fallbacks:

* Run via **Windows PowerShell 5.1** (`powershell.exe`), not PS7 (`pwsh.exe`) -- everything works there.

* Or, if you must use PS7: `Import-Module Appx -UseWindowsPowerShell` first (loads it via the compat shim, PS 7.0.2+).

I've opened #676 to guard against this at startup -- it detects the Core edition (pwsh) before the admin check and exits with a clear "use powershell.exe" message instead of failing mid-run.

One thing worth flagging separately (not covered by #676): despite every app removal failing, the run still printed "All changes have been applied successfully!" (Show-ApplyModal.ps1 prints it unconditionally). The reporter was told it worked when nothing was removed -- that false success is arguably worse than the PS7 error itself, and it would also mask any other failure (AV blocks, permissions, etc.), not just PS7. Gating that message on whether removals/imports actually succeeded would help.

YES