Jump to content

Recommended Posts

Posted

Trying to capture a Win11 24H2 image (new Windows 11 version) but during Sysprep it fails with:

 

SYSPRP Package - Microsoft.Copilot_0.4.2.0_neutral__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

 

So, I have removed Copilot from that user:

 

# Find and Remove

Get-AppxPackage | where Name -like *copilot* | Remove-AppxPackage

 

# Check this returns nothing

Get-AppxPackage | where Name -like *copilot

 

But the same error is coming up, I don’t have any other users on the capture image. Any ideas where sysprep is finding this installed software?

Posted
I thought Win11 wasn’t supported on MDT.

 

Indeed it does work - our whole summer we rebuilt with MDT with Win 11. I don't bother capturing a 'base' image anymore, I find just basing it on a 'virgin' Windows 11 ISO image and remove unwanted .appx's as a step in the re-image task sequence, and install what we need in the traditional ways, either .MSI with GPO and/or we use Burconix to deploy software to our stations.

 

Pete

Posted (edited)

Managed a successful capture and reimaging yesterday with 24H2. I strip out unwanted AppX packages from the vanilla OS before running any task sequences against it, using a script based on using Remove-AppxProvisionedPackage. I found that trying it during the task sequence wasn't always successful, with apps sometimes getting provisioned already before the step in the sequence gets run.

 

I haven't updated my script for that from what I wrote for 23H2, so it doesn't attempt to remove the Copilot app. I'll give it a go and see it it can remove it. I know that the Get Started app is a special case for some reason, as it reappears despite an apparently successful attempt to remove it, so it could be that Copilot is similarly special.

 

EDIT:

Hmm, I think the Copilot app is just a web app, running in an instance of Edge, so no AppX package to speak of.

Edited by jthompson
Posted
Yes, got round this by not bothering with a Capture. Download ISO from MS and just import it, anything else traditionally done before capturing (e.g. .NET 3.5 feature) can be done via the usual software install methods/scripts.
  • 5 months later...
Posted

Hi I have revisited this and think my brain has died trying to sort this error! Does anyone please have the command to help solve this SYSPRP error please? Any help greatly appreciated thanks

 

2025-03-25 16:35:31, Error                 SYSPRP Package Microsoft.Copilot_0.4.2.0_neutral__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

  • 6 months later...
Posted

If it's anything like the fun and games I've had with one of their damned language packs, you need to use a slightly different syntax to remove it:

Get-AppxPackage | Where-Object {$_.PackageFullName -eq "***PACKAGE FULL NAME***"} | Remove-AppxPackage

 (Obviously removing ***PACKAGE FULL NAME*** and replacing it with the package's full name!)

Posted

Thank you these also did the job:

 

Remove-AppxPackage -AllUsers -Package Microsoft.Copilot_0.4.2.0_neutral__8wekyb3d8bbwe
 

Remove-AppxProvisionedPackage -Online -PackageName Microsoft.Copilot_0.4.2.0_neutral__8wekyb3d8bbwe

Posted
On 03/10/2024 at 09:22, FragglePete said:

 

Indeed it does work - our whole summer we rebuilt with MDT with Win 11. I don't bother capturing a 'base' image anymore, I find just basing it on a 'virgin' Windows 11 ISO image and remove unwanted .appx's as a step in the re-image task sequence, and install what we need in the traditional ways, either .MSI with GPO and/or we use Burconix to deploy software to our stations.

 

Pete

 

Have to agree, that that has been our preferred method for years, also then much easier to swap in a new OS or version of Windows - just replacing the 24H2 WIM with the 25H2 one this morning for some testing - no need to generate a whole new "gold image"...

Posted

Also new in 25h2, once you've installed the new admx files:

 

Windows 11 25H2 introduces a new Group Policy setting to remove default Microsoft Store apps, but it only affects new user accounts and requires the Pro or higher edition of Windows. To use it, you must enable the "Remove Default Microsoft Store packages from the system" policy in the Group Policy Editor under "Computer Configuration" > "Administrative Templates" > "Windows Components" > "App Package Deployment" and select the apps you want to remove

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...