Applications fail to quit

I've have problem where applications hang (get into a "not responding' state) but fail to quit after I do a Force Quit from Force Quit Applications. So far I've had this with: Photoshop CS3 10.0.1; Superduper; and Finder. Mostly, I've noticed the problem with Photoshop which is my primary application for work.
For example, when I force Photoshop to quit, it disappears from the Force Quit Application list. However, after quitting, I cannot open .psd or .jpg files from Bridge or from Finder. Raw files open up ok from Bridge into Camera Raw.
And, when I try to shut down or restart my machine i get: " Logout has timed out - The application Photoshop failed to quit and is not responding." so the only way to restart is to force a shut down with the power button. After restarting the Mac everything works ok again for a a while and then the problem happens again.
Additionally, if I try to do a Restart after forcing the Mac to shut down and restart, at times instead of shutting down the screen just goes either black or grey and then hangs before completing the shut down
I have repaired my disk permissions, reset my PRAM and NVRAM and run Diskwarrior, Cocktail and iFreeMem. I have checked memory usage when the problem happens and would appear to have a massive excess of Free memory which moves between 3.5Gb and 7.5Gb.
Any thoughts on what might be causing this and what else I can do to eliminate the problem would be very gratefully received
thanks
I am working on a Dual-Core Intel MacPro with 9GB memory, running OS 10.4.11

Start over. Deep clean and repair. Get to the source and causes. You knew that, right? just pushing it off?
Corrupt drive, directory, files, preferences, cache files cna all play havoc. Sometimes it is just easier to start wiTH A FRESH CLEAN NEW SYSTEM and go from there.
Run Disk Warrior frequently.
Repair your drive and don't assume that it is safe to just relaunch, restart, or reload.
Eliminate anything other than essential to CS3.
Hopefully you never used CS2 or Migration Assistant to bring over applications from a G4/5.
You have a lot of symptoms, but it takes time and sweat to clean up things. The whole idea of using SuperDuper is so you have a known good backup you can just restore from.
A dedicated boot drive makes it easier to maintain the system. Means that your data is on another drive.
A setup for CS3 should have a lean system, dedicated fast boot drive, a drive for data, and a scratch volume (even stripped RAID).
4 x 2GB of memory might be better than having the 'extra' 2 x 512MB sitting there.
To get to the root cause, can you rule out memory with Memtest? bad sectors?
*At the very least, create a new test account.*
I like to put my home folder on non-boot drive.
/Volumes/volname/Users/account - made easier in Leopard but then 10.5 isn't really ready, not for CS3 probably.
My guess is you have a plug-in or something that is bugging your system. Anything that is not Intel, anything that runs under Rosetta, where Activity Monitor shows "Type" is "PPC" for starters.

Similar Messages

One application "failed to quit" on auto shutdown

This has been happening daily now for perhaps a month, and it's got me stumped. I can't identify any pattern or anything.
I have my system scheduled to shutdown overnight and start up in the morning, and have had this same setting for years. What's happening lately is that the unattended shutdown apparently times out and I get a message saying logout failed "because the application [X] failed to quit." Now the really weird bits -
'X' is almost literally a different application every day, and it's rarely if ever attributable to an unsaved document. I think it's happened at least once with every single one of the applications I regularly have running. Sometimes it's an application I've used in the course of the day, and other times it's one I haven't touched. But it happens every day.
if I manually select the shutdown menu command at any time, including after finding that the auto shutdown has again failed, the shutdown runs smoothly with no application failing to quit.
I've run 'repair disk' in Disk Utility and also Disk Warrior and applejack several times each, as well as a weekly scheduled batch of maintenance tasks (using Cocktail). None of these operations has changed the behaviour come shutdown time.
Has anyone else seen this? Solutions anyone? Thanks.

I'm 'bumping' this one.
Still happening very consistently, and becoming a real problem. Since originally posting I've run all the disk operations many times over, as well as one or two system updates at least. Nothing has changed, it just happens like this every night.
The only thing I can offer as a (sort of) pattern is that the application that's most often the one reported as preventing logout is HistoryHound. And it would appear to be one of the first ones the system tries to quit in its shutdown, since most of the apps are still running. However it does still vary - it happens on a different app sometimes, and it happens on some app when HH wasn't even running. So not sure that's much of a clue - unless perhaps certain apps are taking longer to quit than the system expects (or something??? - scratching for clues here ...... )
Can anyone help? Please ....

