Implement feedback

windows/security/application-security/application-isolation/windows-sandbox/index.md

@@ -33,6 +33,9 @@ WSB can be used without any technical skills in various scenarios where users ne
 - **Testing or demoing new software for the first time**: Test drive or demo new software, preview versions, extensions, or add-ons without the hassle of installing and then uninstalling on your host machine.
 - **Maintaining multiple dev environments**: Streamline your development process by utilizing WSB to maintain multiple sandboxes for different development environments. For example, maintain a sandbox for each python version and its dependencies!
 
+> [!NOTE]
+> Windows Sandbox currently doesn't allow multiple instances to run simultaneously.
+
 
 [!INCLUDE [windows-sandbox](../../../../../includes/licensing/windows-sandbox.md)]
 

windows/security/application-security/application-isolation/windows-sandbox/windows-sandbox-cli.md

@@ -32,7 +32,7 @@ The start command creates and launches a new sandbox. The command returns the sa
 - Create a Windows Sandbox environment with a custom configuration:
 
     ```cmd
-    wsb start --config "<configuration><Networking>Disabled</Networking>"
+    wsb start --config "<Configuration><Networking>Disabled</Networking></Configuration>"
     ```
 
 ## List
@@ -50,7 +50,7 @@ The exec command executes a command in the sandbox. The command takes two argume
 > [!NOTE]
 > Currently, there is no support for process I/O meaning that there is no way to retrieve the output of a command run in Sandbox.
 
-Commands in Windows Sandbox can be executed in the system context or in the context of the currently logged on user. However, there's no way to sign-in a user without an active RDP session. Therefore, there currently is no way to execute commands in the user context unless there's an active RDP session.
+An active user session is required to execute a command in the context of the currently logged on user. Therefore, before running this command a remote desktop connection should be established. This can be done using the [connect](#connect) command.
 
 - `--id <id>` (REQUIRED): ID of the Windows Sandbox environment.
 - `-c, --command <command>` (REQUIRED): The command to execute within Windows Sandbox.
@@ -71,17 +71,17 @@ The stop command terminates the sandbox process and releases the resources alloc
 wsb stop --id 12345678-1234-1234-1234-1234567890AB
 ```
 
-## Map
+## Share
 
-The map command maps a host folder to a folder in the sandbox. The command takes three arguments: the sandbox ID, the host path, and the sandbox path. The host path should be a folder. The sandbox path can be either an existing or a new folder. The share command allows the user to share files and folders between the host and the sandbox. An Additional, `--allow-write` option can be used to allow or disallow the Windows Sandbox environment to write to the folder.
+The share command shares a host folder with the sandbox. The command takes three arguments: the sandbox ID, the host path, and the sandbox path. The host path should be a folder. The sandbox path can be either an existing or a new folder. An Additional, `--allow-write` option can be used to allow or disallow the Windows Sandbox environment to write to the folder.
 
 - `--id <id>` (REQUIRED): ID of the Windows Sandbox environment.
-- `-f, --host-path <host-path>` (REQUIRED): Path to folder that is mapped from the host.
+- `-f, --host-path <host-path>` (REQUIRED): Path to folder that is shared from the host.
 - `-s, --sandbox-path <sandbox-path>` (REQUIRED): Path to the folder within the Windows Sandbox.
 - `-w, --allow-write`: If specified, the Windows Sandbox environment is allowed to write to the shared folder.
 
 ```cmd
-wsb map --id 12345678-1234-1234-1234-1234567890AB -f C:\host\folder -s C:\sandbox\folder --allow-write
+wsb share --id 12345678-1234-1234-1234-1234567890AB -f C:\host\folder -s C:\sandbox\folder --allow-write
 ```
 
 ## Connect

windows/security/application-security/application-isolation/windows-sandbox/windows-sandbox-faq.yml

@@ -35,7 +35,7 @@ sections:
               - Windows Sandbox: Provides a secure, isolated environment for testing untrusted software. Any changes made within the sandbox are discarded when you close it.
               - Hyper-V VMs: While VMs also offer isolation, they persistently store changes unless you revert them manually.
           1. **Resource Efficiency**:
-              - Windows Sandbox: More resource efficient than full VM. It adjusts memory usage according to the demand. It also reuses many of the host's read only OS files.
+              - Windows Sandbox: More resource efficient than a full VM. It adjusts memory usage according to the demand. It also reuses many of the host's read only OS files.
               - Hyper-V VMs: VMs have fixed resource allocations, which can impact overall system performance.
           1. **Ease of Use**:
               - Windows Sandbox: Simple to use—just open it, test your software, and close it. No complex setup or management.
@@ -59,12 +59,13 @@ sections:
 
       - question: Installing the latest version of Windows Sandbox fails. How do I fix this?
         answer: |
-          Ensure that your device has access to the Internet, Windows Update, and Microsoft Store. Beginning from Windows 11 24H2, the old Windows Sandbox app attempts to download the latest version from the Store. If the upgrade fails initially, installation continues in the background while the user can still use the app. Additionally, the app is queued in the "Updates & Downloads" section of the Microsoft Store app for users who wish to manually install it manually.
+          Ensure that your device has access to the Internet, Windows Update, and Microsoft Store. Beginning from Windows 11 24H2, the old Windows Sandbox app attempts to download the latest version from the Store. If the upgrade fails on the first attempt, subsequent attempts continue in the background. Meanwhile, the app can still be used. Additionally, the installation app is queued in the "Updates & Downloads" section of the Microsoft Store app for users who wish to manually install.
 
       - question: How do I know which version of Windows Sandbox am I running?
         answer: |
           Run `Get-AppxPackage -Name WindowsSandbox | Select-Object Version` in a PowerShell prompt. If the version is empty, you're running an older version of Windows Sandbox. If it returns a version number, you're running the newer version.
-          Alternatively, if your Windows Sandbox app has a '...' button in the top-right corner that opens a drop-down menu, you're using the new version.
+          Alternatively, you can run `wsb --version`. If `wsb` is not available, you're running an older version of Windows Sandbox.
+          The new version of Windows Sandbox also appears in Windows Settings under **System** > **System components**.
 
       - question: How do I save the Sandbox state?
         answer: |
@@ -76,7 +77,9 @@ sections:
 
       - question: How do I uninstall Windows Sandbox?
         answer: |
-          Run the following PowerShell cmdlet to uninstall the app: `Get-AppxPackage -name WindowsSandbox | Remove-AppxPackage`
+          Run the following PowerShell cmdlet to uninstall the Windows Sandbox app: `Get-AppxPackage -name WindowsSandbox | Remove-AppxPackage`
+
+          To completely remove Windows Sandbox, and all its components, navigate to **Settings > System > Optional features**, then select **More Windows features**, scroll down and unselect Windows Sandbox, then select OK.
 
   - name: Feedback
     questions:
@@ -95,7 +98,7 @@ sections:
               - Behavior you were expecting.
           1. Select an appropriate category and subcategory by using the dropdown menus. There's a dedicated option in Feedback Hub to file **Windows Sandbox** bugs and feedback. It's located under **Security and Privacy** category.
           1. Select **Next**.
-          1. If necessary, you can collect traces for the issue as follows: Select the Recreate my problem tile, then select Start capture, reproduce the issue, and then select **Stop capture**.
+          1. If you are able to reproduce the issue, please collect traces as follows: Select the Recreate my problem tile, then select Start capture, reproduce the issue, and then select **Stop capture**.
           1. Attach any relevant screenshots or files for the problem, then select **Submit**.
 
           Alternatively, you can also use the [Windows Sandbox GitHub repository](https://github.com/microsoft/Windows-Sandbox) to: