Custom package not deploying - Result code: 0x80240003

Question

I have built a customer package to configure Intel AMT. I have set the applicability rule and pre-requisite to a registry key that I know exist on the computers, but each time I try to deploy the package I get the following error:

Update not applicable. Unable to find the Update by ID to perform the requested operation. The update may not be applicable for the selected computer Result Code: 0x80240003

I have triple checked the rules and got my colleagues to check and the computers to meet the requirements.

Please help.

LGarvin · Accepted Answer

I can confirm that in the process of creating the package I have been tweaking the package many times, but each time I amend it I use the Delete option when I republish. This may be part of the issue. The "Delete" option from the Publishing Wizard is not always successful at fully deleting a package from WSUS *and* if you didn't duplicate the package, then it's actually just a revision anyway. Depending on what your'e doing in the package's binary attachment, this could also be part of the problem. As a starting point, I would suggest visually scanning the Update View of the WSUS node and verifying that [a] all previous packages are declined/expired/deleted, and [b] any revisions to the current package are also expired. You might even opt to expire/decline/delete all of them and start with a fresh Revision #1 package. In general, if you're just changing RULES in a package, you only need to publish a revision (which happens automatically if the UpdateID already exists in WSUS). If you're changing PackageBoot or the BINARY files, then the best approach is this: Expire the update on WSUS and allow for all clients to detect and get the expiration (or force a Detect Now to get expirations immdiately). After the expiration has been received by the affect client(s), then you can Decline or Delete the update. (I suggest deleting it.) After configuring the expiration via the WSUS node of the PM console, then Duplicate-and-Publish the package (with needed changes). What this gives you then is: The original UpdateID is now expired, so clients will ignore it. The modified update package has a new UpdateID which will keep it from getting confused with the earlier packages.

Custom package not deploying - Result code: 0x80240003

Top Replies