Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

NEW Windows 10 to 11 Update via Enablement Failing

  • Thread starter Thread starter Greg Shafer
  • Start date Start date
  • Replies Replies 2
  • Views Views 8K

Greg Shafer

Member
Messages
20
Solutions
1
Reaction score
1
Points
3
Hoping someone can offer some insight here. Testing out a Windows 10 to WIndows 11 upgrade via enablement package. The update pushes to the client running Windows 10 22H2 and runs through the download/update process. I reboot my workstation once prompted. I go through a very quick 0% to 100% update screen, reboot, and come back to Windows 10. Launching Software Center, I still see my upgrade update with a retry option, and error 0x87D00324(-2016410844). Of course this error means that the install was not detected (yeah kinda figured that out on my own, lol).

I do notice that on the root of C:, I do have a $WINDOWS.~BT directory. Inside, I launch the setup.exe, and it is definitely the Windows 11 setup files. I have gone through the updated CCM logs. One line in particular stands out in the UpdatesDeployment.log

Detect job result indicates Update (Site_20DA0E5B-3B51-492B-B1B6-3E67DD68DB83/SUM_33700b13-ec32-4ebd-ad1d-722901b18ed8) install completed but presence state still not compliant.

At a bit of a loss here at this point, as this is my second attempt to update this workstation with no results. For what it's worth, I did attempt to update via task sequence a week or so ago, and that was also a fail as I hung at 14% installation, cancelled and performed a rollback. Any thoughts or suggestions on what to check would be greatly appreciated.
 
Hoping someone can offer some insight here. Testing out a Windows 10 to WIndows 11 upgrade via enablement package. The update pushes to the client running Windows 10 22H2 and runs through the download/update process. I reboot my workstation once prompted. I go through a very quick 0% to 100% update screen, reboot, and come back to Windows 10. Launching Software Center, I still see my upgrade update with a retry option, and error 0x87D00324(-2016410844). Of course this error means that the install was not detected (yeah kinda figured that out on my own, lol).

I do notice that on the root of C:, I do have a $WINDOWS.~BT directory. Inside, I launch the setup.exe, and it is definitely the Windows 11 setup files. I have gone through the updated CCM logs. One line in particular stands out in the UpdatesDeployment.log

Detect job result indicates Update (Site_20DA0E5B-3B51-492B-B1B6-3E67DD68DB83/SUM_33700b13-ec32-4ebd-ad1d-722901b18ed8) install completed but presence state still not compliant.

At a bit of a loss here at this point, as this is my second attempt to update this workstation with no results. For what it's worth, I did attempt to update via task sequence a week or so ago, and that was also a fail as I hung at 14% installation, cancelled and performed a rollback. Any thoughts or suggestions on what to check would be greatly appreciated.
we use the servicing plan on SCCM to deploy windows 11. if you have access then create a Windows 11 servicing plan / Upgrade and deploy to a collection. once done SCCM will push the latest version of windows 11 to those PCs that are in that collection.
it is not a solution to your specific issue but it worth to try assuming your pc is win 11 compatible.
 
we use the servicing plan on SCCM to deploy windows 11. if you have access then create a Windows 11 servicing plan / Upgrade and deploy to a collection. once done SCCM will push the latest version of windows 11 to those PCs that are in that collection.
it is not a solution to your specific issue but it worth to try assuming your pc is win 11 compatible.
Thank you for the reply, Ahmed. This is exactly what we are doing - Windows 11 servicing plan pushing out via the enablement package. The hardware was previously confirmed as Windows 11 compatible.

As the plot thickens, a second workstation in this test phase did update properly, so it appears the issue is isolated to my PC. Ironically enough, I had the same issue with the Windows 10 21H1 to 22H2 update.
 
Back
Top