SOLVED Windows 11 upgrade don't start with a required collection

[Dyna20]

Within our organization, we are upgrading our Windows 10 machines to Windows 11. I have created a task sequence for the upgrade, and it has two deployments attached: one for Available and one for Required. When the update is manually started by a user, the machine is successfully upgraded to Windows 11. However, the machines that are in the Required collection are not upgrading.

There are two machines in the collection, and the deployment status error shows the following:

• For one machine: Program may never run due to service window constraints
• For the other machine: Cache too small

I have assigned a 23-hour maintenance window to the collection and increased the cache size on the second machine to 25 GB (previously 20 GB).

Does anyone know why the machines still won’t upgrade?

Thanks in advance.

 

[Garth]

Within our organization, we are upgrading our Windows 10 machines to Windows 11. I have created a task sequence for the upgrade, and it has two deployments attached: one for Available and one for Required. When the update is manually started by a user, the machine is successfully upgraded to Windows 11. However, the machines that are in the Required collection are not upgrading.

There are two machines in the collection, and the deployment status error shows the following:

• For one machine: Program may never run due to service window constraints
• For the other machine: Cache too small

I have assigned a 23-hour maintenance window to the collection and increased the cache size on the second machine to 25 GB (previously 20 GB).

Does anyone know why the machines still won’t upgrade?

Thanks in advance.

Do your logs show that the MW is big enough now? What do the logs say about the Cache size now?

 

[Dyna20]

I solved the problem after watching a video where someone used the option "Install the following feature updates."
With that setting, I was able to select a different image (see picture below) : "Windows 11 Business Editions" instead of the one I had originally imported into SCCM.

Using that image, the upgrade process started successfully.
I'm still not sure why it doesn't work with the other image, especially since the manual installation does work.