Removed sample output

Author: alkohli

azure-local/known-issues-2411.md

@@ -47,7 +47,7 @@ The following table lists the known issues in this release:
 | Security vulnerability <!--ADO--> |Microsoft has identified a security vulnerability that could expose the local admin credentials used during the creation of Arc VMs on Azure Local to non-admin users on the VM and on the hosts. <br> Arc VMs running on releases prior to Azure Local 2411 release are vulnerable.  |To identify the Arc VMs that require this change and to change the account passwords, see detailed instructions in: [Security vulernability for Arc VMs on Azure Local](https://aka.ms/CVE-2024-49060).|
 | Deployment <!--30273426--> |If the timezone is not set to UTC before you deploy Azure Local, an *ArcOperationTimeOut* error occurs during validation. The following error message is displayed: *OperationTimeOut, No updates received from device for operation.*   |Depending on your scenario, choose one of the following workarounds for this issue: <br><br> **Scenario 1.** Before you start the deployment, make sure that the timezone is set to UTC. <br><br>Connect to each of the Azure Local nodes and change the timezone to UTC. <br><br> Run the following command: `Set-TimeZone -Id "UTC"`. <br><br> **Scenario 2.** If you started the deployment without setting the UTC timezone and received the error mentioned in the validation phase, follow these steps:<br><br> 1. Connect to each Azure Local node. Change the time zone to UTC with `Set-TimeZone -Id "UTC"`. Reboot the nodes.<br><br> 2. After the nodes have restarted, go to the Azure Local resource in Azure portal. Start the validation again to resolve the issue and continue with the deployment.|
 | Update <!--ADO--> | With the 2411 release, applying a Solution Builder Extension package requires a separate update run. Solution and Solution Builder Extension update are not combined in a single update run. ||
-| Update <!--ADO--> | When applying solution update, the update fails at the step "update ARB and extension" error "Clear-AzContext failed with 0 and Exception calling "Initialize" with "1" argument(s): "Object reference not set to an instance of an object." at "Clear-AzPowerShellCache". |Follow these steps on each node of the system. <br> 1. Check if `Az.Accounts` PowerShell module version greater than 3.0.3 is installed. Run the following command: <br><br> `Get-InstalledModule Az.Accounts`<br><br> Here is a sample output: <br><br>Version    Name          Repository         Description<br>-------    ----          ----------         -----------<br>3.0.4      Az.Accounts   PSGallery          Microsoft Azure PowerShel…<br> Verify that the version in output is greater than 3.0.3. In this example, 3.0.4 is installed.  <br><br> 2. Force install `Az.Accounts` PowerShell module version 3.0.3. Run the following commands: <br><br> `Uninstall-Module -Name Az.Accounts -RequiredVersion 3.0.4 -Force`<br> `Install-Module -Name Az.Accounts -RequiredVersion 3.0.3 -Force` <br><br> 3. Confirm `Az.Accounts` PowerShell module version 3.0.3 is installed. Run the following command:<br><br> `Get-InstalledModule Az.Accounts`. <br><br>Verify that the version in the output is 3.0.3. <br><br>4. Retry the update.    |
+| Update <!--ADO--> | When applying solution update, the update fails at the step "update ARB and extension" error "Clear-AzContext failed with 0 and Exception calling "Initialize" with "1" argument(s): "Object reference not set to an instance of an object." at "Clear-AzPowerShellCache". |Follow these steps on each node of the system. <br> 1. Check if `Az.Accounts` PowerShell module version greater than 3.0.3 is installed. Run the following command: <br><br> `Get-InstalledModule Az.Accounts`<br><br>Verify that the `Version` in output is greater than 3.0.3.<br><br> 2. Force install `Az.Accounts` PowerShell module version 3.0.3. Run the following commands: <br><br> `Uninstall-Module -Name Az.Accounts -RequiredVersion 3.0.4 -Force`<br> `Install-Module -Name Az.Accounts -RequiredVersion 3.0.3 -Force` <br><br> 3. Confirm `Az.Accounts` PowerShell module version 3.0.3 is installed. Run the following command:<br><br> `Get-InstalledModule Az.Accounts`. <br><br>Verify that the `Version` in the output is 3.0.3. <br><br>4. Retry the update.    |
 
 
 ## Known issues from previous releases