I downloaded xbmc to my MacBook Pro and the application failed to quit and is not responding it is telling me to press continue to logout but the track pad is not responding what do I do?

I downloaded xbmc to my MacBook Pro and the application failed to quit and is not responding it is telling me to press continue to logout but the track pad is not responding what do I do?

Press and hold the power button until the machine turns off. Then restart.
Clinton

HT5381 I am running Snow Leopard 10.6.8 and attempting to upgrade to Mavericks....installation completes and a message appears stating that my computer will restart in x seconds. I then get a message "Application install OS X Mavericks failed to quit". A

IMac upgrade from Snow Leopard 10.6.8 to Mavericks errors by failing to restart computer........after install message states that "your computer is restarting in x seconds"...then window appears that "application install OS x Mavericks failed to quit"...try to log out again, quit install OS x Mavericks and choose apple menu to log out...........this does not work!

Are you running OS X Server (the forum this question was posted in), or are you running OS X? If you're not sure what that difference is and why I'm asking it, then you're probably running OS X and are very likely not running OS X Server here.
Hopefully you have a pre-upgrade backup of your data, on the off chance something has either already gone badly wrong already, or if something goes wrong with the following...
To force the quit here and to force the shutdown here, press and hold the power button for ~10 seconds.
If you don't have a backup already and if the box doesn't reboot, then you'll want to boot from the 10.6 DVD (of OS X or OS X Server) and create a backup — it won't be a particularly good backup of the OS X or OS X Server system, but at least you'll have access to your own files and related data. This backup because recovering from a badly-failed upgrade might involve reinstalling OS X.

Logout has timed out because the application Mail failed to quit.

Hello world... (Mac world that is)
The message says more "Logout has timed out because the application Mail failed to quit. To try again, quit Mail and choose Log Out from the Apple menu."
I tried everything. Still does not let me shut down.
Other programs will not shut down at this time, including Finder. I also know that the Time Machine icon has been spinning for over an hour. So I imagine we are in a loop of sorts.
Unfortunately, I have had similar troubles before that I did not record. So I figure I start now and see if somebody out there can help me.
Peace!
Chopo

I'm having the same problem (can't logout, shut down or restart), but the referenced solution doesn't seem to apply. I do not get a "Cannot connect to server" message, I just get a "Logout has timed out" message. It seemed to happen after an automatic software update that was supposed to involve a restart, but it hasn't been able to restart since.
Can you please clarify, what is meant by "delete the AutoLaunchedApplicationDictionary, which is located under the root node" (with reference to file loginwindow.plist)?
This is what the loginwindow.plist file looks like now:
bplist00Ñ!AutoLaunchedApplicationDictionary¢ÒTPathTHide-/Library/Printers/hp/hpio/HPEventHandler.app/Ò _N/Library/Application Support/Hewlett-Packard/Software Update/HP Scheduler.app//27
I was at the genius bar earlier, and they said I need to 'archive and install' in order to 'reset the OS'... but there's got to be a better answer than that, no? Perhaps this plist thing? I'm surprised that even powering off the imac doesn't reset anything... it just comes back the way it was. I'm supposed to bring the 25 inch imac in to the mac store for surgery (archive and install), but seeing several similar cases on this discussion forum, without archive and install identified as the clear solution, I'm in search of a second opinion... or any suggestion for how to simply make this work the way it was before? Is it 10.5.4 that is causing this? Should I go back to 10.5.3?
Any suggestions are appreciated. Thank you.

Photoshop failed to quit and is not responding

