Re: Adobe Reader Programdata
Raingarda Krzynowek
There were 1,668 folders whose path began with "C:\ProgramData\Adobe\ARM\Reader_10.0.1\" each of which contain the files AcrobatUpdater.exe, AdobeARM.exe, AdobeExtractFiles.dll, and ReaderUpdater.exe. Each of these folders are around 1,805,080 bytes.
So I did uninstall all adobe reader, adobe arm, adobe flash, and adobe shockwave programs. Rebooted the computer. Deleted those folders (all of which were still there). And then reinstalled Flash and Shockwave. They have Adobe Acrobat so Reader is not necessary.
The only other thing that I would ask you at this point - can you pelase collect AdobeARM.log file from the User Temp folder? (each User likely has it's own Temp folder with its own AdobeARM.log file)
It's almost seven years since this question was posted, but Adobe is still trying to protect us against the evil of having extra free space on our hard drives. Here's a screenshot of my ARM window just now, showing more than 400 mb of space being used by various incarnations of Reader going all the way back to 2014.
I just checked and my machine also has 2.0G of historical ARM folders. It's good to know that we are being protected from having unused diskspace for free in this fashion. :). My operating systm on this legacy system is Windows 2012 Server.
There have been a lot of updates since 2013. The last few posts have shown what is supposed to happen, with one download per update. I don't know about Reader, but the updates for Acrobat Pro DC total 26 GB. This is different from the original post, where something had gone haywire, and made thousands of folders for the same update.
Somewhere along the lines, FoxIt added advertisements to their application. So, the speed boost over adobe reader (which is now, as mentioned above, largely non-existant) was replaced by advertising in your PDF reader. I understand the need to have ads, but it's annoying to the average Joe. And, I'm sure they're removable...but, really, I'd rather not deal with that at all.
yeah its not really needed anymore with the improvements in 8.1 and 9.0 to speed. Heck, I have the full version of Acrobat 9 and when its open with no PDF's loaded its like 20MB of RAM, not too shabby and it starts really fast.
Ok -- I just grabbed the latest adobe.. And sorry it takes atleast a couple of seconds longer to open the same exact pdf. And here -- same pdf opened.. which one is using more memory, handles, etc. Use what you want -- I will live with thos ads ;) vs the bloat that is adobe.
Why not do like I used to do-- I used to create a folder to put it in -- with a text file explaining the where it was on my xp install-- then when that folder hits close to 700mb -- burn it to a cd. Just don't forget should you have to repair to copy it back over to the folder you referenced in the text file. (you don't have to create a separate txt file for each moved file -- just append it) that and after you copy it back over change the read only status. That is what I used to do.
other than hat the only time I use PDF's anyway is when I look in ig manuals or soemthing, wich usually was back when I worked support. at wich point the search in adober reader is a million times better than foxit.
Eh, Reader 9 still flies on older computer anyhow. And if one has to be concerned with the installer eating up a lot of the space of the actual folder in this day and age, well, you must be running like a 10GB or something hard drive. :) I still get your point though hehe. I guess I don't care much even though I am running on smaller drives being I use raptors over 7200PM on my desktop. :)
Now that you mention it, I went ahead and checked up, and sure enough, the ads are (now) able to be turned off. The ads were very much obtrusive back in August, it seems they got the message and changed things. I'm only on Windows now and again; my bad.
the problem i find with foxit is that the text is often not very clear wheras adobe 9 the text is very clear and the space those setup files is negligable so i would not remove them as they may be needed later and if you delete them and say the updater needs them you would have to reinstall adobe just to get them back and those ads in foxit are annoying(i dunno why foxit added them)adobe used to be slow but now it seems they have learned and made it fast.
I keep an up to date administrative install point that is deployed using patch manager. If you put an uninstall rule for msi code AC76BA86-7AD7-1033-7B44-AB0000000001 in package boot, any existing versions of Reader 11 will be uninstalled and the up to date package will be installed with your customizations. This allows you to have one package for new installs and updates from any previous version while retaining your customizations.
Have you tried using the setup bootstrapper included with the extracted files? When you extract the compressed exe you should get a group of files including the installation MSI and CAB, setup.exe, setup.ini and abcopy.ini. The setup.ini should already specify the patches that were included, but you can add more as they are released. Add a CmdLine parameter to specify your transform file, like the example below:
Then build your update package as an .exe package using setup.exe and include all the other files as additional content. More detailed instructions are available on Adobe's website at Bootstrapper Deployment Enterprise Administration Guide
I assume that AcroRead.mst is the correct name of your transform and that the transform has been included in the package, is that correct? If you added any new files since originally publishing the package, did you delete and republish the package?
Can you describe the package you are using to deploy this update (i.e. the files you have included and the settings used)? It would also be helpful if you could export the xml from the packageboot helper and attach it as a file to this thread
By the way, you can get a basic progress bar for your test run by putting the following parameter under [Startup]. This might help ensure that the installer isn't prompting for any missing information.
my obervation of 2013-04-08 refer to the extract only part (step 2 in my first message). The administration install (step 3) has now been abandoned as this way nothing can be achived if already an older version is installed.
I'm also having a hard time getting this to work. I have clients on 10.0.4 and I'd like to get that uninstalled and 11.0.02 installed. So far, I've been unable to get 10.0.4 uninstalled so on test machines I'm ending up with both versions installed at the same time. I followed the instructions over here: . I'm not sure what I'm doing wrong, but I'd like to get it right. I think the only option, short of a solution here, is to find a way to uninstall 10.0.4 separately. I found a reference on the Adobe community site: Adobe Community: Adobe Reader Customization uninstall previous versions that is still unanswered which makes me wonder if there isn't something broken with the transform.
I've now successfully deployed my installer, at least to a test machine. It turns out that there's a bug in the customization wizard which requires you to wait until just before you save the msi to check the "remove all previous versions of reader" box. I also had a separate, but related at least in my case, issue with the adobeARMservice, that I've found a way to deal with now.
d3342ee215