deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Acro-updates

Browse Source
This commit is contained in:
Vinay Pamnani (from Dev Box) 2024-10-22 15:57:56 -06:00
parent e6613bb5f4
commit 284258a524
4 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
windows/security/application-security/application-isolation/windows-sandbox/windows-sandbox-cli.md
View File

@ -50,11 +50,11 @@ 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 is no way to log on a user without an active RDP session. Therefore, there currently is no way to execute commands in the user context unless there is an active RDP session.
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.
- `--id <id>` (REQUIRED): ID of the Windows Sandbox environment.
- `-c, --command <command>` (REQUIRED): The command to execute within Windows Sandbox.
- `-r, --run-as <ExistingLogin|System>` (REQUIRED): Specifies the user context to execute the command within. If the System option is selected, the command will run in the system context. If the ExistingLogin option is selected, the command will run in the currently active user session or fail if there is no active user session.
- `-r, --run-as <ExistingLogin|System>` (REQUIRED): Specifies the user context to execute the command within. If the System option is selected, the command runs in the system context. If the ExistingLogin option is selected, the command runs in the currently active user session or fails if there's no active user session.
- `-d, --working-directory <directory>`: Directory to execute command in.
```cmd
@ -76,9 +76,9 @@ wsb stop --id 12345678-1234-1234-1234-1234567890AB
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.
- `--id <id>` (REQUIRED): ID of the Windows Sandbox environment.
- `-f, --host-path <host-path>` (REQUIRED): Path to folder that will be mapped from the host.
- `-f, --host-path <host-path>` (REQUIRED): Path to folder that is mapped 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 will be allowed to write to the shared folder.
- `-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

2
windows/security/application-security/application-isolation/windows-sandbox/windows-sandbox-configure-using-wsb-file.md
View File

@ -9,7 +9,7 @@ ms.date: 09/09/2024
To launch a Windows Sandbox with default settings, locate and select Windows Sandbox on the Start menu or search for 'Windows Sandbox'. This launches a basic Sandbox with maximum capacity of 4GB memory with the following properties:
- **vGPU (virtualized GPU)**: Enabled on non-ARM64 devices.
- **vGPU (virtualized GPU)**: Enabled on non-Arm64 devices.
- **Networking**: Enabled. The sandbox uses the Hyper-V default switch.
- **Audio input**: Enabled. The sandbox shares the host's microphone input into the sandbox.
- **Video input**: Disabled. The sandbox doesn't share the host's video input into the sandbox.

2
windows/security/application-security/application-isolation/windows-sandbox/windows-sandbox-install.md
View File

@ -9,7 +9,7 @@ ms.date: 09/09/2024
## Prerequisites
- ARM64 (for Windows 11, version 22H2 and later) or AMD64 architecture
- Arm64 (for Windows 11, version 22H2 and later) or AMD64 architecture
- Virtualization capabilities enabled in BIOS
- At least 4 GB of RAM (8 GB recommended)
- At least 1 GB of free disk space (SSD recommended)

8
windows/security/application-security/application-isolation/windows-sandbox/windows-sandbox-versions.md
View File

@ -11,8 +11,8 @@ Starting with Windows 11, version 24H2, a newer version of Windows Sandbox is av
- **Faster Updates**: With the app now being updated through the Microsoft Store, you can install the bug fixes and new features as soon as they're available, rather than needing to wait for an update of the Windows operating system.
- **Revamped UI**: The app now features WinUI 3, a modern and sleek user interface built on the Fluent design system.
- **New Runtime Features**: Users can now access clipboard redirection, audio/video input control, and folder sharing directly during runtime using the "…" icon in the top-right corner. No need for pre-configured .wsb files.
- **Command Line Preview**: We've introduced an early version of command line support for Windows Sandbox. Check out ---- for more details.
- **New Runtime Features**: Users can now access clipboard redirection, audio/video input control, and folder sharing directly during runtime using the "…" icon in the top-right corner without needing a preconfigured `.wsb` file.
- **Command Line Preview**: An early version of [command line support](windows-sandbox-cli.md) for Windows Sandbox is now available.
## Upgrading to the newer version
@ -25,8 +25,8 @@ Starting with Windows 11, version 24H2, a newer version of Windows Sandbox is av
### Upgrade
- Launch **Windows Sandbox** from the Start menu.
- If the app hasn't been upgraded to the latest version, a progress dialog appears as it automatically attempts to update. This process typically takes 30 seconds to 2 minutes.
- Once the installation is complete, you'll be directed to the updated version of the app.
- If the app isn't upgraded to the latest version, a progress dialog appears as it automatically attempts to update. This process typically takes 30 seconds to 2 minutes.
- 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.