I've had a nasty problem for the past few days that seems to be getting gradually worse. ie it now happens within a few minutes of openning Photoshop, whereas before it was happenning after an hour or two of working on an image....
At some point while working on a moderately complex .psd (roughly 70mb with some 15 layers) Photoshop hangs and Force Quit Applications tells me that Photoshop is not responding. I can't identify anything particular that i'm doing that triggers it.... i use a fairly wide variety of tools and filters and the hang doesn't seem to be triggered by anything specific.
I force Photoshop to quit, and it disappears from the Force Quit Application list. However, after quitting, I cannot open .psd or .jpg files from Bridge or from Finder. Raw files open up ok from Bridge into Camera Raw. And, when I try to shut down or restart my machine i get: " Logout has timed out - The application Photoshop failed to quit and is not responding." so the only way to restart is to force a shut down with the power button. After restarting the Mac Photoshop works ok again for a a while and then the problem happens again.
I have repaired my disk permissions and run Diskwarrior over both my Mac HD ad the external Firewire drive where all my images live - which didn't identify anything out or the ordinary.
Any thoughts on what else I can do to eliminate this problem would be v gratefully received
I am working on a Dual-Core Intel MacPro with 9GB memory, running OS 10.4.11 and Photoshop CS3 10.0.1 and Bridge CS3 2.1.1.9

Neil, just for reference the Cron script problem was fixed in 10.4.2 and should be run on boot if they haven't already. This doesn't mean that running cocktail occasionally to make sure doesn't have value or to run the maintance scripts early doesn't help (it wont hurt).
Nick
The 3 Gb limitation is a limitation of 32bit operating systems and software. Photoshop can't address (use) more than 3Gb regardless of how much you have free or installed. OSX 10.4 is kind of 64bit but not completly, it has the ability to remap memory so EACH program can use a max of 3Gb. so in your case with 5ish Gb used PS is using 3Gb, Safari is using a bit and the OS is prob using most of the rest.
Looking at what you posted the only two figures your really interested in is the Used and Free (which add up to approx 9Gb). The fact that the used number doesn't change from the several files open and the liquify filter opening indicates to me that it has already grabbed as much memory as it can( it's using 3Gb of the 5.52, the rest is the OS etc).
Simply put PS IS running out of memory. You can help this by putting the memory allocation in the PS preferences higher (the OS will use other areas of memory so it wont cause a problem) and make sure the scratch disk is set to a drive with plenty of space. But keep in mind the Liquify filter is VERY memory intensive so you may not be able to use it with lots of files open.
BRETT

10.5.3 Sleep Problems - Failed to Quit or Logout Messages

OK, so I should have written down the exact message (I will do next time it happens). Installed 10.5.3 on a brand new iMac 3.06GHz 24-inch. Put the iMac to screensaver and it sleeps by itself (as intended) or sleep the iMac from the Apple menu.
Then when I wake it from sleep. Mail.app or Camino have messages to the effect of 'Failed to Logout' or 'Failed to Quit, logout time expired'. As though the iMac had tried to logout or quit and application whilst it was sleeping or during the sleep process.
Any ideas?
When it happens next time I will post the exact messages.
This does not happen when the iMac has been put to sleep for a short period of time.
Edit: I should also add, that I have 10.5.3 and the same apps on a MacBook Pro and this has none of the same problems.
Message was edited by: DavoMrMac

OK, so it happened again. The iMac went to sleep from the screensaver. Then when I woke it about an hour later... Mail.app had quit.
The only other running app was Camino. The message says 'Logout has timed out because the application Camino failed to quit. To try again, quit Camino and choose Log Out from the Apple menu'.
So, I guess the message is not the important thing. I just need to know what is causing the iMac to try and log out.

Logout has timed out because the app (program name) failed to quit

Hi,
I've been having an odd problem with my Mac since I did the last software upgrade.
I upgraded to 10.5.8 and this problem has been occurring sporadically ever since.
Basically, 7 times out of 10, when I try and shut the computer down, I get the following message: "Logout has timed out because the app (program name) failed to quit."
The program apparently causing the problem varies - sometimes it's Photoshop, sometimes iTunes, OpenOffice, etc. Today it failed because Software Update (which I'd just run, in order to install the latest update) failed to quit!
The only way I can get the computer to shut down in this case is to press and hold the power button.
My Mac is a 20 inch 2.66 GHz with 2GB of RAM, and is about 18 months old. Up until the last upgrade I had no problems with it.
Has anyone else had this problem and is there a way to fix it?

HI,
Open Activity Monitor (Applications/Utilites)
Click the pop up menu and select: My Processes
You can Force Quit any of the apps you mentioned from that window befoe you shut down.
Carolyn

Preview fails to quit

