Skip to content
This repository was archived by the owner on Dec 9, 2025. It is now read-only.

The issue with sandbox strategy. #39

Description

@minusmulticoloredper

I searched online for a range of browsers built on the latest Chromium version that would run on Windows 7. All of them displayed empty sandbox policies on Windows 7, whereas these policies were properly shown on Windows 10 and later versions. Initially, I believed this was simply a compatibility issue with Windows 7. However, after injecting Vxkex into Ungoogled-Chromium, I found that the sandbox policy was still empty.

I thought that since the browser worked fine on Windows 10, I could trick it into thinking it was running on Windows 10. So, I enabled the system version spoofing feature in Vxkex and launched the browser again. To my surprise, the sandbox policy was now displayed correctly.

I am not a developer—just a user—but I suspect that Chromium checks the operating system version and applies different sandbox policies accordingly. Since there’s no sandbox policy designed specifically for Windows 7, it defaults to an empty policy.

Test results are as follows:

Without Vxkex enabled

Image

With Vxkex enabled

Image

With OS version spoofing enabled

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions