DeployMaster 4.2.1 Crack & License Key 2020
Forum continued to use the old proxy settings until you closed the forum window if you changed the proxy settings after having successfully connected to the forum. Command line parameters are not passed to 3rd party installers. MSI installers are not run silently when your installer is run silently.
Some combinations of identity settings were not handled correctly while building the installer, causing the installer to skip asking for identity information if no support DLL with identity routines was provided, or to ask for all information if it was. Unregistering DLLs caused command prompt windows to briefly flash on the screen. In particular. Detect and install version 4. NET framework. Windows 8 option to specify whether to allow your installer to be run on Windows 8 or not.
F2 key now allows you to edit items on the Files page and Registry page as could previously be done by clicking twice slowly. The shortcut to the uninstaller should not appear on the start screen on Windows 8.
Building the installer creates the output folder if it does not yet exist instead of failing to write the installer. Building the installer without saving the. Application icon is now used to list the application in the Programs and Features applet in the Window Control Panel if you add the same icon as a file on the Files page. Otherwise, the icon for the desktop shortcut is used as in previous versions of DeployMaster. Terminate with an exit code that indicates whether there were any warnings, non-fatal errors or fatal errors when building from the command line with DeployMasterCmd.
Silent installs failed with an error claiming insufficient access rights when run from an account with full administrator privileges that does not require elevation on a system with UAC enabled, such as the Administrator account on Windows Server Version 4. Silent installs of installers built with version 4. Rebuilding your installer with version 4. The button to delete messages is now labeled Cancel for messages that are being edited, to make it more obvious that this button deletes the edited message, but leaves the original message in place.
Do not show an error about the file name of the generated setup being the same as that of a 3rd party setup when one of the. NET options is selected but no. NET installer is specified and one of the file names for the setups to generate on the Media tab is blank.
If one of the. NET versions was selected and a. NET installer file was specified but no. Search box did not work. License key was not installed when installing DeployMaster 4. Errors with signing. Not signing. When typing a full path with a drive letter as the installation folder for a portable install, automatically select that drive in the list so that the installation will be created on that drive instead of the drive that was previously selected in the list.
Disabled context-sensitive help in the bit version of DeployMaster if Internet Explorer 9 is installed. IE 9 causes all bit applications that use a. Installer crashed on startup when the option to require a previous version to be installed was turned on. Activating the Media tab caused the setup to be marked as modified, enabling the Save button and resulting in a question to save unsaved changes when closing DeployMaster even if no changes were made to the setup 4.
If the same file name is specified for both the installer with integrated 3rd party installers and the one without, refuse to build the installers and show a clear error message instead of failing to properly write the installers at the end of the build.
Files that needed to be replaced upon reboot had their names shortened to 8. The installer would not proceed beyond the welcome screen except for portable installations on Windows Server if the user was logged on as an actual Administrator as opposed to a user with administrative privileges and User Account Control UAC was enabled 4.
If the installer allowed portable installations and the application was already installed on the hard disk and the user running the installer did not have sufficient access rights to update the installation on the hard disk, a message saying that a previous version was already installed was overlaid on top of the message saying only portable installations were possible.
Now the setup will only say that only portable installations are possible. Turning on the option to cover the screen background caused DeployMaster to get stuck behind the background. This only happened on Windows 7 and only in the DeployMaster Builder.
The setup with integrated 3rd party installers always claimed to be damaged if you requested both a setup with 3rd party packages and a setup without 3rd party packages to be built at the same time. If the setup covered the screen background and needed elevation on Windows Vista or Windows 7 then it showed a harmless error message about not being able to focus a window.
Waiting for executables that are run as part of the installation is now optional. Language files are now saved as Unicode, so characters in all scripts are properly preserved. If a previous version was already installed, the welcome screen of the installer indicated that the current version was already installed rather than the previous version 4.
Command line: Option for each. This can be used to register. Option to make a folder writable by all users on Windows Vista and 7. Option to mark files as bit or bit or both when creating installers that support both bit and bit Windows. Forum that can be accessed from within DeployMaster via the Help menu. Automatic code signing for the setup. Specify window caption or class name for DeployMaster to test whether the application is still running so it can prevent the installation if it is.
Files that turn out to be incompressible or barely compressible are now stored uncompressed in the setup. LZMA compression. Use all available CPU cores to compress files. No restriction on the maximum size of each file or the total size of all files in the setup, even when creating a bit setup. The size of each file added to the setup and the total size of the setup is no longer limited to 2 GB. Open start menu and run installed application without administrator privileges. Choices to have a single.
File masks for files that DeployMaster should not attempt to compress because they will likely turn out to be incompressible, e. Check for truncated and damaged setups before starting the installation.
Use all CPU cores to decompress files if the setup is not split into multiple disks. Request elevation when starting the actual installation rather than before the setup starts. That allows portable installations to be created by users without administrative privileges. DeployMaster 3. Creating portable installations sometimes failed if the setup included shortcuts to files or URLs which are ignored for portable installs.
Files that were in use during installation were not correctly scheduled to be replaced at reboot. Progress meter in the installer was not updated while copying files.
Show the option to call regsvr32 for. Save only the 32×32 icon into the setup rather than the whole. Other sizes only take up needless space, and Vista-style icons can cause errors. You can now select an. DeployMaster will extract the 32×32 size of the first icon from the file and put just the icon into the setup. Selecting and deselecting components in the installer can now be done by pressing the space bar on the keyboard.
If this happens, that likely indicates a bug in the DLL or that the DLL is incompatible with the version of Windows it is being installed on. Warn if the file name of a 3rd party setup is the same as the file names on the Media tab. That causes DeployMaster to see its own setup. Use regsrv Turning the option to create an autorun. Language files are now saved in the application data folder under your Windows user profile instead of in Program Files, so they can be modified without administrator rights.
Installing version 3. Windows 7: Setup programs created with DeployMaster and their uninstallers now contain a manifest that advertises Windows 7 compatibility to prevent false warnings from the Program Compatibility Assistant on Windows 7. If the last 3rd party package was one to be skipped new ability in version 3. If a 3rd party setup does not specify a download URL, installation detection file, or installation detection registry key, and the 3rd Party setup is not included in the installation package created by DeployMaster, then the installation package no longer prompts that the 3rd party setup needs to be installed.
Confirming the installation by checking a registry value did not work correctly. Only checking a registry key without checking a value worked correctly. Clicking the Shortcuts sometimes get. PIF instead of. LNK extension. In that case, the uninstaller did not properly delete the shortcut. Base the file name of the temporary installer previously dpy. Create portable installations even if the user does not have administrator rights. More sample translations on the Language tab.
Shortcuts to console applications ran the application invisibly. It also indicates the combined size of the 3rd party setups. If the 3rd party installation program could not be found while building the installer, the build was aborted with a string build error, instead of completing the build without embedding that installer and showing a warning about that. If you specified a file name for the complete setup package with integrated 3rd party installers on the Media tab, but not for the setup without 3rd party installers, DeployMaster would generate a faulty setup.
Also, the Test Installation Program button showed the folder containing the setup program instead of starting the setup. Specifying a URL other than the default for downloading the. NET framework caused the link in the installation program to point to http: Ability to detect and install the. NET framework, either from dotnetfx. Ability to run 3rd party installers before the DeployMaster installation. The 3rd party installer can be included inside the self-extracting setup created with DeployMaster, or copied separately along with the DeployMaster setup.
Create Portable Installation: Advanced Options should not allow empty folders to be specified, or syntactically incorrect paths to be used. It should force the user to correct the paths before proceeding. If the target file already exists, clear its read only attribute if it is set, so the file can be overwritten.
The installer now warns if available disk space is insufficient. Checkboxes and buttons in dialog boxes no longer disappear when you press the Alt key. Additional strings were added on the Language tab. DeployMaster 2. Though DeployMaster 2. We have fully tested it with the final release of Windows Vista, and found it fully compatible. The new Vista-compatible uninstaller introduced in version 2.
Setup packages built with 2. Checkboxes now blend in better with the gradient background Setup: The installer and uninstaller now contain a manifest telling Windows Vista they need administrator privileges Setup: Select the font the installer should use.
Double byte character set compatibility. The second byte of certain characters in Far East languages was interpreted as a backslash by DeployMaster Finished: This prevents multiple uninstall shortcuts if you turn off the option to delete obsolete files on the Update page.
Print button below the readme and the license agreement in the setup program is now hidden when no printer has been installed. When browsing for an installation folder in the setup program, the user can now browse through network neighborhood. The select components button was not displayed by the setup program if the first component was not user-selectable version 2.
File Types: The option to register. TLB files was not preserved when saving and reloading a setup script. Command line option to save the build results when building from the command line; e. The select components button was never displayed by the setup program, even if there were selectable components Silent installation caused the installation to fail with an access violation if the installer used a background covering the entire screen which is invisible during a silent installation DeployMaster 2.
Installation of a patch installer new capability of version 2. Update page: These are installation packages that contain only files that are new or different from those shipped in a previous version of the software.
DeployMaster will check whether a proper previous version of the software is already installed, before installing the patch. If not, DeployMaster will show a message that you provide e. Identity page: As an alternative to creating a support DLL to store and validate identity information such as serial numbers, DeployMaster can now automatically store this information into the registry and do simple verification of serial mumbers, etc.
Files page: Option to never uninstall certain files. These files will stay behind, even after your software is uninstalled.
Media page: Installation packages can now be split across multiple CDs, or split into parts of any size to your liking. Appearance page: Option to hide the Advanced Options Installation button. Except for the first one, these problems occur only in very few situations.
The second user will then be able to install for themselves as well as install for all users. If the second user installs for all users, the first user will still be able to update or uninstall their user-specific installation. Because DeployMaster now differentiates between all-user and user-specific installs, it imposes some new restrictions on the folders that you can use. These folders are user-specific folders and are not easily accessible to other users on the same PC.
These folders are shared between all users. They are shared between all users and require admin rights to write to. DeployMaster will permit you to use them for user-specific installs, however, if you turn on the option to require admin rights for installations for the current user. Doing so is not recommended as it mostly defeats the purpose of allowing user-specific installs. This option is mainly provided to allow you to deal with poor decisions made in the past.
This combination of options will also allow installations made with DeployMaster 5. There are also new restrictions on registry keys. If that succeeds, it is running from a user-specific install. Keys you place there are created for all user accounts.
This will allow the uninstaller to clean up those registry keys for all users. If you just want upgrade to DeployMaster 6 and keep your installer working the way it always has, just open your. If you did, switch to the Project page. Cut and paste the default installation folders from the left hand side to the right hand side.
Then rebuild. Either way, your new installer will correctly upgrade existing installations. Since you had to switch because you were using user-specific folders or registry keys, your installation was never really correct for all users anyway.
On a PC used by a single person with a single account, that person will not see any difference between an install for all users or an install for the current user with admin rights. DeployMaster itself can now be installed for the current user without admin privileges. It can still be installed for all users like before.
The Advanced Installation now allows you to choose in which folder DeployMaster should place the. On the Update page, you can now have your installer expire on a specific date or a certain number of days after the release date.
This can be useful to prevent prospective customers from making a decision based on an outdated trial version. If you sell software on a subscription basis, you can prevent accidental installs of outdated versions. You can customize the message shown by an expired installer to explain where the user can get the latest version. This feature is intended to prevent the user from wasting their time installing obsolete software. It can be easily bypassed by fiddling with the system clock.
If you really need your software to stop working after a certain date, you need to add such protection to the application itself. You can specify this font on the Appearance page. The progress meter in the installer no longer updates itself for each and every file when very small files are being installed as this needlessly slowed down the installation.
On the 3rd Party page, you can now specify. These are documented in the topic about the Media page where you can use the same placeholders in file and folder names. The checkboxes for selecting file associations during an advanced options installation now scale correctly on high DPI systems.
This means that if your installers no longer need to support XP or Vista, then you can continue using Windows 7 to build installers with digital signatures that will be accepted by Windows 10 after January 1st, We previously believed Windows 7 could not apply RFC timestamps.
It can, but the function needed for that on Windows 7 is documented incorrectly by Microsoft, causing a crash when called as documented. Windows 10 will require SHA time stamps for downloaded files on January 1st, This means Windows 10 will consider the download unsigned when the certificate used to apply the signature expires. You will never get this warning if you build your installer on Windows 8 or later, as Windows 8 and later can apply dual signatures if needed.
If you build on Windows 7, you will get this warning if you select Windows 10 as well as XP or Vista on the Platform page. The installer will still be built successfully and will still be signed and timestamped with SHA-1 when this warning or error appears. As of January 1st, , you need an Authenticode certificate based on SHA to build installers with digital signatures that will be accepted by Windows 7 and later. If you purchased your certificate in or , then you likely already have a SHA certificate.
Older certificates are likely still based on SHA To check this, open Windows Explorer and right-click on an. Click on the Digital Signatures tab. To check your certificate, click the Details button. Then click the View Certificate button. Then click the Details tab. In that case, you need to obtain a new certificate. The replacement certificate will automatically use SHA SHA-1 certificates are no longer issued. Since Windows and prior do not display any warnings based on digital signatures and only support versions of Internet Explorer that do not display such warnings, this is not really a problem.
So DeployMaster can still generate a single installer that works on Windows 98 through Windows DeployMaster itself now requires Windows XP or later to run. Windows is no longer supported. DeployMaster 4. It can do so using an SHA certificate. Like many others, we previously believed that SHA-1 signatures would not be accepted by Windows 7 and later unless timestamped prior to January 1st, But this is incorrect.
Windows 7 and later continue to accept SHA-1 signatures. Even MD5 signatures are still accepted. MD5 is considered broken and was never used by DeployMaster. This made DeployMaster itself require Windows 8 or later, as Windows 7 and prior cannot apply dual signatures. If you build on Windows 7 then DeployMaster 5. In other words, DeployMaster 5. So you get the strongest possible signature, without requiring you to upgrade your development system to a newer version of Windows.
RFC timestamps are now applied to digital signatures for Windows 7 and later if you build your installer on Windows 8 or later. DeployMaster requests SHA to be used for the timestamp. Timestamp services are required to support SHA as of January 1st, In our tests, all timestamping services selectable on the Media page do this.
The only exception right now is Geotrust which provides an SHA-1 timestamp. We expect Geotrust to update their timestamping service in the near future. Authenticode timestamps using SHA-1 are still applied to digital signatures for Vista and prior, as they do not recognize RFC timestamps. Authenticode timestamps are also applied when building your installer on Windows 7. SHA-1 timestamps are still accepted by all versions of Windows. Windows 10 will require SHA time stamps for downloaded files on January 1st, next year.
If you are still running Windows 7 and want to provide signed downloads to Windows 10 users, you should get your free upgrade to Windows 10 prior to 29 July This was widely believed but turned out to be incorrect. We removed these release notes to avoid further confusion.
The version history keeps a full record of all the changes that were made. The release notes for 5. Upgrading to DeployMaster 5. On the Build page, there is now an Abort button that allows you to abort the build. The Build button is now disabled during a build, so you can no longer accidentally cause the build to fail by clicking the Build button twice.
The only real change is that the Platform page now has a separate checkbox for Windows Installers created with DeployMaster 4. Installers created with earlier DeployMaster 4. Like Windows 8. Installers created with DeployMaster 3. Installers created with even older versions of DeployMaster released between the years and will have the same issues on Windows 10 as they had on Windows Vista, as they predate Windows Vista and its tighter security system.
On the Project page, there is a new checkbox to skip the license agreement. An installer built with this option does not show its license agreement if the same application is already installed.
The installer for DeployMaster itself uses this option too. Several new command line parameters were added to the installer. If your installer uses a support DLL to define additional installation folders, then those folders can also be changed by using the name of the folder as a command line parameter.
If the software was previously installed, using these command line parameters changes the installation folder, just like the Advanced Options Installation button can be used to change the folders of an existing installation.
In that case, when using the Advanced Options Installation button, the default folders will be those specified on the command line. Selecting different folders via Advanced Options Installation overrides the command line parameters. The setup.
When the stub runs, it extracts the actual installer into the temporary files folder and executes it. Only then does the installer appear on the screen. Running from the temp folder is a legitimate technique that has been used for a long time by installers and self-updating software. But recently some companies have implemented a Software Restriction Policy that blocks executables in the temporary files folder in the belief that this can block malware.
In this situation, installers built with previous releases in DeployMaster fail to run without showing an error message. If your application requires. If you specify that your application requires. NET 3. NET 1. Windows XP2 or later is required for installing. Windows XP3 or later is required for installing. Windows Vista SP2 or later is required for installing. A few bugs were fixed. Without this registry key there are never any issues with pointers beyond 4 GB. On the 3rd Party page , the 4.
This better reflects that only one 4. NET can be present on a PC, and that any application that is compatible with a specific 4. NET is also compatible with all later 4. This is not necessarily the case with. If your application needs. Microsoft released the Windows 10 Technical Preview at the end of last month. Windows 10 pretends to be Windows 8. Windows 10 pretends to be Windows 8 to installers built with DeployMaster 4.
On the Media page , you can now select the time stamping URL that DeployMaster uses to countersign the digital signature on your installer. Previously, DeployMaster always used the Verisign time stamping service. This happens occasionally due to maintenance and network outages. DeployMaster remembers the URL as a global preference. It is not saved into the. This way you only need to select a different URL once if your previous choice stops working.
The new URL will be used for all future builds until you change it again. A couple of bugs were also fixed. Splitting the installer into chunks of a certain size resulted in chunks files without file names if you did not specify a file name for the installer without 3rd-party installers.
On the 3rd Party page , you can specify whether your installer should install the. NET framework. Versions 1. The build of the. NET framework that is included with Windows 8. This build is more recent than the.
Previously DeployMaster incorrectly detected the new. Now, you can use those same placeholders in the background labels that you can specify on the Appearance tab. On the Update page , you can specify window captions that your installer should look for to detect whether your application is still running or not. You can specify multiple captions by delimiting them with semicolons.
Previously, DeployMaster incorrectly treated spaces as delimiters between captions. Now, spaces are treated as literal characters so captions that consist of multiple words can be detected. Since Windows 8. The only change is that the Platform page now has a separate checkbox for Windows 8.
You can use this checkbox to control whether your installer should allow your software to be installed on Windows 8. If you created an installation script with a previous 4. Installers built with previous 4. If Windows 8 was checked on the Platform page then the installer will work on Windows 8. If Windows 8 was not checked on the Platform page, then the installer will not allow installation on Windows 8. The reason for all this is that Windows 8. Installers build with DeployMaster 4.
Installers built with previous versions do not. The best way to get technical support for DeployMaster is via its built-in forum.
You can access it by selecting Help Forum in the menu in DeployMaster. Previously, DeployMaster could connect to the Internet and to the forum if your PC had a direct internet connection or if it could connect through an HTTP proxy that either required no authentication or allowed basic authentication.
You can configure the proxy server via the Proxy button on the login screen to the forum. On the Identity page , some combinations of identity settings were not handled correctly while building the installer, causing the installer to skip asking for identity information if no support DLL with identity routines was provided, or to ask for all information if it was. This bug has existed since DeployMaster 1. It went unnoticed because it is rare for a newer version of an application to have fewer shared files than a previous version, and the option on the Update page to delete such files is off by default.
The bug is acute in DeployMaster 4. If build an installer with DeployMaster 4. This makes it impossible to uninstall those other applications. If you did not turn on the option on the Update page to delete old files, then there is no problem.
The installer for DeployMaster itself had the option to delete files from previous installations on the Update page turned off, so there are no problems with the uninstaller when upgrading DeployMaster itself to version 4. So if you have released installers built with DeployMaster 4. If your installers are built with older versions of DeployMaster, then there is no rush to upgrade though you may still want to do so for the improved Windows 8 support. If you built installers with DeployMaster 4.
It will be replaced with the Application Version Number specified on the Project page. Including the version number in these messages is useful if you have different versions of an application that target different versions of Windows.
The most obvious change in Windows 8 is that the Start Menu that was introduced with Windows 95 has been replaced with a Start Screen. This is what happens on Windows 8 to shortcuts created by installers built with DeployMaster 4. This option allows you to tell Windows 8 what to do with the shortcut when your application is first installed.
You can choose the default behavior, or you can choose not to pin the shortcut by default, or you can force the shortcut to be pinned. If your installer adds shortcuts for utility applications, you may want to choose not to pin those. If your installer installs only document files, meaning nothing would get pinned by default, you may want to force the main document to be pinned. Windows 8 only respects this option upon first installation. If you want to test this feature, you need to do so on a copy of Windows 8 on which your software was never installed.
A virtual machine is probably the best way to do this. If you turn on the option to create a shortcut to the uninstaller on the Finished page, then DeployMaster will automatically tell Windows 8 not to pin that shortcut. If multiple applications are installed into the same folder, they will share a single copy of the uninstaller.
On the Media page, you can now choose between faster or stronger compression, or no compression at all. Version 4. Silent installs of installers built with version 4. Rebuilding your installer with version 4. Because of the latter bug, the installer for the licensed version of DeployMaster 4. If you created installers with DeployMaster 4.
On the 3rd Party tab, if you selected one of the. NET versions and you specified a. NET installer file but you did not specify a. If your installer needs. If you click this link in your browser, it will list all. NET versions that DeployMaster supports. But when this link is launched from your installer, it will list only the. NET version that your installer needs. Also on the 3rd Party tab, selecting one of the.
NET options without specifying a. NET installer no longer causes an error about the file name of the generated setup being the same as that of a 3rd party setup when one of the file names for the setups to generate on the Media tab is blank. If any of those. The Build tab will still display an error message, but the error is no longer treated as fatal Not signing.
If you paste that link into a message on the forum, it will now be highlighted as a link. Double-clicking the link will activate the message. DeployMaster uses a. This is the standard help system for modern Windows applications. Due to a bug in Internet Explorer 9, if a bit application requests context-sensitive help using a. On the Update page you can configure your installer to require a previous version of your application to be installed.