New in version 3.1

The following new features and bug fixes have been implemented in version 3.1 of the Packaging PowerBench:

New features


DSM script commands that have been newly implemented


Changes / enhancements to existing commands
  • The Remove-Directory command now has an option to also delete directories if they are not empty.
  • The Invoke-Goto command now has an option to be executed during package uninstall.
  • For the Uninstall-MsiProduct command, "Silent" is now the default selection for "UI level" when creating a new entry, so by default there is no prompt to uninstall the product when it is executed.
  • The Test-Platform condition can now also check for "Windows 11" and "Windows Server 2022".


The following bugs and problems from version 3.0 have been fixed
  • When creating a new package from the Backstage view, the package was not opened.
  • In expert mode, the "Replace with:" text box was disabled in the Find and Replace dialog.
  • In expert mode the ribbon button "Delete Entry" was disabled.
  • The "Test-InstallMode -InstallComputerPart" check incorrectly returned True when "InstallUserPart" was specified as the installation mode.
  • Icons could not be specified for the "New-Link" and "New-InternetLink" commands.
  • When opening a package created with a previous version, the Common Runtime Files were not updated if the "TemplateIncludePath" entered in the Package.xml did not (no longer) exist.
  • In the file directory selection dialog wrong results were returned if the input mode (the variable representation) was not "Simplified PowerShell".
  • The package installation aborted undefined if the file "Package.Defaults.xml" was not present.
  • When imported Winget packages had multi-line descriptions, only the first line was formatted as comment, the other lines were incorrectly not commented out.
  • The DSM package template did not check for return code 60001 and DSM packages therefore became compliant even though the called PPB package terminated with this error code.
  • When installing PPB packages via the Microsoft Company Portal that were called with the RestartInteractive parameter, the installation was initially logged as failed.
  • When using user authentication mode for Intune publishing, the PPB would sometimes hang and waited for authentication without timeout.
  • For nested blocks, when the outer block was commented out, the code disappeared if a block comment already existed in the inner block (e.g., for nested If blocks).
  • It could happen that line breaks were incorrectly assigned in the generated PowerShell code when indenting and outdenting lines and blocks in standard mode.
  • When uninstalling MSI packages, the uninstallation stopped by default with a prompt "Do you really want to uninstall xyz".
  • For scripts that contained more than 100 lines, the PPB froze when scrolling in expert mode during the transition from two- to three-digit line numbers.
  • If a PPB package was executed in the context of the system account that contained a Start-ProgramAs or Invoke-ScriptAs command to invoke a process in another user context, this call failed.


Miscellaneous
  • The PAExec auxiliary tool used for executing the Start-ProgramAs and Invoke-ScriptAs commands has been updated to version 1.29.