Contact Us2020-10-26T10:39:30-07:00

Have more questions?

Contact us and we’ll get back to you ASAP!

This site is protected by reCAPTCHA and the
Google Privacy Policy and Terms of Service apply.

Or Contact Us Directly

aiden Headquarters

Can’t find what you’re looking for?

Maybe these will help!

How to receive RSS update notifications for new packages and more2020-10-15T15:02:36-07:00

Subscribe to our RSS feeds to receive updates for packages, OS builds, and more.

On Windows machines, click one of the following links to subscribe with Outlook or your default RSS reader

For all other platforms, copy one of the following URLs into your RSS reader

Exit Codes2020-10-14T16:18:02-07:00

Some application packages have unique exit codes, which are described in the application package catalog.  In general,
100-199 are prerequisite failures
200-299 are installation failures, and
300-399 are validation failures.

Code Description
0 The package ran successfully
100 Unsupported OS version
101 Unsupported OS architecture
102 Invalid verbosity mode
104 Aborting installation; unsafe conditions
105 Invalid command line argument
106 Unsupported hardware
195 Cannot find license file
196 Invalid license file
197 Invalid license file
198 Unauthorized computer or network
199 The license has expired
200 Failed to run the installer
201 Failed to extract the answer file
202 Failed to cache the package to the local disk
203 Failed to extract the installer
271 Failed to find the font directory
272 Failed to find a valid font
273 Failed to build a list of font files
274 Failed to create the temp directory
275 Failed to extract the font installer
276 Failed to run the font installer
277 Failed to install one or more fonts
280 File extraction error: The specified archive file does not exist
281 File extraction error: Unable to delete the extraction directory
282 File extraction error: Unable to create the extraction directory
283 File extraction error: Failed to run the extraction tool
284 File extraction error: One or more files were not extracted
285 File extraction error: Fatal error
286 File extraction error: Command line error
287 File extraction error: Not enough memory for operation
288 File extraction error: User stopped the process
289 File extraction error: Unknown error
3017 A restart is required before installing

Microsoft Installer (MSI) exit codes are described below.
Source: https://docs.microsoft.com/en-us/windows/desktop/Msi/error-codes

