"Attempting to remove Clipchamp.Clipchamp..." is kept on for more than 20 minutes.

[blunelsongamer]

Describe the bug
I was doing what it was told, open powershell on admin, use the script, select the default, and I waited for 20 minutes...but that was 8 HOURS! And even that shows NOTHING, In 24h2, I don't know why it's taking too long???

To Reproduce
Steps to reproduce the behavior:

1. Open & ([scriptblock]::Create((irm "https://win11debloat.raphi.re/")))
2. Select Default
3. Wait for Attempting to remove Clipchamp.Clipchamp..."
4. Just takes too long

Expected behavior
Maybe the script was not meant for 24h2 ig???

Screenshots
It's just 6AM because I waited for HOURS, and no other apps have been removed.

Additional context
Waited for HOURS, slept in, woke up to find nothing on Windows 11 24h2

[Raphire]

Heya,

This is very strange indeed. I am unable to reproduce this myself on Windows 11 24H2.

Could you try manually removing the app by running powershell as administrator and running the following command:

Get-AppxPackage -Name *Clipchamp* -AllUsers | Remove-AppxPackage -AllUsers

This is the same command Win11Debloat runs under the hood.

[blunelsongamer]

Hey! So this is what i found

Remove-AppxPackage : User cancelled the install request.
AppX Deployment operation failed for package Clipchamp.Clipchamp_3.0.10220.0_neutral_~_yxz26nhyzhsrt with error
0x80073CF8. The specific error text for this failure is: Deployment operation failed.
At line:1 char:47

• ... ppxPackage -Name Clipchamp -AllUsers | Remove-AppxPackage -AllUsers

•                                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : NotSpecified: (:) [Remove-AppxPackage], COMException
  • FullyQualifiedErrorId : System.Runtime.InteropServices.COMException,Microsoft.Windows.Appx.PackageManager.Comman
    ds.RemoveAppxPackageCommand

[blunelsongamer]

Any luck or fixing it yet?

[Raphire]

Any luck or fixing it yet?

I unfortunately haven't been able to find a fix. It does seem similar to the issue here, although I previously assumed that only affected Windows 10.

[ServiceDeskCSI]

ah this explains why it worked on my windows 11 for testing and not windows 10 when i deployed it. I was like what the hell they both use the same commands.