Drag the PyCharm Community Edition 2022.3 shortcut from the desktop into SandMan;
PyCharm fails to start and reports the following error:
My Windows system login user name is sandboxie_test_user1. According to my analysis, this is caused by the path being too long after Sandboxie converts the directory; so I did the following test:
Adjusted the LongPathsEnabled under HKLM\SYSTEM\CurrentControlSet\Control\FileSystem in the registry to 1;
Adjusted the configuration related to 8dot3 in the registry;
Set "Enable Win32 long path" in the group policy to enable;
However, the error persists.
But the same user name and application can be started normally in Sandboxie in Windows Server 2016 without any settings.
For the above situation, is Sandboxie compatible?
Describe what you noticed and did
My Windows system login user name is sandboxie_test_user1. According to my analysis, this is caused by the path being too long after Sandboxie converts the directory; so I did the following test:
However, the error persists. But the same user name and application can be started normally in Sandboxie in Windows Server 2016 without any settings. For the above situation, is Sandboxie compatible?
How often did you encounter it so far?
Appears every time you use.
Affected program
pycharm-community-2022.3.exe
Download link
https://www.jetbrains.com/pycharm/download/#section=windows
Where is the program located?
The program is installed only outside the sandbox.
Expected behavior
PyCharm can start normally.
What is your Windows edition and version?
Windows Server 2019 Standard
In which Windows account you have this problem?
A local or Microsoft account without special changes.
Please mention any installed security software
Windows Defender
What version of Sandboxie are you running?
Sandboxie plus 1.5.3 64
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 standard isolation sandbox (yellow sandbox icon).
Can you reproduce this problem on an empty sandbox?
I can confirm it also on an 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