Code Description
0 ERROR_SUCCESS
The action completed successfully.
13 ERROR_INVALID_DATA
The data is invalid.
87 ERROR_INVALID_PARAMETER
One of the parameters was invalid.
120 ERROR_CALL_NOT_IMPLEMENTED
This value is returned when a custom action attempts to call a function that cannot be called from custom actions. The function returns the value ERROR_CALL_NOT_IMPLEMENTED. Available beginning with Windows Installer version 3.0.
1259 ERROR_APPHELP_BLOCK
If Windows Installer determines a product may be incompatible with the current operating system, it displays a
1601 ERROR_INSTALL_SERVICE_FAILURE
The Windows Installer service could not be accessed. Contact your support personnel to verify that the Windows Installer service is properly registered.
1602 ERROR_INSTALL_USEREXIT
The user cancels installation.
1603 ERROR_INSTALL_FAILURE
A fatal error occurred during installation.
1604 ERROR_INSTALL_SUSPEND
Installation suspended, incomplete.
1605 ERROR_UNKNOWN_PRODUCT
This action is only valid for products that are currently installed.
1606 ERROR_UNKNOWN_FEATURE
The feature identifier is not registered.
1607 ERROR_UNKNOWN_COMPONENT
The component identifier is not registered.
1608 ERROR_UNKNOWN_PROPERTY
This is an unknown property.
1609 ERROR_INVALID_HANDLE_STATE
The handle is in an invalid state.
1610 ERROR_BAD_CONFIGURATION
The configuration data for this product is corrupt. Contact your support personnel.
1611 ERROR_INDEX_ABSENT
The component qualifier not present.
1612 ERROR_INSTALL_SOURCE_ABSENT
The installation source for this product is not available. Verify that the source exists and that you can access it.
1613 ERROR_INSTALL_PACKAGE_VERSION
This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service.
1614 ERROR_PRODUCT_UNINSTALLED
The product is uninstalled.
1615 ERROR_BAD_QUERY_SYNTAX
The SQL query syntax is invalid or unsupported.
1616 ERROR_INVALID_FIELD
The record field does not exist.
1618 ERROR_INSTALL_ALREADY_RUNNING
Another installation is already in progress. Complete that installation before proceeding with this install.For information about the mutex, see _MSIExecute Mutex.
1619 ERROR_INSTALL_PACKAGE_OPEN_FAILED
This installation package could not be opened. Verify that the package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer package.
1620 ERROR_INSTALL_PACKAGE_INVALID
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
1621 ERROR_INSTALL_UI_FAILURE
There was an error starting the Windows Installer service user interface. Contact your support personnel.
1622 ERROR_INSTALL_LOG_FAILURE
There was an error opening installation log file. Verify that the specified log file location exists and is writable.
1623 ERROR_INSTALL_LANGUAGE_UNSUPPORTED
This language of this installation package is not supported by your system.
1624 ERROR_INSTALL_TRANSFORM_FAILURE
There was an error applying transforms. Verify that the specified transform paths are valid.
1625 ERROR_INSTALL_PACKAGE_REJECTED
This installation is forbidden by system policy. Contact your system administrator.
1626 ERROR_FUNCTION_NOT_CALLED
The function could not be executed.
1627 ERROR_FUNCTION_FAILED
The function failed during execution.
1628 ERROR_INVALID_TABLE
An invalid or unknown table was specified.
1629 ERROR_DATATYPE_MISMATCH
The data supplied is the wrong type.
1630 ERROR_UNSUPPORTED_TYPE
Data of this type is not supported.
1631 ERROR_CREATE_FAILED
The Windows Installer service failed to start. Contact your support personnel.
1632 ERROR_INSTALL_TEMP_UNWRITABLE
The Temp folder is either full or inaccessible. Verify that the Temp folder exists and that you can write to it.
1633 ERROR_INSTALL_PLATFORM_UNSUPPORTED
This installation package is not supported on this platform. Contact your application vendor.
1634 ERROR_INSTALL_NOTUSED
Component is not used on this machine.
1635 ERROR_PATCH_PACKAGE_OPEN_FAILED
This patch package could not be opened. Verify that the patch package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer patch package.
1636 ERROR_PATCH_PACKAGE_INVALID
This patch package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer patch package.
1637 ERROR_PATCH_PACKAGE_UNSUPPORTED
This patch package cannot be processed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service.
1638 ERROR_PRODUCT_VERSION
Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs in Control Panel.
1639 ERROR_INVALID_COMMAND_LINE
Invalid command line argument. Consult the Windows Installer SDK for detailed command-line help.
1640 ERROR_INSTALL_REMOTE_DISALLOWED
The current user is not permitted to perform installations from a client session of a server running the Terminal Server role service.
1641 ERROR_SUCCESS_REBOOT_INITIATED
The installer has initiated a restart. This message is indicative of a success.
1642 ERROR_PATCH_TARGET_NOT_FOUND
The installer cannot install the upgrade patch because the program being upgraded may be missing or the upgrade patch updates a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.
1643 ERROR_PATCH_PACKAGE_REJECTED
The patch package is not permitted by system policy.
1644 ERROR_INSTALL_TRANSFORM_REJECTED
The patch package is not permitted by system policy.
1645 ERROR_INSTALL_REMOTE_PROHIBITED
Windows Installer does not permit installation from a Remote Desktop Connection.
1646 ERROR_PATCH_REMOVAL_UNSUPPORTED
The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
1647 ERROR_UNKNOWN_PATCH
The patch is not applied to this product. Available beginning with Windows Installer version 3.0.
1648 ERROR_PATCH_NO_SEQUENCE
No valid sequence could be found for the set of patches. Available beginning with Windows Installer version 3.0.
1649 ERROR_PATCH_REMOVAL_DISALLOWED
Patch removal was disallowed by policy. Available beginning with Windows Installer version 3.0.
1650 ERROR_INVALID_PATCH_XML
The XML patch data is invalid. Available beginning with Windows Installer version 3.0.
1651 ERROR_PATCH_MANAGED_ADVERTISED_PRODUCT
Administrative user failed to apply patch for a per-user managed or a per-machine application that is in advertise state. Available beginning with Windows Installer version 3.0.
1652 ERROR_INSTALL_SERVICE_SAFEBOOT
Windows Installer is not accessible when the computer is in Safe Mode. Exit Safe Mode and try again or try using System Restore to return your computer to a previous state. Available beginning with Windows Installer version 4.0.
1653 ERROR_ROLLBACK_DISABLED
Could not perform a multiple-package transaction because rollback has been disabled. Multiple-Package Installations cannot run if rollback is disabled. Available beginning with Windows Installer version 4.5.
1654 ERROR_INSTALL_REJECTED
The app that you are trying to run is not supported on this version of Windows. A Windows Installer package, patch, or transform that has not been signed by Microsoft cannot be installed on an ARM computer.
3010 ERROR_SUCCESS_REBOOT_REQUIRED
A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run.
How to boot from a USB device or optical media2020-10-14T17:49:38-07:00