I have run MacOSX 10.2.8 (Jaguar) on my iBook successfully for years. Suddenly, Preview has developed an intractable fault. Preview will not open any files yet fails to quit. Finder won’t force quit Preview either. In the Force Quit window Preview appears in red, which must mean something - angry? I’ve tried Process Viewer and quitting or force quitting Preview there: still no joy!! If I ‘open’ the application again, Finder generates the dreaded beachball and after a minute Finder says +“The operation could not be completed. An unexpected error occurred (error code - 1712)”.+ OK so the only thing left is to restart. Big problem: Finder won’t shut down or restart, saying Preview has to be quit first ..... Now what? As it’s an iBook so even pulling the plug doesn’t help, as the battery takes over - of course! As long as I don’t need to install any software updates I can continue, putting iBook to sleep overnight, but it’s getting slower and slower and soon it’ll be Christmas. Any clues gratefully received.

Welcome to discussions Itakuera,
1. If Preview won't Force Quit, open Activity Monitor and locate Preview, highlight it and click Quit Process, to kill it.
2. To attempt to rectify the recalcitrant Preview, locate the property list file
~/Library/Preferences/com.apple.Preview.plist
and trash it.
Now open Preview again and see if it works.
3. If it doesn't, I suggest you run Repair Disk from your Install DVD.
To do this: Insert the Install Disk 1 into the drive and then select Restart; when you hear the chime hold down C key until the apple logo appears.
This will take you to the installation software, but you do not want to install.
Select your language, then go up to the top menu bar and navigate to the Disk Utility application.
Select the start up drive, then go to the First Aid pane where you can click on Repair Disk.
If it finds errors, repeat the process until it reports no errors.
After these repairs, quit the application, and restart normally.
Once restarted normally run Repair Permissions from the Disk Utility application found on your hard drive in Application/Utilities.
4. Another option is to re-install the latest 10.2.8 combo update, as I remember having similar problems with Preview in 10.2, and the optimization phase of the software update was the magic that put things back in order.

Java "Application Failed to run" error in safari

I'm getting a " Application Failed to run" error on safari when trying to upload photos to facebook via the java uploader. I can't use the iphoto uploader for this particular page so that is not a solution.
I've uploaded photos plenty of times before but starting today, I get the following JAva Console message that I've deleted my user name from. Although I don't see anything here that indicates an erro, it is promted by an Error message that you click for details, which says the "The Application failed to run". Any thoughts on what I can do to correct this? I haven't changed anything since it's worked in the past and I've quit safari, restarted and ran disk utility.
Java Plug-in 1.6.0_15
Using JRE version 1.6.0_15-b03-219 Java HotSpot(TM) 64-Bit Server VM
User home directory = /Users/
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
o: trigger logging
p: reload proxy configuration
q: hide console
r: reload policy configuration
s: dump system and deployment properties
t: dump thread list
v: dump thread stack
x: clear classloader cache
0-5: set trace level to <n>
----------------------------------------------------

This I guess is not a Safari problem since I got the same error in Firefox. How does one fix a Java problem occurring in at least two different browsers?

FlashBuilder fails to quit AIR app before launching new one

Frequently FlashBuilder fails at quitting a currently running debug application. Is there any way this could be improved so it could consistently quit the application when launching another debug session?
Launch Failed
If the program is already running, close it before attempting to run.

These are user to user forums, so if you want Apple to see your report, best to repost it at
http://www.apple.com/feedback/macosx.html

MacInstall fails to quit.

Hello guys,
lately my MacBookPro fails to quit. Whet I hit Shut Down, the laptop does not quit and warning comes up: MacInstall fails to quit.
I only manage to quit the machine by force quit.
Is there anything I can do to fix it? What is MacInstall anyways?
Thanks

MacInstall is a third-party installer application that some software developers use instead of Apple's Installer application to build installation packages for their software. Evidently you've installed some piece of software whose developer used MacInstall, and for whatever reason, MacInstall isn't quitting as it should. Force-quit it, then use Spotlight to locate MacInstall on your hard drive, trash it, and empty the trash.

My software applications were unexpectedly quitting (i tunes, pages, skype) so I upgraded to Lion OS 7. It took 2 days to download, 14 hours and counting to install so I switched it off and on. The only result is a screen asking for my password. I key in

