When ever there is problem with the liveudpate not downloading the defnintions and you come across the error codes (e.g LU1835) which might not mean any thing to you, well below is the information which will help you to determine what exactly those numbers means.
1800 The operation was successful or the patch installed successful
1801 The user pressed the Cancel button or some other process (callback) told LiveUpdate to Cancel.
1802 COM Initialization failed (CoInitialize() function comes back as failed.) - We display a Windows Message Box at the start of LiveUpdate processing, before we create LuComServer.exe and before we create the normal UI.
1803 Our generic error code that we use when we don't know what happened or we don't try to get any extended error information.
1804 We didn't have enough system memory available to declare some object.
1805 There are no registered products in the Product Catalog.
1806 All downloaded patches failed to install.
1806 LiveUpdate was unable to install any of the updates selected for a particular PVL
1807 DUN configuration for RAS no longer exists - This appears in a Windows Message box when the user opens up the configuration pages.
1808 Users computer does not have Dial-up Networking installed - We don't currently display this error message.
1809 There was some error creating the Patch Catalog Object or converting legacy LU 1.5 settings into a Product Catalog file.
1809 Unable to create the stCheckForUpdates object. This is the main LuComServer.exe object.
1809 Unable to get an interface pointer to the stPatchCatalog when one is required.
1810 This message will be generated when the we can't move the legacy working folder to the new per machine location. This error message can happen for any number of reasons, from being unable to create the new directory to be unable to delete the original files. My guess is usually this occurs as a problem with access rights.
1811 LiveUpdate could not unzip the livetri.zip or Mini-TRI file. The TRI file was probably corrupted.
1812 The process launched by the LaunchEx command returned something other than 0, 1, or 2. This indicates that the patch failed.
1813 Proxy or Host authentication failed because we didn't provide authentication or we provided an incorrect authentication
1814 LiveUpdate could not find the livetri.zip or Mini-TRI files on the server. At this point, the error means that LiveUpdate found no TRI files on any of its hosts.
1815 LiveUpdate could not read or write a file because the user did not have sufficient rights
1815 LiveUpdate could not read or write a file for some unknown reason.
1816 LiveUpdate did could not install the UI selected patch. No additional information for on the error is available.
1817 Some updates were applied successfully, but others were not. (I don't know if this error ever gets generated.)
1817 LiveUpdate was only able to install a few of the selected updates for a particular PVL
1818 LiveUpdate could not create a directory it needed because the user did not have sufficient rights.
1818 LiveUpdate could not create a directory it needed for some unknown reason.
1819 The Proxy Server requires authentication and we are not giving it any authentication.
1820 LiveUpdate failed to install some patches and other patches were not selected
1821 The destination file for a COPY or UPDATE DIS primitive is in use.
1821 The file that a DELETE or DELAYDELETE command was trying to remove was in use. (I'm not sure if LiveUpdate still generates this error.)
1821 This update failed because it tried to overwrite a file that was in use. Close all of your Symantec applications and run LiveUpdate again.
1822 The target file for a COPY or UPDATE DIS primitive does not exist. (I'm not sure this error is ever generated.)
1823 There is already another LiveUpdate session in progress. (Not an ALU process. That is handled with a 1803 error.)
1824 An update was successfully applied, but it needs a reboot to complete.
1824 An update was successfully required, but it needs the machine to be rebooted immediately to complete.
1825 LiveUpdate could not find or open the DIS script for an update.
1825 The DIS script contained a command that LiveUpdate could not parse.
1825 There's some code that allows the user to simulate a DIS script without actually installing it. It doesn't work that well and will never get executed during a normal LU run. The error means LiveUpdate could not write out its simulation file.
1825 The file that a DELETE or DELAYDELETE command was trying to remove did not exist. (I'm not sure if LiveUpdate still generates this error.)
1825 The target file of the LAUNCH or LAUNCHEX command does not exist.
1825 The LAUNCH or LAUNCHEX command failed to start the new process. This could mean that the target of the command was not an executable file.
1826 The User chose not to install some of the available updates
1827 The User chose not to install any updates.
1828 There was an exclusive update available, so no other products where updated. You need to re-run LiveUpdate to get your updates.
1830 LiveUpdate cannot connect to a LiveUpdate server when using the LAN host.
1831 LiveUpdate could not create the download directory in the All Users/Application Data/… folder. This is likely a user permissions error.
1832 LiveUpdate could not read an update's (or TRI file?) zip file. The downloaded zip file was corrupted.
1832 LiveUpdate could not extract an update's (or TRI file's?) file from the downloaded zip file. The downloaded zip file was corrupted.
1833 The DoOnramp() command line was ill formed. (No matching brackets, or such problems.) This is either an internal error of the integrating product, a user error if the user tried to manually run LiveUpdate, or a LU Admin error, if the user tried to download to many products in a single LiveUpdate session. (We have a maximum size of data on our command line.)
1834 The HTTP transfer failed because the requested file did not exist on the server. This is an update not found error, not a missing TRI file error.
1835 The HTTP transfer failed because the server timeout waiting period expired.
1835 The HTTP transfer failed because the file is no longer available.
1836 The HTTP transfer failed because the server returned an internal error.
1837 The HTTP transfer failed because the gateway or proxy returned an error.
1838 The HTTP transfer failed because the server returned busy / temporarily overloaded error.
1839 The HTTP transfer failed because the gateway or proxy returned a timeout error.
1840 There is already another session of Automatic LiveUpdate run. (The luall.exe version LiveUpdate is handled in the 1823 error.)
1841 The RAS Dial-up connection didn't work.
1842 The DELAYDELETE command could not set up the files to be deleted on reboot. (This could be a permissions error.)
1842 The DELAYUPDATE command could not set up the files to be copied on reboot. (This could be a permissions error.)
1843 LiveUpdate could not read the DIS script for a patch. This is an IO error, not a parsing error.
1844 Old LU 1.90 error code which is now divided up into error codes 1844-1852. Products will also now be able to set their own unique error codes if they wish.
1845 The product was aborted by the product's presession callback and a unique error wasn't set. This is probably a subscription related issue.
1846 The product was aborted by the product's postsession callback and a unique error wasn't set.
1847 The product was aborted due to an authentication error with the associated Mini-TRI file.
1848 The product's registered callback failed to launch.
1849 The product was aborted due to a syntax error in the PreCondition.
1850 The product was aborted due to a memory allocation error during evaluation of its PreCondition.
1851 The product was aborted due to a unknown error during evaluation of its PreCondition.
1852 The product was aborted due to a failure to load LuPreCon.dll when evaluating a PreCondition.
1853 A failure that was never assigned a proper error code. (This is a coding error.)
1853 Since the error page is supposed to display errors only, trying to display a Success code here is considered an internal error. (This would be a coding error if we got it in the function that is trying to display error messages.)
1853 COM Error - We are trying to create a COM interface on an object that doesn't support the interface. (This is a coding error.)
1853 We are trying to call a function on a COM object that has not been implemented. (This is a coding error.)
1853 Some unexpected catastrophic COM error occurred. (This is usually the result of a coding error.)
1853 We passed invalid arguments to a COM function. (This is a coding error.)
1853 An invalid COM pointer was passed into a COM object via a COM Interface. (This is a coding error.)
1853 An invalid HANDLE was passed to COM object. (This is a coding error.)
1853 This error message is generated if a COM object can't be create because the out-of-proc server can't be created. This error gets generated if LuComServer.exe does not exist.
1853 Some code attempted to change the threading model of the current COM thread. (This is a coding error.)
1853 We tried to use COM before calling the CoInitialize function. (This is a coding error.)
1853 We tried to call CoInitialize twice on the same thread. (This is a coding issue, but I don't think this will be fatal error to LiveUpdate.)
1853 LiveUpdate throws this error if it gets into a situation that it doesn't think it should get into. (This is a coding error.)
1853 LiveUpdate is attempting to use a group operation on some registered products when the products are not grouped together. (This is a coding error.)
1853 This error will get generated if someone attempts to add a registered product to two different coupled groups. (This is a consistency issue with the Product Catalog. I don't know if this will result in a failed LiveUpdate session or not.)
1853 LU only supports adding 300 registered products to a single coupled group. (I don't think this will abort a LiveUpdate session, but I've never actually tried it.)
1853 Someone is trying to use a moniker for a product that is not registered. (This is a coding error inside LiveUpdate or a Point Product / Callback.)
1853 Someone tried to modify LiveUpdate's list of files to download while LiveUpdate was trying to download them. (This is a coding error, because the change attempt is happening too late.)
1853 An attempt was made to change the value of the Product, Version, or Language properties on a registered command line, but there is already another registered command line that would match on the new Product, Version, and Language property values. (This is a coding error if this gets returned to LiveUpdate where these error codes are process.)
1853 The Product Catalog is in an inconsistent state. (Two identical monikers, two identical PVL, etc.) (I don't know if this error gets propagated to the LiveUpdate UI.)
1853 LiveUpdate used an invalid session cookie for the current LiveUpdate session. (This is a coding error.)
1853 LiveUpdate could not generate the default variables (like the LiveUpdate installation directory.) This usually means that something, probably in the registry, is really messed up.
1854 LiveUpdate disabled Custom Content support because the LOTS file retrieval failed.
1855 LiveUpdate disabled Custom Content support because it was unable to retrieve a valid custtri.zip file.
1856 LiveUpdate was unable to access the file it downloaded.
1857 Callback was not signed by Symantec, possible tampering may have occurred.
1858 One of the updates retrieved requires you to restart your computer to finish its installation. Try running LiveUpdate again after you reboot.
1859 This patch was aborted because the version of the product for which it is intended is no longer present. This is most likely because another patch that was installed earlier in this session upgraded the product to a new version.
1860 LiveUpdate has detected a potential security compromise on your computer: one or more entries for the Symantec LiveUpdate servers exist in your Windows Hosts file. A malicious entry in your Hosts file could enable a denial-of-service (DoS) attack. Additionally, LiveUpdate may fail to connect to a non-Symantec LiveUpdate server. Generally, Symantec LiveUpdate server entries are not placed in your Windows Hosts file. To remove Symantec LiveUpdate entries from your Windows Hosts file, click Remove.
1861 Automatic LiveUpdate cannot run because a bug in the Microsoft Scheduler is preventing the NetDetect task from being launched. In order to fix this bug, you must visit Microsoft's web site and download a fix patch. Automatic LiveUpdate should work properly after that patch is applied.
1862 LiveUpdate was unable to remove the host entries from all Windows Host files. As a result, the LiveUpdate Security Warning dialog may appear again in future runs of LiveUpdate.
1863 "There is not enough disk space to download or extract the requested file(s).
If an application is stripping the content length header, we’ll report this error. The problem is LU won’t know how large the file really is and won’t attempt to download. This is known behavior."
1864 There is not enough disk space to download, extract, install or process the virus definitions update.
1865 LiveUpdate could not successfully authenticate the mini-tri file.
1866 There is not enough disk space to download the requested update package.
1867 There is not enough disk space to extract the contents of the update package.
1868 There is not enough disk space to process the script associated with this update package.
1869 There is not enough disk space to install files from this update package.
1870 A timer expired forcing LiveUpdate to abort the product callback.
1871 Failure to start a helper process forced LiveUpdate to abort the product callback.
1872 LiveUpdate aborted the update, because there was an open window created by the package
1873 LiveUpdate aborted the update during the prepackage phase for this update package.
1874 LiveUpdate aborted the update during the postpackage phase for this update package.
1875 LiveUpdate aborted the update during the welcome phase for this update session.
1876 LiveUpdate aborted the update during the finish phase for this update session.
1877 LiveUpdate could not execute a callback because it was busy processing another callback.
1878 LiveUpdate encountered an error, due to package automatic shutdown
1879 LiveUpdate encountered an error, due to access denial to create a directory
1880 LiveUpdate encountered an error, due to access denial to create a file
1881 LiveUpdate Control Panel functions are unavailable.
1882 LiveUpdate site blocked by NIS AOP - Parental Control.
1899 LiveUpdate could not update this product or component. If this problem persists please visit the Symantec Support web site for more information.
1900 LiveUpdate could not find all of the files it needed to run. LiveUpdate was either not installed correctly or some of its files were inadvertently deleted. You need to reinstall LiveUpdate before you can update your Symantec products.
1901 LiveUpdate encountered unexpected errors while getting updates. Your Symantec programs were not updated.You should try getting updates at a later time.
1902 LiveUpdate is unable to get updates at this time. Your Symantec programs were not updated. You should try getting updates at a later time.
1903 Network or a proxy server is attempting to redirect LiveUpdate's connection.
1904 The DAT file contains invalid entries
1905 A file listed by .dat is missing from TemHostEx directory.
1906 An available patch was removed from the LiveUpdate session. This happens if the user deselects a patch in the LiveUpdate UI or ALU removes a non-ALU compatible patch from its list of patches to install.
2000 There is a problem with the Virus Defs folder that prevents updates
2001 There is not enough disk space to update virus definitions
3000 LiveUpdate failed to download some updates for Lu Admin
3001 LiveUpdate failed to download the selected patch for Lu Admin
3002 The download directory was not given to LiveUpddate or the specified directory does not exist. (Admin mode only)
3003 LiveUpdate was unable to move a downloaded update to the specified destination directory (Admin mode only)
3003 LiveUpdate was unable to move the livetri.zip file to the destination directory. (Admin mode only)
6001 The guard or signature file is missing from the TRI file.
6002 LiveUpdate was unable to extract the guard file from the TRI file.
6003 LiveUpdate was unable to load the root certificate.
6004 No matching hash in the authenticated Guard file matched the update file.
6005 The update file matches the Expired SHA-1 not the current SHA-1.
6006 An unknown security related error was thrown be the security libraries.
6007 The guard file was present, but not acceptable (not signed / signature invalid.)
6008 LiveUpdate cannot trust any custom content, because it was unable to find the signing certificate within the LOTS.
6009 The LOTS file is invalid because it lacks information that identifies it as a LOTS file.
6009 The LOTS file is invalid because the certificate list size is invalid.
6009 The LOTS file is invalid because its format version is not supported by this release of LiveUpdate.
6009 The LOTS file is invalid because it does not contain any trusted Signer certificates.
6010 LiveUpdate was unable to open the LOTS file.
6010 LiveUpdate was unable to determine the size of the LOTS file.
6010 LiveUpdate was unable to read the version label of the LOTS file.
6010 LiveUpdate was unable to read the format version number of the LOTS file.
6010 LiveUpdate was unable to read data from the LOTS file.
6011 LiveUpdate cannot trust the LOTS file because its signing certificate does not chain to a trusted root.
6011 LiveUpdate cannot trust the LOTS file because it was unable to verify the LOTS file's digital signature.
6011 LiveUpdate cannot trust the LOTS file because it does not contain a valid signing certificate in its digital signature.
6012 LiveUpdate was unable to process the LOTS file (this is a "catch-all" error, indicating that an unexpected error occurred while opening/reading/authenticating the LOTS file).
6013 One of the updates or TRI files LiveUpdate download cannot be trusted. This error occurs if the size of a TRI file or update file is too large or there are problems with the file's archiving. The file archiving problems can be either the file willl be too large when it is extracted, the extractable size of the file is greater than the size reported in the zip headers, or the zip file contains illegal path information.
6014 The current user does not have sufficient privileges to install this update or execute the callback. To install this update or run this callback, log in as an administrative user and run LiveUpdate again.
6015 This type of update or callback can only be installed when LiveUpdate is run by an interactive user.
6016 The current user does not have sufficient privileges to update this product. To update this product, log in as an administrative user and run LiveUpdate again.
6017 This product can only be updated when LiveUpdate is run by an interactive user.