Update known-issues.md

Author: sipastak

azure-local/known-issues.md

@@ -65,7 +65,7 @@ The following table lists the known issues in this release:
 | Security <!--30348397--> |  Azure Local might face an issue during normal operations (for example, Update, Repair) while using Defender for Endpoint and when the **Restrict App Execution** setting is enabled for one or more servers in the deployment.  | Disable the **Restrict App Execution** setting in the Defender portal and reboot. If the issue persists, [open a support case](/azure/azure-portal/supportability/how-to-create-azure-support-request). |
 | Deployment <!--33390832--> | Deployment fails with errors during validation that state that the mandatory Arc extensions are not yet installed. |  |
 | Deployment <!--33392176--> |  Deployment fails with PSTerminatingError. | If you face this issue, retry the deployment. |
-| Update <!--33470082--> |  Solution update fails with the error: `Unable to install solution update "11.2506.1001.24" - Type 'UpdateFOD' of Role 'ComposedImageUpdate' raised an exception.` | To work around this issue, run the following on each node:<br><br>`$ComposedImageRegistryKeyPath = "HKLM:\SYSTEM\CurrentControlSet\Services\ComposedBuildInfo\Parameters"`<br>`$ComposedBuildIdKey = "COMPOSED_BUILD_ID"`<br>`$ComposedBuildIdValue = "11.2504.0.3141"`<br><br>`if (!(Test-Path -Path $ComposedImageRegistryKeyPath))`<br>{<br>` Write-Host "Creating registry key $($RegKeyPath) with key $($ComposedBuildIdKey)";`<br>`New-Item -Path $ComposedImageRegistryKeyPath -Force | Out-Null;`<br>`New-ItemProperty -Path $ComposedImageRegistryKeyPath -Name $ComposedBuildIdKey -PropertyType String -Force | Out-Null;`<br>`Set-ItemProperty -Path $ComposedImageRegistryKeyPath -Name $ComposedBuildIdKey -Value $ComposedBuildIdValue`<br>`Write-Host "Set registry with value $($ComposedBuildIdValue)"`<br><br>`}` |
+| Update <!--33470082--> |  Solution update fails with the error: `Unable to install solution update "11.2506.1001.24" - Type 'UpdateFOD' of Role 'ComposedImageUpdate' raised an exception.` | To work around this issue, run the following on each node:<br><br>`$ComposedImageRegistryKeyPath = "HKLM:\SYSTEM\CurrentControlSet\Services\ComposedBuildInfo\Parameters"`<br>`$ComposedBuildIdKey = "COMPOSED_BUILD_ID"`<br>`$ComposedBuildIdValue = "11.2504.0.3141"`<br><br>`if (!(Test-Path -Path $ComposedImageRegistryKeyPath))`<br>`{`<br>` Write-Host "Creating registry key $($RegKeyPath) with key $($ComposedBuildIdKey)";`<br>`New-Item -Path $ComposedImageRegistryKeyPath -Force | Out-Null;`<br>`New-ItemProperty -Path $ComposedImageRegistryKeyPath -Name $ComposedBuildIdKey -PropertyType String -Force | Out-Null;`<br>`Set-ItemProperty -Path $ComposedImageRegistryKeyPath -Name $ComposedBuildIdKey -Value $ComposedBuildIdValue`<br>`Write-Host "Set registry with value $($ComposedBuildIdValue)"`<br><br>`}` |
 
 ## Known issues from previous releases