Validation Getting stuck at Name: AzStackHci_OSImageRecipeValidation_LCU DisplayName: Latest Cumulative Update matches recipe.

Hello Mishra Keshav Kumar,

Greetings! Thanks for raising this question in Q&A forum.

The reason this validation is failing is quite clear from the error detail — the Azure Local deployment validator is checking that specific Latest Cumulative Updates (LCUs) defined in the OS Image Recipe are installed on your node, but the expected updates KB5082417 and KB5082063 are not present on the host USDTNAZLOCALP02. Your node currently has KB5087051, KB5087539, KB5082062, and KB5089717 installed, but the recipe strictly requires the exact KB versions it was built with. Even though some of your installed updates are newer, the recipe validation does an exact match check and will fail if the specific expected KB is not found.

Here are the steps to fix this:

Do not manually install the missing KBs one by one — The right fix is to re-image the node using the correct OS image that matches the recipe version. The validation is telling you the OS baseline on this node doesn't match what the deployment recipe expects. The official remediation link in the error itself points you to: https://learn.microsoft.com/en-us/azure-stack/hci/deploy/deployment-tool-install-os

Check which OS image version your deployment recipe requires — Log into your deployment tool or the Azure Local cluster configuration and confirm the exact OS image recipe version being used. Make note of the recipe name and version — this tells you which ISO or image you need to apply.

Re-image the affected nodes using the correct baseline OS image — Download the correct Azure Stack HCI OS image that corresponds to your recipe. When you re-image, it will include the exact LCU baseline (including KB5082417 and KB5082063) that the recipe expects. Follow the steps at the link above for the OS installation procedure.

Do not apply Windows Updates manually before deployment completes — This is a very common cause of this exact issue. If Windows Update ran on the node after the OS was installed but before deployment finished, it may have replaced or superseded the exact KB versions the recipe checks for. After re-imaging, make sure to disable Windows Update or disconnect from the internet temporarily until the deployment validation passes.

Verify all nodes in the cluster use the same image — Since the error says "all nodes," make sure you apply the correct baseline image consistently across every node. Mixed update states across nodes will cause the same validation to fail on multiple machines.

Re-run the validation after re-imaging — Once the correct OS image is applied to all nodes, re-trigger the deployment validation from your Azure Local deployment tool. The AzStackHci_OSImageRecipeValidation_LCU check should pass once the exact expected KBs are present.

If re-imaging is not an option right now — As a workaround, you can try running the following command on the affected node to check what's installed and then manually apply the missing KBs from the Microsoft Update Catalog (https://catalog.update.microsoft.com). Search for KB5082417 and KB5082063 directly and install them. However, re-imaging is the cleaner and more reliable fix.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,

Jerald Felix.