My software applications were unexpectedly quitting ( I Tunes, page, skype) so I downloaded Lion OS 7. It took 48 hours to download and 18 hours to install (and counting) so i turned it off and on several times. All i get now is a screen with the Apple Icon asking for my password with option to switch off or restart. tried both but it just brings me back to the same screen
what do i do?
thanks

When you decided to upgrade because you were having serious problems, you jumped from the frying pan into the fire. If the problem was the system, then reinstalling the current system is the way to go. But you had several application quiting, some from Apple and some not. so the quitting was something affecting all of them, and of course the system could be the culprit, but the system is not the only possible culprit. Replacing the system when it was not the problem only buries the problem under a whole new pile of problems.
Before reinstalling a system you need to make your Mac as trouble free as possible and back up as much as you can. There is a wide variety of problems that can affect many applications. Here is a short list:
Font problems. Use Font Book to verify your fonts. Delete or disable bad fonts.
Disk, permission, or cache corruption.
Incompatible Startup Items, Login Items, interface modifications or menu extras.
Corrupted preferences other than those of the affected applications. Check preferences system-wide using the freeware applications Preferential Treatment or AppleJack
Insufficient RAM or lack of free disk space.
Programming errors. Bugs in application code are not uncommon. For third-party applications, check the vendor's Web site for updates to the application, reports of known bugs, or for information on how to contact the vendor for support. A bad program might be grabbing up too much RAM and causing the other applications to fail as well.
Corrupted application. Check the logs to see where the crash occurred.
Other software problems or conflicts.
Corrupted Mac OS X installation. Perform an Archive and Install of your current Mac OS X.
Hardware problems. Run the Apple Hardware Test that came with your Mac.
Try to discover the culprit:
Open Console, located in the Macintosh HD > Applications > Utilities folder.
Check the Console and System logs for messages that may be related to the problem.
To open these logs, in Console choose File > Open, then choose:
Open Console Log and Open System Log
Messages in these logs are time stamped when the message was logged.
Scroll the log windows to the approximate time when the problem occurred.
Details of the messages may provide additional clues you use in troubleshooting.
Do not post an entire log to a forum. Post only the messages referring to the function or application causing a problem.
AppleJack is a free program you run in 'Single User Mode.' Install it. When you want to run it, press Command s until you get a black screen with text. Type 'applejack' and run the repairs.

Firefox fails to quit on OS X 10.10

