Update known-issues.md

1 files changed, 6 insertions, 16 deletions

diff --git a/release-notes/6.0/known-issues.md b/release-notes/6.0/known-issues.md
index 91126cab..6c92f56a 100644
--- a/release-notes/6.0/known-issues.md
+++ b/release-notes/6.0/known-issues.md
@@ -34,22 +34,12 @@ If you build .NET 6 projects with MSBuild 16.11, for example, you will see the f
 
 You can use the .net 6 SDK to target downlevel runtimes in 16.11.
 
-#### 1. dotnet test x64 emulation on arm64 support
-While a lot of work has been done to support arm64 emulation of x64 processes in .net 6, there are some remaining [work](https://github.com/dotnet/sdk/issues/21686) to be done in 6.0.2xx. The most impactful remaining item is `dotnet test` support.
+#### 1. Windows admin installs of the .NET 6.0.400 SDK will not correctly update .NET SDK optional workloads
+Commands like `dotnet workload install` and `dotnet workload update` will not correctly update to the latest versions of the workloads on the first try. This is because a timing issue in the workload manifest update code causes the SDK to stop early typically only updating 0-1 manifests.
 
-`dotnet test --arch x64` on an arm64 machine will not work as it will not find the correct test host.  To test x64 components on an arm64 machine, you will have to install the x64 SDK and configure your `DOTNET_ROOT` and `PATH` to use the x64 version of dotnet.
-
-#### 2. Upgrade of Visual Studio or .NET SDK from earlier builds can result in a bad `PATH` configuration on Windows
-When upgrading Visual Studio to preview 5 or the .NET SDK to RC2 from an earlier build, the installer will uninstall the prior version of the .NET Host (dotnet.exe) and then install a new version. This results in the path to the x64 copy of dotnet being removed from the `PATH` then added back. If you have the x86 .NET Host installed, it will end up ahead of the x64 one and will be picked up first. 
-
-In this case you may find that Visual Studio is unable to create projects, or commands like `dotnet new` fail with a message like this:
-```
-Could not execute because the application was not found or a compatible .NET SDK is not installed.
-```
-
-To confirm, run `dotnet --info` and you'll see (x86) paths for all of the found .NET runtimes and .NET SDKs installed. 
-
-To fix this, edit your `PATH` environment variable to either remove the `c:\Program Files (x86)\dotnet` entry or move it after the entry for `c:\Program Files\dotnet`. Now reopen your console window.
+**Workarounds**
+1. Run `dotnet workload update` again and again until all workloads are updated.
+2. Run `dotnet workload update --from-rollback-file` specifying the exact workload versions you want to install.
    
 ## ASP.NET Core
 
@@ -157,4 +147,4 @@ This happened because WPF builds in 6.0.7 onwards, only considered source genera
             <Analyzer Include="@(FilteredAnalyzer)" />
         </ItemGroup>
     </Target>    
-    ```
\ No newline at end of file
+    ```