Rename SbieDll

[H4CK3R0FF1C14L]

Is your feature request related to a problem or use case?

How can I rename SbieDll to avoid detection by the program? And since I can generally build this project, there are no build instructions and it makes it very difficult to work with this project?

Describe the solution you'd like

.

Describe alternatives you've considered

No response

[isaak654]

How can I rename SbieDll to avoid detection by the program?

You can find references and cross-references about it in #2880

And since I can generally build this project, there are no build instructions and it makes it very difficult to work with this project?

• Build instructions and content related to Sandboxie Classic:
  https://github.com/sandboxie-plus/Sandboxie/blob/master/Sandboxie/ReadMe.md
  https://github.com/sandboxie-plus/Sandboxie/blob/master/Sandboxie/install/ReadMe.md
  https://github.com/sandboxie-plus/Sandboxie/blob/master/LICENSE.Classic

• Build instructions and content related to Sandboxie Plus:
  https://github.com/sandboxie-plus/Sandboxie/blob/master/SandboxiePlus/ReadMe.md
  https://github.com/sandboxie-plus/Sandboxie/tree/master/Installer
  https://github.com/sandboxie-plus/Sandboxie/blob/master/LICENSE.Plus

• Documentation category and related labels:
  https://github.com/sandboxie-plus/Sandboxie/discussions/categories/documentation-and-notes
  https://github.com/sandboxie-plus/Sandboxie/issues?q=label%3A%22build+issue%22
  https://github.com/sandboxie-plus/Sandboxie/issues?q=label%3A%22documentation%22

• More build instructions #3092

If you're interested about adding further documentation content in the repository files, please provide a detailed explanation or a pull request of how this should be done from your perspective.

[H4CK3R0FF1C14L]

Old instructions with version typos

* Build instructions and content related to Sandboxie Plus:
https://docs.google.com/document/d/1iUZVUnfwpmGdj_m6_MZ3SVn4756jOk14FQ0sfek0TTI

There are no problems with building Sandboxie itself, but Sandboxie-Plus gives me QT-related errors. I first installed QT 5.12.x which is specified in this document, but found that there is no msvc 2019, other sources specify version 5.15, as well as in the yaml file from Github Actions also specified version 5.15, I installed it, downloaded the plugin for VS 2019, added, but still get errors related to QT but different.

Error	C1083	Cannot open include file: 'QtWin': No such file or directory SandMan 
\Sandboxie\SandboxiePlus\SandMan\Helpers\WinHelper.cpp	

Also in the Sandboxie-Plus folder there are cmd files that are used in the GitHub Actions yaml file and I don't really understand what they are for, as running install_jom.cmd I obviously don't do what I should, I get the QT folder on the desktop, then running qmake_plus.cmd it gives errors related to the fact that it can't find some QT files (most likely the ones I have installed on my C drive, but it looks for them inside the same folder). I would like to know more about the Sandboxie-Plus build, as it causes a lot of problems for me.

[H4CK3R0FF1C14L]

I installed QT version 6.3.x and was able to build Sandboxie-Plus under x64, but there is no msvc2019 under x32 which makes it impossible for me to build the x32 version. And as far as I understand using QT 6 version Sandboxie-Plus will not work on older Windows versions.

5>SandMan.vcxproj -> C:\Users\donet\Desktop\Sandboxie\SandboxiePlus\x64\Release\SandMan.exe
5>Done building project "SandMan.vcxproj".
========== Build: 5 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

[offhub]

version 5.15, I installed it, downloaded the plugin for VS 2019, added, but still get errors related to QT but different.

Error	C1083	Cannot open include file: 'QtWin': No such file or directory SandMan 
\Sandboxie\SandboxiePlus\SandMan\Helpers\WinHelper.cpp	

For Qt 5.15
Visual Studio 2022 -> SandMan -> Properties -> Configuration Properties ->
Qt Project Settings -> QtModules -> Click the down arrow next to it to open the Select Modules window ->
Select the WindowsExtras module from the window that opens > OK

Note

Menus may differ in the 2019 version.

[isaak654]

version 5.15, I installed it, downloaded the plugin for VS 2019, added, but still get errors related to QT but different.

Error	C1083	Cannot open include file: 'QtWin': No such file or directory SandMan 
\Sandboxie\SandboxiePlus\SandMan\Helpers\WinHelper.cpp	

You can also try with commit 251d7cc

I'm not sure why winextras was not included in master, is a new pull request needed?

[H4CK3R0FF1C14L]

Yes, this fixes an issue with a build using QT version 5.15.x. Now it remains to figure out how to rename the SbieDll library to a different name.

You can also try with commit 251d7cc

[H4CK3R0FF1C14L]

I have renamed all .vcproj, .h, .rc, .cpp files wherever I can find "SbieDll.dll" and "SbieDll.lib" but I seem to be missing something. The application is fully built via Github Actions (except for the ARM version) but I get this error when I try to run anything through the sandbox.

[isaak654]

There is a dedicated troubleshooting wizard for SBIE2181, which can be useful for non-standard Sandboxie installation paths:

• All browsers do not work in sandboxie #3503 (comment)

[H4CK3R0FF1C14L]

• All browsers do not work in sandboxie #3503 (comment)

This doesn't solve the problem, when I try to launch anything, I have Start.exe appear for a second in my box and disappear after a second, not even the application selection window appears.

[isaak654]

What is your Windows version?

[H4CK3R0FF1C14L]

What is your Windows version?

Windows 11 Pro 22H2

I think the problem is due to the fact that I renamed SbieDll.dll incorrectly, because the normal version worked without problems. But I don't know what else I should rename so that SbieDll.dll has a different name and it doesn't cause any problems.

[H4CK3R0FF1C14L]

It seems that I'm just an idiot who accidentally using CTRL + H in the code editor, replaced also the name of the file sbiedll.h because of which nothing worked (it's strange that it was built under x86/64 but under ARM it gave an error, which I didn't care about because I don't own ARM devices). Also I forgot to change the field in my_headers.h (although actually I remember that I changed it, but apparently I forgot to save it).

ARM version still does not build because it is missing some make file, but it does not matter in general. XD

[isaak654]

ARM version still does not build because it is missing some make file

This has recently been fixed with commit f8377e1