So, you're looking to get Adobe Digital Editions (ADE) version 4.5 up and running? It's a common question, especially when you're dealing with software updates or migrating from an older version. Let's break it down, shall we?
Many folks find themselves in a similar boat, wondering about the best way to install ADE 4.5. A common scenario involves having an older version, like ADE 2.0, already on a Windows 7 machine. The big question then becomes: do I need to uninstall the old one first, or can they coexist?
From what I've gathered, it's generally a good idea to uninstall the older version before installing ADE 4.5. While sometimes different versions can work together, it's not always a smooth ride. To avoid potential hiccups and ensure everything runs as it should, a clean slate is usually the way to go. So, the typical process would be to remove ADE 2.0, and then proceed with installing version 4.5.
Now, for those of you in a more technical role, perhaps managing multiple machines, the idea of a 'silent install' for ADE 4.5 might be on your radar. This is where things can get a bit more intricate. The standard command for a silent installation, like ade_4.5_installer.exe /s, often runs into a snag: a prompt asking if you want to include Norton Security. This is understandably frustrating when you're trying to deploy software without manual intervention.
Digging into this, it seems the installer checks for certain antivirus products. If it doesn't find what it's looking for, it offers to install Norton Security. To bypass this, the trick is to manipulate the Windows Registry before running the installer. Specifically, you'd add a registry key to signal that Norton Security isn't needed or has been handled. For 32-bit systems, this would be under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\N360, and for 64-bit systems, it's HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\N360.
Some users have also found success with specific command-line switches or by repackaging the installer into an MSI format, especially when using deployment tools like SCCM. For instance, adding -passthru when using PowerShell scripts can help manage the process, and some have experimented with switches like nss=0, though its effectiveness seems to vary.
Ultimately, whether you're a single user upgrading your software or an IT professional managing a fleet, the key is often preparation. For a straightforward personal installation, uninstalling the old version and then installing 4.5 is usually the path of least resistance. For mass deployments, a bit of registry tweaking or repackaging might be necessary to achieve that seamless silent install.