Hello
I'm having an issue with Firefox 33.1 on Mac OSX 10.10 - basically Firefox fails to quit. If I issue a quit command the UI will shut down but the process stays active for ever.
1. This 100% reproducible
2. Tried "rest Firefox" to no avail
3. Tried to re-install Firefox (fresh download)
4. I have tried to run without extensions:
AGTMBP13:~ alex$ /Applications/Firefox.app/Contents/MacOS/firefox-bin -safe-mode
LOGIN CALLBACK in libCVP11LCB: CK_RV CB_Initialize(CK_CONTEXT*, CK_C_INITIALIZE_ARGS*, CK_ULONG*)
[22564] ###!!! ABORT: Aborting on channel error.: file /builds/slave/rel-m-rel-osx64_bld-0000000000/build/ipc/glue/MessageChannel.cpp, line 1547
[22564] ###!!! ABORT: Aborting on channel error.: file /builds/slave/rel-m-rel-osx64_bld-0000000000/build/ipc/glue/MessageChannel.cpp, line 1547
Terminated: 15
AGTMBP13:~ alex$
(the abort above is when killing the process).
All in all it simply does not work :(
Any suggestion most welcome

Hello
Thanks for you answer - here we go with the troubleshooting infos
Application Basics
Name: Firefox
Version: 33.1
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:33.0) Gecko/20100101 Firefox/33.0
Multiprocess Windows: 0/1
Crash Reports for the Last 3 Days
All Crash Reports
Extensions
Name: BetterPrivacy
Version: 1.68
Enabled: true
ID: {d40f5e7b-d2cf-4856-b441-cc613eeffbe3}
Name: Dictionnaire français «Classique»
Version: 4.3
Enabled: true
ID: [email protected]
Name: Ghostery
Version: 5.4.1
Enabled: true
ID: [email protected]
Name: LastPass
Version: 3.1.54
Enabled: true
ID: [email protected]
Name: NoScript
Version: 2.6.9.3rc3
Enabled: true
ID: {73a6fe31-595d-460b-a920-fcc0f8843232}
Name: npIpcam
Version: 2.0.1.7
Enabled: true
ID: [email protected]
Name: Perspectives
Version: 4.5.2
Enabled: true
ID: [email protected]
Name: Readability
Version: 2.4
Enabled: true
ID: [email protected]
Name: SPDY indicator
Version: 2.1
Enabled: true
ID: [email protected]
Name: Troubleshooter
Version: 1.1a
Enabled: true
ID: [email protected]
Name: User Agent Switcher
Version: 0.7.3
Enabled: true
ID: {e968fc70-8f95-4ab9-9e79-304de2a71ee1}
Name: Xmarks
Version: 4.3.5
Enabled: true
ID: [email protected]
Name: Adobe Acrobat - Create PDF
Version: 1.1
Enabled: false
ID: [email protected]
Graphics
Device ID: 0x 126
GPU Accelerated Windows: 1/1 OpenGL (OMTC)
Vendor ID: 0x8086
WebGL Renderer: Intel Inc. -- Intel HD Graphics 3000 OpenGL Engine
windowLayerManagerRemote: true
AzureCanvasBackend: quartz
AzureContentBackend: quartz
AzureFallbackCanvasBackend: none
AzureSkiaAccelerated: 0
Important Modified Preferences
accessibility.typeaheadfind.flashBar: 0
browser.cache.disk.capacity: 102400
browser.cache.disk.smart_size_cached_value: 640000
browser.cache.disk.smart_size.enabled: false
browser.cache.disk.smart_size.first_run: false
browser.cache.disk.smart_size.use_old_max: false
browser.cache.frecency_experiment: 1
browser.fixup.alternate.enabled: false
browser.history_expire_days_min: 10
browser.history_expire_days.mirror: 180
browser.newtab.url: about:blank
browser.places.importBookmarksHTML: false
browser.places.smartBookmarksVersion: 7
browser.privatebrowsing.dont_prompt_on_enter: true
browser.search.suggest.enabled: false
browser.search.useDBForOrder: true
browser.sessionstore.upgradeBackup.latestBuildID: 20141030112145
browser.startup.homepage: https://www.google.com/ncr
browser.startup.homepage_override.buildID: 20141030112145
browser.startup.homepage_override.mstone: 33.1
browser.tabs.warnOnClose: false
dom.mozApps.used: true
dom.w3c_touch_events.expose: false
extensions.lastAppVersion: 33.1
font.internaluseonly.changed: true
font.name.serif.x-western: Verdana
media.gmp-gmpopenh264.lastUpdate: 1415357552
media.gmp-gmpopenh264.version: 1.1
media.gmp-manager.lastCheck: 1415913133
network.cookie.prefsMigrated: true
network.protocol-handler.external.mailto: false
network.security.ports.banned: 8118,8123,9050,9051
places.database.lastMaintenance: 1416012207
places.history.expiration.transient_current_max_pages: 104858
places.history.expiration.transient_optimal_database_size: 167772160
places.last_vacuum: 1296166981
plugin.disable_full_page_plugin_for_types: application/x-bittorrent,application/pdf
plugin.importedState: true
plugin.state.doubletwistwebplugin: 0
plugin.state.folx3plugin: 0
plugin.state.folxnetscapeplugin: 0
plugin.state.officelivebrowserplugin: 0
plugin.state.sharepointbrowserplugin: 0
print.print_bgcolor: true
print.print_bgimages: true
print.print_colorspace:
print.print_command:
print.print_downloadfonts: false
print.print_duplex: 0
print.print_evenpages: true
print.print_footerleft:
print.print_footerright:
print.print_headerleft:
print.print_headerright:
print.print_in_color: true
print.print_margin_bottom: 0.5
print.print_margin_left: 0.5
print.print_margin_right: 0.5
print.print_margin_top: 0.5
print.print_oddpages: true
print.print_orientation: 0
print.print_page_delay: 50
print.print_pagedelay: 500
print.print_paper_data: 0
print.print_paper_height: 11.00
print.print_paper_name:
print.print_paper_size_type: 1
print.print_paper_size_unit: 0
print.print_paper_width: 8.50
print.print_plex_name:
print.print_printer:
print.print_resolution: 0
print.print_resolution_name:
print.print_reversed: false
print.print_scaling: 1.00
print.print_shrink_to_fit: true
print.print_to_file: false
print.print_unwriteable_margin_bottom: 17
print.print_unwriteable_margin_left: 17
print.print_unwriteable_margin_right: 17
print.print_unwriteable_margin_top: 17
privacy.cpd.offlineApps: true
privacy.cpd.siteSettings: true
privacy.donottrackheader.enabled: true
privacy.sanitize.migrateFx3Prefs: true
privacy.sanitize.timeSpan: 0
security.warn_viewing_mixed: false
security.warn_viewing_mixed.show_once: false
storage.vacuum.last.index: 1
storage.vacuum.last.places.sqlite: 1413937753
Important Locked Preferences
JavaScript
Incremental GC: true
Accessibility
Activated: false
Prevent Accessibility: 0
Library Versions
NSPR
Expected minimum version: 4.10.7
Version in use: 4.10.7
NSS
Expected minimum version: 3.17.2 Basic ECC
Version in use: 3.17.2 Basic ECC
NSSSMIME
Expected minimum version: 3.17.2 Basic ECC
Version in use: 3.17.2 Basic ECC
NSSSSL
Expected minimum version: 3.17.2 Basic ECC
Version in use: 3.17.2 Basic ECC
NSSUTIL
Expected minimum version: 3.17.2
Version in use: 3.17.2
Experimental Features
---------------------

