Windows Feature Update Schedule - Succeeded but not actually applied
I created a Windows Feature Update schedule to push to a specific device that has Windows 10 21H2 that will upgrade it to 22H2. The schedule runs and says that it completed, I can force an inventory check and get the device to check-in but the device never receives the pop-up to OK/Snooze/Cancel.
Kace 1000
Action: Detect and Deploy
Device is selected
Selected Feature update to Windows 10 Version 22H2 (for Windows 10 versions 1903 to 21H2) -- the target device is Windows 10 Version 21H2 Build 19044
Selected editions: I have all 3 highlighted (I tried them individually as well)
Notify Options: OK/Snooze/Cancel
Reboot Options: Prompt User
Schedule: Set to None but I'm forcing it to Run Now. I also selected "Run on next connection if offline"
-
I am also seeing this behavior with 22H2. Has anyone found a fix yet? I'm about to open a support ticket but wanted to check here first for a quick fix. - jordanbradley86 10 months ago
-
Have not found a fix. My support ticket has not made much progress. We're going to use a workaround. - craig.s 10 months ago
Answers (3)
I have the same issue as both of you. I thought at first that the computers were missing patches, but that does not seem to be the case. After digging through the KAgent.log files of the computers with issues, I can see where the logs become different on successful/unsuccessful machines. Currently have about an 80% success rate, and it seems that the updates are failing in the detect stage for me.
Successful update
KacePatchModule::Detect: Patch PTCH327151 Name Feature Update to Windows 10 Version 22H2 x64-based systems 2022-10 via Enablement Package Applicable YesUnsuccessful update
KacePatchModule::Detect: Patch PTCH327151 Name Feature Update to Windows 10 Version 22H2 x64-based systems 2022-10 via Enablement Package Applicable No
Applicable No
Means exactly that. It doesn't apply. Enablement Package does not contain any feature updates itself, it only Enables them. They must already be there. They would be installed by previous patches. It is most likely that a required patch for the Enablement pack to run has not been applied.
Try running a full Detect and Deploy to a test system that didn't run. If some patches going into "Downloading" you need to wait til they download or do a manual dl.
Then try the enablement pack again.
Unfortunately the enablement pack does not report to the SMA Agent logs exactly What is missing, just the results of its testing for being applicable.