mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Implement feedback items from Kavya
This commit is contained in:
Vinay Pamnani (from Dev Box)
parent
284258a524
commit
78a8b00b0d
@ -107,7 +107,7 @@ Supported values:
|
||||
|
||||
An array of folders, each representing a location on the host machine that is shared with the sandbox at the specified path. Currently, relative paths aren't supported.
|
||||
|
||||
When using `<Mappedfolders>` to map folders, the folders are mapped before the execution of the [Logon command](#logon-command).
|
||||
When using `<Mappedfolders>` to map folders, the folders are mapped before the execution of the [Logon command](#logon-command). Beginning in Windows 11, version 23H2, you can use environment variables in the path.
|
||||
|
||||
```xml
|
||||
<MappedFolders>
|
||||
@ -123,11 +123,11 @@ When using `<Mappedfolders>` to map folders, the folders are mapped before the e
|
||||
```
|
||||
|
||||
- **HostFolder**: Specifies the folder on the host machine to share into the sandbox. The folder must already exist on the host, or the container fails to start.
|
||||
- **SandboxFolder**: Specifies the destination in the sandbox to map the folder to. If the folder doesn't exist, it gets created. If no sandbox folder is specified, the folder is mapped to the container desktop.
|
||||
- **SandboxFolder**: Specifies the destination in the sandbox to map the folder to. If the folder doesn't exist, it gets created. If no sandbox folder is specified, the folder is mapped to the container user's desktop. The default user of Sandbox is `WDAGUtilityAccount`.
|
||||
- **ReadOnly**: If *true*, enforces read-only access to the shared folder from within the container. Supported values: *true*/*false*. Defaults to *false*.
|
||||
|
||||
> [!NOTE]
|
||||
> Files and folders mapped in from the host can be compromised by apps in the sandbox or potentially affect the host. Changes made during a Sandbox session to a mapped folder with write-permissions will persist after a Sandbox is disposed.
|
||||
> Files and folders mapped from the host can be compromised by apps in the sandbox or potentially affect the host. Changes made during a Sandbox session to a mapped folder with write-permissions will persist after a Sandbox is disposed.
|
||||
|
||||
### Logon command
|
||||
|
||||
|
||||
@ -48,6 +48,32 @@ sections:
|
||||
answer: |
|
||||
Today, Windows Sandbox only allows users to launch one Sandbox instance at a time.
|
||||
|
||||
- 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.
|
||||
|
||||
- question: How do I know which version of Windows Sandbox I am running?
|
||||
answer: |
|
||||
Run `Get-AppxPackage -Name WindowsSandbox | Select-Object Version` in a PowerShell prompt. If the version is empty, you are running an older version of Windows Sandbox. If this returns a set of digits, you are 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.
|
||||
|
||||
- question: How do I save the Sandbox state?
|
||||
answer: |
|
||||
Windows Sandbox is temporary; closing it deletes all software, files, and state.
|
||||
|
||||
- question: How can I open Windows Sandbox with a different OS version?
|
||||
answer: |
|
||||
Windows Sandbox only allows you to use the same build as your host OS. This allows us to keep Windows Sandbox 'lightweight'.
|
||||
|
||||
- question: What applications aren't supported inside a Windows Sandbox?
|
||||
answer: |
|
||||
Inbox apps (for example, Store, Notepad) and Optional features turned on via 'Turn Windows Features On or Off' are not supported.
|
||||
While Store apps can be installed, you can't download them directly from the Store since the Store app isn't available in the Sandbox. However, if you have an `.appx` package, you can still install those apps.
|
||||
|
||||
- question: How do I uninstall Windows Sandbox?
|
||||
answer: |
|
||||
Run the following PowerShell cmdlet to uninstall the app: `Get-AppxPackage -name WindowsSandbox | Remove-AppxPackage`
|
||||
|
||||
- name: Feedback
|
||||
questions:
|
||||
|
||||
|
||||
@ -16,4 +16,6 @@ This article lists some common issues with Windows Sandbox and possible solution
|
||||
| `E_INVALIDARG` | The `.wsb` file provided by the user is invalid or has errors. Check the `.wsb` file. |
|
||||
| `REGDB_E_IIDNOTREG` | Verify if Windows Sandbox component is enabled under 'Turn Windows features on or off'. For more information, see [Install Windows Sandbox](windows-sandbox-install.md) |
|
||||
| `The following settings are enforced by your IT administrator.` | `.wsb` file has a setting enabled that is controlled via group policy. |
|
||||
| General failure during installation. | Possible causes: <br><br>- Installing Windows Sandbox is disabled via group policy. Check with your IT Admin. <br>- Timeout error where we can't reach the Microsoft Store. Try again later. |
|
||||
| `No hypervisor was found. Please enable hypervisor support.` | Windows Sandbox only supports Hyper-V Hypervisor. Third-party hypervisors are not supported. Ensure that Hyper-V is enabled. |
|
||||
| `Cannot upgrade to the latest version of Windows Sandbox` | Ensure that your device has access to the Internet, Windows Update and Microsoft Store. Beginning with Windows 11, version 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 install it manually. |
|
||||
| `E_FAIL`, or `E_UNEXPECTED` or general failure during installation. | Possible causes: <br><br>- Installing Windows Sandbox is disabled via group policy. Check with your IT Admin. <br>- Timeout error where we can't reach the Microsoft Store. Try again later. |
|
||||
|
||||
@ -20,7 +20,7 @@ Starting with Windows 11, version 24H2, a newer version of Windows Sandbox is av
|
||||
|
||||
- Windows Sandbox must already be installed. If it isn't already installed, [install Windows Sandbox](windows-sandbox-install.md).
|
||||
- Device must be running Windows 11, version 24H2, with KB10D or later.
|
||||
- Microsoft Store and Windows Update must be accessible.
|
||||
- Internet access for Microsoft Store and Windows Update.
|
||||
|
||||
### Upgrade
|
||||
|
||||
@ -29,4 +29,4 @@ Starting with Windows 11, version 24H2, a newer version of Windows Sandbox is av
|
||||
- Once the installation is complete, you're directed to the updated version of the app.
|
||||
|
||||
> [!NOTE]
|
||||
> If the upgrade fails on the first try, the installation continues in the background while you use the older version of 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.
|
||||
> If the upgrade fails on the first try, the installation continues in the background while you use the older version of the app. Additionally, the app is queued in the "Updates & downloads" section of the Microsoft Store app for users who wish to install it manually.
|
||||
Loading…
x
Reference in New Issue
Block a user