Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Explorer has difficulty navigating when running in a sandbox with data protection enabled on Windows 11 #3517

Closed
offhub opened this issue Dec 22, 2023 · 5 comments
Labels
explorer.exe Compatibility issues with explorer.exe fixed in next build Fixed in the next Sandboxie version Win 11 Windows 11 issues Workaround Temporary or alternative solution

Comments

@offhub
Copy link
Collaborator

offhub commented Dec 22, 2023

Describe what you noticed and did

When you click back to go to previous folders, the content area remains the same, only the path in the address bar changes.

UsePrivacyMode=y

  1. Open sandboxed Windows Explorer
  2. Navigate to 'C:\Program Files (x86)\Microsoft\Edge\Application' folder by clicking
  3. Try going back to previous folders by clicking back
  4. The content area remains the same
sbie3517wenvgt.mp4

How often did you encounter it so far?

Every time

Affected program

Sandboxed Windows Explorer

Download link

Not relevant

Where is the program located?

The program is installed only outside the sandbox.

Expected behavior

It should work just like outside the sandbox.

What is your Windows edition and version?

Windows 11 Pro 22H2 64-bit (22621.2861)

In which Windows account you have this problem?

A local account (Administrator)., An account with UAC protection set to Always notify.

Please mention any installed security software

Microsoft Windows Defender

What version of Sandboxie are you running?

Sandboxie-Plus 1.12.6 64-bit

Is it a new installation of Sandboxie?

I recently did a new clean installation.

Is it a regression?

No response

In which sandbox type you have this problem?

In a sandbox with data protection (blue sandbox icon).

Can you reproduce this problem on a new empty sandbox?

I can confirm it also on a new empty sandbox.

Did you previously enable some security policy settings outside Sandboxie?

No response

Crash dump

No response

Trace log

No response

Sandboxie.ini configuration

UsePrivacyMode=y
@offhub offhub added Confirmation pending Further confirmation is requested Win 11 Windows 11 issues labels Dec 22, 2023
@offhub offhub added the explorer.exe Compatibility issues with explorer.exe label Jan 5, 2024
@offhub
Copy link
Collaborator Author

offhub commented Jan 5, 2024

The same problem occurs if you block the XAML path when privacy mode is not enabled.

WriteFilePath=explorer.exe,%ProgramData%\Microsoft\Windows\AppRepository\Packages\Microsoft.UI.Xaml.CBS_*__8wekyb3d8bbwe\machine.pckgdep

It may also be related to this #3516.

@offhub offhub added the Workaround Temporary or alternative solution label Jan 5, 2024
@offhub
Copy link
Collaborator Author

offhub commented Jan 5, 2024

Workaround:

UsePrivacyMode=y
ReadFilePath=explorer.exe,%ProgramData%\Microsoft\Windows\AppRepository\Packages\*

@DavidXanatos
Copy link
Member

I think we need to open some subset of %ProgramData%\ in privacy enchanced boxes

@DavidXanatos
Copy link
Member

I'll add
NormalFilePath=%ProgramData%\Microsoft\Windows\AppRepository
to the next build that location is basically like programfiles\windows apps so it needs to be accessible and shouldnt be very personal

@DavidXanatos
Copy link
Member

After revieving the other folders there all of %ProgramData%\Microsoft\ seams to be writable only for processs with administrative privileges, hence the entire NormalFilePath=%ProgramData%\Microsoft\ should be safe to be made readable like C:\program files as there should be no personal data in that location

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
explorer.exe Compatibility issues with explorer.exe fixed in next build Fixed in the next Sandboxie version Win 11 Windows 11 issues Workaround Temporary or alternative solution
Projects
None yet
Development

No branches or pull requests

2 participants