Key Changes in SetupBuilder 2025 and important Information

Apologies, everyone! The instructions for SetupBuilder 2025 aren’t fully completed yet. Our main goal was to release the beta today, and we’ve done that! Updated documentation will be available in the next beta build, with more detailed info coming over the next few days. Need help or have questions? Feel free to reach out to me directly at friedrich@lindersoft.com.


* Custom Code-Signing for Web Update Clients

SetupBuilder 2025 no longer includes pre-signed wupdate*.exe and wucheck*.exe web update clients. To comply with updated CA/B Forum regulations, developers must now use their own code-signing certificates to sign these clients. The source code for these clients remains available, allowing full customization and compliance with modern security standards.

This change ensures greater flexibility and security, aligning with industry best practices for trusted software distribution.

* Secure Downloads in the IDE

SetupBuilder 2025's Integrated Development Environment now exclusively uses secure HTTPS downloads via the setupbuilder.com domain, replacing non-secure protocols. This enhancement strengthens the security of file transfers, ensuring safer and more reliable interactions with the SetupBuilder ecosystem.

* Updated Core PreRequisites Support

SetupBuilder 2025 discontinues support for outdated Core PreRequisites to streamline compatibility with modern systems. Currently, only the Microsoft C++ 2013 runtime is included, with additional standard PreRequisites planned for the beta phase. Users can seamlessly utilize PreRequisites from prior SetupBuilder versions by copying them into the "Runtimes" folder, ensuring flexibility and backward compatibility.

* Evolving Documentation and Support

SetupBuilder 2025 is actively developing its updated documentation, new project examples, and a dedicated support channel. These resources are currently under construction, with enhancements planned to provide users with comprehensive guidance and improved support throughout the beta phase and beyond.

* Enhanced Code-Signing Security

In the final (Gold) release of SetupBuilder 2025, all components will be code-signed using a secure EV SHA-256 certificate, replacing the outdated SHA-1 standard due to its vulnerability to collision attacks. During the beta phase, some files remain signed with SHA-1, but this will transition fully to SHA-256 by the official release, ensuring robust security and compliance with modern standards.

* Enhanced Code-Signing Security

In the final (Gold) release of SetupBuilder 2025, all components will be code-signed using a secure EV SHA-256 certificate, replacing the outdated SHA-1 standard due to its vulnerability to collision attacks. During the beta phase, some files remain signed with SHA-1, but this will transition fully to SHA-256 by the official release, ensuring robust security and compliance with modern standards.

* Safe Testing Environment with Windows Sandbox

SetupBuilder 2025 introduces a Safe Testing Environment, allowing users to test installation packages in a fast, isolated Windows Sandbox on Windows 10 or 11 Pro/Enterprise/Education. This feature enables safe compatibility checks without risking your primary system, providing a secure and efficient way to validate software installations.

How to Enable Windows Sandbox:

1. Ensure you are running Windows 10 or 11 Pro, Enterprise, or Education (Sandbox is not available in Home editions).
2. Open the Windows Search bar and type "Turn Windows features on or off."
3. In the "Windows Features" window, scroll down and check the box for Windows Sandbox.
4. Click OK, then restart your computer when prompted.
5. After rebooting, search for "Windows Sandbox" in the Start menu and launch it to begin testing in an isolated environment.
6. Compile your project and then select IDE -> Build -> Run Installer in Windows Sandbox
Note: Your system must support virtualization, and it should be enabled in the BIOS/UEFI settings. For detailed requirements, refer to Microsoft?s documentation.

* Advanced Code-Signing Support

SetupBuilder 2025 introduces robust support for state-of-the-art code-signing methods, enhancing security and compliance. New built-in support includes eTokens (non-SafeNet and SafeNet), Microsoft Trusted Signing, and (Certum) Cloud Signing, providing developers with flexible, modern options for secure software authentication.

* Regular Beta Phase Updates and Insights

During the SetupBuilder 2025 beta phase, we will regularly share information, tips, and tricks to enhance your testing experience. The beta period will also serve as an opportunity for us to deepen our understanding of the system, identify potential issues, and address common questions, ensuring a more robust final release.

* Modernized Installer Interface

SetupBuilder 2025 introduces a sleek, contemporary design for the installer, offering a visually appealing and updated user experience. Note that the dimensions of the side and top banner bitmaps have changed to accommodate this modern style, so existing graphics may need adjustment.

* Beta Phase Update Process

During the beta phase, SetupBuilder 2025 will not support updates via the Web Update channel. Instead, full-featured update installers will be provided to ensure users receive comprehensive and reliable updates throughout the testing period.

Beta Note: SetupBuilder 2025 is BETA software. Despite thorough testing, unknown bugs may still occur. Please report any issues encountered.