Adobe Reader Vista Temp Error
Contents |
One games Xbox 360 games PC adobe reader temp folder games Windows games Windows phone games Entertainment All
Adobe Reader Temp Files
Entertainment Movies & TV Music Business & Education Business Students &
Adobe Reader Temp Files Mac
educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security
Adobe Reader Application Initialization Error
Internet Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Band Microsoft cannot install adobe reader Lumia All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
By If you're going to put up an error message, try to make it one that the user can DO something about, and try to make it unambiguous. A good error adobe acrobat reader dc application initialization error message takes work, and error handling seems to be one of those things that install adobe reader for windows 7 gets worked on last. A few weeks back I installed Tim Heuer's excellent Foxit PDF Preview Handler for Outlook 2007. Worked great. adobe reader not working windows 10 I had (fervently) lamented the slowness of Acrobat, and folks in the comments - including an Adobe employee - commented that Acrobat 8 was way better and way faster than before. I figured today I'd give Acrobat https://support.microsoft.com/en-us/kb/936645 8 a try on Vista since Ryan Gregg just released a PDF Preview Handler that uses Adobe's ActiveX SDK. Acrobat 8 on Vista is supposed to be nice because you get Thumbnail support and Search-ability for PDFs. I fired up the installer and was greeted with this error: Certainly they could have figured out ifthe drive was full by asking the drive if it was full. Instead, this error says (basically) "something went wrong http://www.hanselman.com/blog/AdobeAcrobat8OnVistaTheTempFolderIsOnADriveThatIsFullOrIsInaccessibleAndWhatIsLocalLow.aspx writing to a file, and I'm not sure what. Go ahead and see what you can do about it, user." So what does user do? Well... "Gosh! Is my hard drive full? How do I figure that out? Maybe My Computer:Nope, it's not full. Permissions? Well, this is where Mom stops. How does she know where the Temp folder is? Heck, how does any user? I went to a command line and typed ECHO %TEMP% and was told C:\Users\Scott\AppData\Local\Temp, but it turns out that's not true! Acrobat (actually Netopsystem's Feed Squisher Installation Stuff)writes to C:\Users\Scott\AppData\LocalLow\Temp. LocalLow? What's that?Certainly I can either check the properties and permissions on that folder, or I can use icacls which tells me I do have permission: C:\>icacls \Users\scott\AppData\LocalLow\Users\scott\AppData\LocalLow ScottPC\Scott:(I)(OI)(CI)(F)NT AUTHORITY\SYSTEM:(I)(OI)(CI)(F)BUILTIN\Administrators:(I)(OI)(CI)(F)Mandatory Label\Low Mandatory Level:(OI)(CI)(NW) As an aside, there's a great blog post on Vista and IL (Integrity Levels) over on Joanna's Invisible Things. Adobe's installer is trying to be clever and it's first squishy installer unpacks the real MSI installed into a folder that installers that will be elevated don't have access to. This happens on machines, like mine, that have UAC (User Access Control) turned off. Then, after the unpack/install files the temporary files are deleted. Solutions I can certainly try to grab the files by copying them out before I dismiss the dial
trying to install adobe reader v8 in Vista. When the program launches and extracts an error continues to pop up that says exactly: "The http://www.pcreview.co.uk/threads/adobe-reader-install-temp-folder-error.2999415/ Temp folder is on a drive that is full or is inaccessible. Free up spaceon the drive or verify that you have write permission on the Temp Folder" That message is provided by the windows installer with no other error codes or information provided. WHat temp folder is this referencing and how do I resolve the issue? Anyone know? Thanks Guest, Feb adobe reader 14, 2007 #1 Advertisements Guest Guest Hello, That's a known problem that has a work-around. Run the install again and when you get that error message go the the Adobe temp folder (if my memory is correct, it will be in "Users/yourusername/AppData/Local/Temp") and run the setup executable found there. Note that you must not exit from the error message prior to running setup adobe reader temp from the temp folder. If you do, the files in the temp folder will go away. You could also copy the Adobe temp folder to your desktop, exit the error message and re-run setup from the folder you just copied to your desktop...either way works fine. Tim "tpark369" wrote: > I am trying to install adobe reader v8 in Vista. When the program launches > and extracts an error continues to pop up that says exactly: > > "The Temp folder is on a drive that is full or is inaccessible. Free up > spaceon the drive or verify that you have write permission on the Temp Folder" > > That message is provided by the windows installer with no other error codes > or information provided. > > WHat temp folder is this referencing and how do I resolve the issue? Anyone > know? > > > Thanks Guest, Feb 14, 2007 #2 Advertisements Sascha Benjamin Jazbec Guest run it with compatibility mode for Windows XP SP2 and as admin, that did the trick here. Just right click the *.exe and have a look under propert