When you can’t PXE boot (network boot) because a DHCP relay hasn’t been configured, or because your device doesn’t have an Ethernet adapter, the next best way to set up a PC or server is with a bootable USB device.

Create a bootable USB Flash Drive

  1. Insert a USB flash drive that is OK to wipe
  2. Run the following script:
    \\<ServerName>\MassDeploy\Operating-Systems\Boot\x64\Images\Create-Bootable-USB-Drive.cmd
  3. For UEFI systems, you may need to choose the MBR or GPT option for UEFI

Create a bootable DVD

  1. Burn the following ISO:
    \\<ServerName>\MassDeploy\Operating-Systems\Boot\x64\Images\MassDeploy-WinPE-x64.iso

Manually specifying the server name

While booting from a USB flash drive or optical media, if broadcasts are not reaching the aiden server, you will receive an error “There was a problem initializing WDS mode”.

  1. Close the error message.
  2. Press shift-F10 (or Fn-Shift-F10) to open a command prompt
  3. Type:
    X:\Setup.exe /wds /wdsdiscover /wdsserver:<ServerName>
How to customize start panel layouts for Windows 102020-10-14T17:49:38-07:00

Your aiden Windows 10 builds include a custom Start Panel layout, but you may supply your own layout for any or all Windows 10 builds, by emailing an exported layout to our support staff.

Exporting to an XML file

On any Windows 10 PC, customize the Start Panel as desired. Then, open Windows PowerShell, Command Prompt, and run the following command:

Export-StartLayout -Path “$env:USERPROFILE\Desktop\StartLayout.xml”

Or from a Command Prompt, run the following command:

powershell.exe -Command “Export-StartLayout -Path “$env:USERPROFILE\Desktop\StartLayout.xml””

You should see a file called StartLayout.xml on your desktop. Please email this XML file to your aiden support team, and specify which OS build option(s) it should apply to.
How to use the WIN32_MassDeploy WMI Class to target devices2020-10-14T17:52:30-07:00

The Win32_MassDeploy WMI class can be used to target devices in specific departments or pilot systems. This is especially useful for Group Policy targeting.

Properties

Name: ReleaseChannel
Type: string
Registry path (32-bit): HKEY_LOCAL_MACHINE\SOFTWARE\MassDeploy|ReleaseChannel
This value is often set to “Pilot” while setting up a computer with an “IT” build, but it can also be set manually, or automatically with Group Policy.

Name: TargetConfig
Type: string
Registry path (32-bit): HKEY_LOCAL_MACHINE\SOFTWARE\MassDeploy|TargetConfig
By default, this value will match the build option chosen while setting up a device. e.g. If a PC was set up with an “Accounting” build, the TargetConfig value will be “Accounting” without the quotes.

Installation

The Win32_MassDeploy WMI class is automatically installed by the MassDeploy System Builder, but you can install it manually by running your “MassDeploy Windows Config” package.

Example Group Policy WMI Filters

In the Group Policy Management console, under WMI Filters, create a new filter called “IT Systems“. Add the following query:

SELECT * FROM Win32_MassDeploy WHERE TargetConfig = “IT”

In the Group Policy Management console, under WMI Filters, create a new filter called “Pilot Systems“. Add the following query:

SELECT * FROM Win32_MassDeploy WHERE ReleaseChannel = “Pilot”

Automatically Define Pilot Systems in Group Policy

You can use Group Policy Preferences to automatically define pilot systems, based on where your pilot users log on.

  1. Open the Group Policy Management console
  2. Create a new GPO called “Pilot system Targeting”
  3. Edit the GPO and browse to: User Configuration\Preferences\Windows Settings\Registry
  4. Create a New Registry Item with the following values:
    1. Action: Update
    2. Hive: HKEY_LOCAL_MACHINE
    3. Key Path: SOFTWARE\WOW6432Node\MassDeploy
    4. Value name: ReleaseChannel
    5. Value type: REG_SZ
    6. Value data: Pilot
  5. Under the Common tab, enable “Item-level targeting”
  6. Press the “Targeting…” button
  7. Create a new “WMI Query” item:
    1. Query: SELECT OSArchitecture FROM Win32_OperatingSystem WHERE OSArchitecture = “64-bit”
    2. Namespace: Root\cimv2
  8. Create a new “Security Group” item:
    1. Press the “…” button to find your “pilot users” group
    2. Select the “User in group” radio button
  9. Press OK, and OK again
  10. If you have any 32-bit systems, create another identical Registry Item with the Key Path:
    SOFTWARE\MassDeploy, and
    target OSArchitecture = “32-bit”

Automatically Define Pilot Systems in WSUS

You can use Group Policy to automatically sort computers into a WSUS “Pilot Systems” computer group, instead of manually updating the group each time a pilot user changes or rebuilds their computer.

  1. Open the Group Policy Management console
  2. Create a new GPO called “WSUS Pilot Systems”
  3. In the Scope tab, under WMI Filtering, select “Pilot Systems”
  4. Edit the GPO and browse to: Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Update
  5. Set the following values:
    1. Enable client-side targeting=Enabled
    2. Target group name for this computer=”Pilot Systems”
  6. Open the WSUS admin console
  7. Under <ServerName>\Computers\All Computers, add a computer group called “Pilot Systems”
  8. Under Options\Computers, where “you can specify how to assign computers to groups”, select “Use Group Policy or registry settings on computers”
How to analyze crash dumps / blue screens (BSOD)2020-10-14T17:49:38-07:00

BlueScreenView

This simple free tool, will often find the driver that caused the crash.
http://www.nirsoft.net/utils/blue_screen_view.html

 

How to analyze crash dumps / blue screens (BSOD)

WinDbg

When BlueScreenView does not provide enough information, Microsoft’s Debugging Tools may be needed.
https://msdn.microsoft.com/en-US/library/windows/hardware/ff551063(v=vs.85).aspx

Installation

If you only want to install the Debugging Tools, run the Windows SDK installer, select the Debugging Tools for Windows box, and clear all the other boxes.

Install-Debugging-Tools-for-Windows

Configuration

Symbols

Symbols are used to decode the information held in the memory dump file which allows you to see the function names in the call stack.

  1. Open WinDbg -> File -> Open -> Symbol Search Path
  2. Add the following symbol path and press OK: http://msdl.microsoft.com/download/symbols
  3. To save your configuration for next time, click File -> Save Workspace

WinDbg-Symbol-Search-Path

Opening Crash Dumps

  1. Make sure you have access to your DMP files
    1. Either run WinDbg with an elevated token (Start -> WinDbg -> right-click -> Run as administrator)
    2. Or copy the “C:\Windows\Minidump” directory to a location where you have read access.  e.g. your desktop.
  2. WinDbg -> File -> Open Crash Dump -> Browse to your latest .DMP file
    1. By default, .DMP files are saved in C:\Windows\Minidump\
    2. You may also find C:\Windows\MEMORY.DMP
  3. Let the analysis run.  It may take 10 or more minutes to complete.

WinDbg-Bugcheck-Analysis

Go to Top