LR2: 1st Launch of Demo - The application failed to initialize properly (0xc0150004)

Hello all,
I've never used Lightroom nor had any need to really justify buying it when PS meets my needs, but thought I'd at least take a look at Lightroom 2 to see what it's like. Well, upon installing the trial to my Vista 64 system, the subsequent launch of LR2 only gave the subject "application failed to initialize properly (0xC150004)" error. I see no posts regarding this particular error, and Google searches only turn up that this error could be due to a wealth of things, inclusive of the usual talk regarding viruses or spyware.
Notwithstanding that I've got quite a number of applications installed, I keep my system relatively clean and do not suspect anything awry. Many speak ill of Norton products, of which I use Norton Internet Security 2008 and have had nothing negative to say about it...no issues from it with reagard to PS CS2 or CS3, so I'd expect none with LR2.
Oh...and as far as any departure from the default installation goes, I installed LR2 to a separate partition where most of my applications get installed, rather than to the system partition. Of course, that should be transparent and not matter.
I'm largely looking to see if there are any known obvious LR2 problems that might cause such an error to arise. If not, I'll just uninstall and forget about it. It's not worth spending too much time to resolve.
I have installed LR2 under the Windows XP/SP2 boot configuration of my system, using a separate installation path on my programs partition than used for the 64-bit version, and all looks to be working fine there. So, this may be more of an LR2 issue with Vista 64.
Thanks,
Daryl

Hi Ian,
Thanks, but no luck with that idea either. I know 32- and 64-bit O/Ses are different, but I largely expected LR2 to work with both my installations under Norton Internet Security 2008 since all else does. A leap of assumption perhaps, but at least this exercise suggests the problem is unrelated to Norton software. I disabled all services and startup processes for both NIS2008 and Norton Ghost 14, via msconfig, even uninstalled and reinstalled LR2 under those conditions, and the problem persists.
One additional thing I did observe, as I decided to monitor Task Manager while the LR2 installer ran, is that even after the installation completed and I left the box selected to launch LR2, the MS installer 'msiexec' did not close out. So, I rebooted and with no msiexece active in the list afterwards, again tried launching LR2 with no success.
The only thing I can glean from this is a similar issue I had with Raxco PerfectDisk 2008, which launched 3 instances of msiexec during its installation, and never closed those. If I killed all related processes and attempted to launch PerfectDisk, it would freeze up at the splash screen with those 3 msiexec processes active again. I sent in some detailed notes to Raxco support for some feedback and if they come up with anything to offer that resolves the issue, perhaps it will be related to why the LR2 installer also doesn't close, or can't close, the msiexec. Perhaps a problem unique to my Vista 64 installation in spite of all else working. As with LR2, PerfectDisk works fine under XP32.
Regards,
Daryl

Applications fail to quit

Similar Messages

Maybe you are looking for