Skip to content

Bypass default encryption policy when expanding sandbox vhdx#2572

Open
mendsley wants to merge 1 commit intomicrosoft:mainfrom
PlayEveryWare:bypass_vhd_encryption_policy
Open

Bypass default encryption policy when expanding sandbox vhdx#2572
mendsley wants to merge 1 commit intomicrosoft:mainfrom
PlayEveryWare:bypass_vhd_encryption_policy

Conversation

@mendsley
Copy link

@mendsley mendsley commented Dec 9, 2025

This fixes the following error when running on machines with a policy to enforce bitlocker encryption on fixed drives

failed to create scratch layer: failed to expand sandbox vhdx size to #### bytes: FSCTL_EXTEND_VOLUME \\?\Volume{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}: The media is write protected.

Fixed: #2464

@mendsley mendsley requested a review from a team as a code owner December 9, 2025 16:42
@mendsley mendsley force-pushed the bypass_vhd_encryption_policy branch from ea83880 to 328b926 Compare December 9, 2025 16:43
This fixes the following error when running on machines with a policy to
enforce bitlocker encryption on fixed drives

```
failed to create scratch layer: failed to expand sandbox vhdx size to #### bytes: FSCTL_EXTEND_VOLUME \\?\Volume{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}: The media is write protected.
```

Fixed: microsoft#2464
Signed-off-by: Matthew Endsley <mendsley@gmail.com>
@thaJeztah
Copy link
Contributor

@ambarve PTAL if you have time; this may resolve an issue with Docker that people ran into.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Containers Fail To Start When Fixed Drive Bitlocker Is Enforced

2 participants