![]() ![]() The following are some Microsoft Articles which describe different Microsoft Installer error codes: Note, this is NOT done by default (see image below).įor a comprehensive list of Windows system error codes, see (v=vs.85).aspx. In these Uninstall cases it is common to add the code 1605 to the Return Codes field. We recommend using the Command Step to uninstall an application that was installed via MSI. Note: For information on configuring success codes in Command step properties, see Command Step Properties. This return code means the installation requires a reboot but a reboot was NOT initiated. This return code means that the installation required the target to reboot AND that a reboot was initiated. All other product and company names are the property of their respective owners.This is (almost always) considered successful and should be treated as such except in very rare cases. PDQ.com is a trademark of PDQ.com Corporation. IMPORTANT: Debug events should be enabled only as directed by PDQ Support. Logs events that are used for troubleshooting. Logs events that indicate a significant, successful operation. Logs events that indicate a potential problem. ![]() Logs events that indicate a significant problem the PDQ Deploy administrator should act on usually a loss of functionality or data. ![]() For more information on how PDQ.com encrypts passwords, see Credentials. Passwords are not included in any data sent to PDQ.com. IMPORTANT: Any information that could be used for identification will be anonymous including, but not limited to, IP addresses, MAC addresses, domains, computer names, hostnames, and user names. Prior to submitting a ticket, the diagnostic details being sent are available in that window for review. The only time PDQ.com will receive exception/diagnostic data that is not anonymous is when the Submit a Support Ticket window is used to create a support ticket with us. Allows you to opt-in or opt-out of sending anonymous exception/diagnostic data to PDQ.com to improve the products, identify trends, and ideally fix bugs before they ever reach you. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |