0

I've been trying to create a WIM of my modified Windows 11 install. To that end, I've been attempting to have Sysprep clean Win 11 using the "generalize" option. Yet, in Sysprep, every time I tick "generalize" & click OK, a dialog saying "Sysprep was not able to validate your Windows installation" pops up.

This doesn't seem to be the case as checking System > Activation > Activation state says it's "Active". It seems like the license for the OEM Win 10 this laptop came with carried over for Win 11.

So far, every once in a while, I've been able to trigger a reboot/shutdown with generalize when I use tools that disrupts the activation state of Windows, like say, running KMSpico or manually entering a different product key.

I need a way to be able to reboot/shutdown with generalize selected without these fickle tricks of disrupting the activation state.

13
  • Just to clarify, Windows 10 OEM licenses, are able to activate OEM installations of Windows 11.
    – Ramhound
    Sep 19 at 7:34
  • Very little without the setupact.log file that was generated. The reason Windows was unable to validate (which has nothing to do with the activation status of Windows) will be specified in the log file. By the tone of your last comment, I can tell you don't find my comment very helpful, which makes me very cautious asking for additional information since I have no idea how you will react to additional questions about your problem.
    – Ramhound
    Sep 19 at 16:42
  • Here's a copy of the setupact.log: drive.google.com/file/d/1LXFq4OiWPhy9fMNy8_ysr4HCLbUnNwkG/view Sep 19 at 19:06
  • It's been 4 hours. When I have the time I will look at it the logs, if I see something, I will submit an answer. If there is a problem with that timeline, then I can just skip that last part, and enjoy my night.
    – Ramhound
    Sep 19 at 23:20
  • “Microsoft.OneDriveSync_21220.1024.5.0_neutral__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.” - This is the error that cause the “cannot validate” error.
    – Ramhound
    Sep 19 at 23:54

1 Answer 1

0

To that end, I've been attempting to have Sysprep clean Win 11 using the "generalize" option. Yet, in Sysprep, every time I tick "generalize" & click OK, a dialog saying "Sysprep was not able to validate your Windows installation" pops up.

Error: SYSPRP Package Microsoft.OneDriveSync_21220.1024.5.0_neutral__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

The log you provided indicates that Microsoft.OneDriveSync was the reason Windows wasn’t able to be validated.

Run the following commands as an Administrator in a PowerShell prompt:

Import-Module Appx

Import-Module Dism

Get-AppxPackage -AllUsers Microsoft.OneDriveSync_21220.1024.5.0_neutral__8wekyb3d8bbwe | Remove-AppxPackage -AllUsers

Remove-AppxPackage -Package Microsoft.OneDriveSync_21220.1024.5.0_neutral__8wekyb3d8bbwe

Get-AppxPackage -AllUsers | Where PublisherId -eq 8wekyb3d8bbwe | Format-List -Property PackageFullName,PackageUserInformation

For each application from the last command run the following:

Remove-AppxPackage -Package <packagefullname>

Remove-AppxProvisionedPackage -Online -PackageName

Source:

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.