DriveDX is not a login item per se. Neither is it a LaunchAgent or LaunchDaemon. To the best of my knowledge its launch mechanism is unique. Embedded in the DriveDX application package there as an executable named DriveDXLoginItemHelper I suspect is the trigger, but I have no idea how it works or why it is launched in this unique manner. confused

As to the launch order, I really have no way of accurately determining the actual launch order, but there are breadcrumbs that lead me to believe it is working and has resolved a couple of minor launchtime annoyances.


"All you've got to do is own up to your ignorance
honestly, and you'll find people who are eager to
fill your head with information"
--Walt Disney