

The exact increase in space was 430,731,264 bytes or 410.8 megabytes. Installing the software increased the used space to 4.24GB. After doing so, the used space on the C disk was 3.84GB. This time, I copied the 48MB installer for version 11.0.06 into the XP VM. Not to rush to judgment, I found a Windows XP virtual machine that also had never had any previous installations of the Adobe Reader. More exactly, the used space increased by 406,261,760 bytes or 387.4MB. Then, after downloading and installing the Adobe Reader, the C disk had grown to 17.4GB. The pre-installer was deleted, but the fate of the main 48MB download is a mystery.īut I suspected something was up before I started, so, before doing anything, I took note of the fact that the used space in the C disk partition was 17GB.
#Adobe reader installer for mac pdf
In contrast, my preferred PDF Reader, Sumatra, is 8MB and the PDF viewer embedded in the Chrome browser is 4MB. The software was installed to C:\Program Files\Adobe\Reader 11.0 which occupies 116 megabytes of hard drive space (this was a 32 bit copy of Windows 8). Following the prompts however, you download a 1MB pre-installer called "install_reader11_en_mssd_aaa_aih.exe" and you never see or deal with the main 48MB installer. The software was downloaded from the official location, /reader which said that the download was 48MB. On a Windows 8 machine that had no prior versions of the Adobe Reader, I did a fresh install of the latest edition, released last month, version 11.0.06. But, while researching the new issue, I ran across yet another reason not to like the software: it consumes mass quantities of hard drive space, at least on Windows. Yesterday I found a new reason not to like it, which I expect will be the next Defensive Computing blog. I'll come clean right off the bat: I don't like the Adobe PDF Reader.
