Quicktime failed to initialise - error 2095 (ag...
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I've had a good look round and have not yet found a fix to my instance of this error. I have...
- Windows Vista Business SP2
- Quicktime 7.6.5
- iTunes 9.0.3.15
I have installed and removed (with Revo Unsinstall Pro) both iTunes and Quicktime separately and together many times including manually removing all references to quicktime from the registry. I have re-installed from all of user, administrator and 'hidden' administrator accounts. I have tried adding specific permissions in registry HKLM/Software/Apple../Quicktime. I have tried running system file checker tool. All yield the same result - which is:
- iTunes works fine (hurrah!)
- quicktime works fine on 'hidden' administrator and regular user accounts
- on my (administrator) account:
-- quicktime files play in Chrome with UAC on, but not in IE(8)
-- quicktime files play in iTunes with UAC on
-- quicktime(.exe) works fine with UAC off
-- with UAC on, I get error 2095 trying to launch quicktime directly or by double clicking on an .mov file. I also get plug-in did not initialise errors in IE.
I really would like to fix it! What should I try next?
Many thanks.
14 replies
Sign in or join Beachball Help to reply.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Excellent diagnostic work, OUM!
This reminds me of an old possibility. (It's a bit tricky to diagnose because the symptoms vary from QuickTime version to Quicktime version.) On XP, you could get similar behavior if one or some accounts had lost permissions on Registry keys for QuickTime. (The UAC behavior seems consistent with that too.)
Is that a 32-bit version of Vista or a 64-bit Vista? I can think of a couple of things we could try, and that will have a bearing on one of them.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi, Thanks for your reply.
It is Windows Vista Business 32-bit Operating System with Service Pack 2 and all latest updates.
By the way, I have tried adding myself as a specific user to HKLM/Software/Apple Computer, Inc./QuickTime (Right-click) Permissions... to no avail.
Thanks for any ideas.
Mike. - 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
By the way, I have tried adding myself as a specific user to HKLM/Software/Apple Computer, Inc./QuickTime (Right-click) Permissions... to no avail.
Good gracious ... you tracked down the "stejskal family special" instructions? (It's certainly what was occurring to me when I saw your symptoms.)
Still ... with that one, most commonly it would be only one of the user accounts on the PC that was launching QuickTime/iTunes (and the others would be erroring). Often, it would be standard user accounts rather than admins that were erroring too. You've got something very similar-looking, but it's almost the mirror image of that particular problem.
Wondering ... in the course of your troubleshooting to date, have checked on the registry entries for the QuickTime preferences file in the troublesome user account? (Usually that'll cause display problems nowadays, but conceivably if it's mucked up in just the right way, it could cause a user-account-specific launch error.)
In regedit, select:
HKEYCURRENTUSERSoftwareApple Computer,Inc.QuickTimeLocalUserPreferences
There should be a FolderPath entry in that key with the following value:
C:Documents and Settings<YourUserAccountName>Local SettingsApplication DataApple ComputerQuickTime
Is the correct name for your user account in that path?
If it is, also check the permissions on that particluar key. Does your user account have full control?
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Thanks for your perseverence.
The key, path and permissions pointing to my user account version of QuickTime.qtp are all present and correct. Full control is inherited from the HKCU top level.
Its a conundrum isn't it.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Just a thought ... the new QuickTime 7.6.6 version was released today. Perhaps try installing that. If you get an error saying a Registry key could not be opened or created, note down the precise name of the Key. (If you get a different sort of error let us know what's going on with that.)
Roughly speaking, the hope is that we can use the 7.6.6 update as a "registry check". If there is a problem with a key, that might cause an install error and the error message for the install might give us a heads up on the key that may be giving us grief here.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Well, it has done something... I now get a different error message - now from Windows: "Quicktime Player has stopped working. A problem caused the program to stop working correctly Windows will close the program and notify you if a solution is available".
In more detail:
- Downloaded QuickTimeInstaller.exe to my own hard drive.
- Ran the installer from my (Administrator) account.
- The install process complained about IE and iTunes helper being active - it couldn't shut them down down so I shut them both down manually.
- The install completed with no other complaints.
- I rebooted for good measureIn my (Administrator) account, firing up QT from 'Start' menu gives the error "Microsoft Windows - Quicktime Player has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available".
Trying to open a QT page in IE causes IE to ask to install quicktime.
In Google Chrome (which used to work) the apple quicktime troubleshooting page recognises the add-in but trying to view the Scott Pilgrim trailer invokes the same 'stopped working' Windows error. Oddly dropping a (previously working) .mov file onto chrome plays it just fine. Similarly, iTunes plays the aforementioned .mov file Ok.In the user (non-Administrator) account and the 'hidden' Administrator accounts, everything works just as it should - as before.
As an aside, this version seems more sensitive to .mov variations. For example, from this site:
http://www.dreamguitars.com/preowned/alberico/albericogrand_auditorium_roxanna_82/alberico_grand_auditorium_roxanna82.php
The movie has no sound (I do get a dialog on the first occasion asking to download extra components - but that doesn't seem right). If I try using chrome I get an error - "The following plug in is unresponsive - would you like to stop it"
Just to be thorough, I thought I'd do it all again and due to a random brainwave decided to also uninstall DivX too just in case there was a codec problem. So, I uninstalled DivX, QuickTime, Apple Application Support (using Revo Uninstaller). Emptied the recycle bin. Rebooted (iTunes error on start-up - not a surprise). Installed QuickTime from local drive. Rebooted...
...no difference at all.I'm nothing if not persistent - any other ideas/clues?
Thanks,
Mike. - 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Well, it has done something... I now get a different error message - now from Windows: "Quicktime Player has stopped working. A problem caused the program to stop working correctly Windows will close the program and notify you if a solution is available".
Not necessarily significant I'm afraid, Mike. Error messages for the same issue tend to differ from version of QuickTime to version for the same sorts of problems.
On the other hand, if it's throwing one of those, Vista will be recording problem reports for the issue.
Generate a few more of those errors, making a note of the time showing on the PC when the reports are generated. Now head into your Problem Reports and Solutions control panel and look for QuickTime problem reports generated at the time of the errors. Open then up and have a look through them.
Are they all saying roughly the same thing? If so, paste the contents of a report here so we can have a look at it. (The details may suggest something specific we can follow up on.)
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Do you mean this... (yes, they are all very similar)
Product
QuickTime PlayerProblem
Stopped workingDate
01/04/2010 22:16Status
Report SentProblem signature
Problem Event Name: APPCRASH
Application Name: QuickTimePlayer.exe
Application Version: 7.66.71.0
Application Timestamp: 4ba1a755
Fault Module Name: StackHash_7bb1
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 00000000
OS Version: 6.0.6002.2.2.0.256.6
Locale ID: 2057
Additional Information 1: 7bb1
Additional Information 2: 5146db5664ecadcc8706d7e4905cf83f
Additional Information 3: 3000
Additional Information 4: a866469466f008e5248e3bfff1245eb2Extra information about the problem
Bucket ID: 1784779563 - 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Fault Module Name: StackHash_7bb1
... but of course. A Stackhash is Vista's way of saying "I don't know what module caused the crash". (Roughly equivalent to XP's "unknown module" result.)
Okay ... working on the theory that we've got some subtle problem associated with permissions either for the user account itself, the administrators group, or possibly even the System account. Although we don't know which file, folder or key is involved, we can try a shotgun approach.
Perhaps try the procedure from the following weblog entry, Mike:
[Solving setup errors by using the SubInACL tool to repair file and registry permissions|http://blogs.msdn.com/astebner/archive/2006/09/04/solving-setup-err ors-by-using-the-subinacl-tool-to-repair-file-and-registry-permissions.aspx]
A couple of things before proceeding.
(1) Prior to doing the subinacl run, I'd be strongly inclined to set up a system restore point.
(2) When in Notepad, editing the two YOURUSERNAME values in the reset.cmd batch file, be sure all the 9 lines of the file start on a different line. (The lines have been getting smooshed together in the reset.cmd for some folks, and the commands don't work then.)
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Very well done! Problem fixed. Thanks.
Whilst the problem may have been a subtle permissions issue, there is nothing subtle about the fix which is VERY thorough and generated a 1.8GB log file (I couldn't find anything capable of opening it as it was so big). It also seemed to trample over my Google toolbar - but nothing a reinstall didn't fix. Reassuring to have a restore point.
Top work B.Noir.
Many thanks,
Mike. - 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Excellent news, Mike!
Whilst the problem may have been a subtle permissions issue, there is nothing subtle about the fix which is VERY thorough and generated a 1.8GB log file
... yes, "shotgun" might have been understating things a bit. Sorry about that ...
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Mmm.. Though it did undoubtedly solve my problem, Acrobat distiller now won't work. Of the two, I think I'd rather have Acrobat than Quicktime - so, I've given up and gone back to the system restore point. Hey ho...
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Acrobat distiller now won't work.
What's the error message with Distiller, Mike?
(Adobe products can be prone to the same sorts of weird ACL errors as QuickTime, although Flash is the most common one to get caught by this sort of thing.)
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
No error message. I was printing to Adobe PDF "printer". The Adobe Save File As dialog came up as expected, the Adobe Creating Adobe PDF dialog started to fill out the progress bar, got 1/3 of the way accross then silently curled up and died.