Loading...
Loading...
Affected Products: Dell Device Manager Console Issue occurs under the following conditions: The ACL owner of the C:\ProgramData\Dell folder is SYSTEM The drivers subfolder within C:\ProgramData\Dell is not present The user attempts to install a DUP based on the 5.4.1 framework in ADMIN mode Note: This situation is most likely to occur on freshly imaged computers where no previous DUP installations have been performed. In typical environments, the installation proceeds without any issues. These issues are exclusive to this version and do not affect earlier or later releases.
During installation, the DUP checks folder ACL permissions to ensure appropriate access and the absence of symbolic links. As part of this validation, it resets permissions on the Dell folder. In the scenario described, the Dell folder is owned by SYSTEM , and the DUP is run under an Admin context. Initially, the process can remove existing ACL entries due to Admin's full control. Once those permissions are removed, the process lacks the necessary rights to set new ACL entries, due to ACL owner not having sufficient privileges. The DUP fails to create the drivers folder required for driver extraction, resulting in an installation error.
Note: Do not create a work order for any hardware replacement for this issue. Workaround: Open Command Prompt with admin privileges using psexec.exe In the Command Prompt, go to the folder where the DUP is located Run the DUP, this restores the original permissions and allows the installation to complete successfully Long-Term solution: Later versions of the DUP framework have been enhanced to handle this scenario. These versions no longer reset permissions to the Dell folder, repackaging the DUP originally built with version 5.4.1 using a newer framework resolves the issue, as it avoids altering folder permissions.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.