-
All replies
-
Helpful answers
-
Jan 27, 2015 8:46 AM in response to dret58by Brett L,Howdy dret58,
If you are having an issue with your Software Update for Windows application such as crashing, I would suggest removing and reinstalling it. Use the steps in this article -
How to repair Software Update for Windows
Thanks for using Apple Support Communities.
Best,
Brett L
-
Jan 27, 2015 10:34 AM in response to Brett Lby dret58,Unfortunately I have already tried a repair install as well and that has not solved the problem.
Andre
-
Jan 28, 2015 8:47 AM in response to dret58by Brett L,Hi dret58,
Thank you for using Apple Support Communities. Due to the nature of the issue you described you may find more information by using another one of Apple's support resources - https://getsupport.apple.com/GetproductgroupList.action.
Brett L
-
Jan 28, 2015 2:37 PM in response to Brett Lby dret58,I do not currently have an Apple device, computer or otherwise, to receive Apple support. If someone that is interested in following up with this case that does have access to the above linked AppleCare support, I would be more than willing to feed information and logs for the purpose of resolving this issue. To start, here is the basic crash information provided:
Problem signature:
Problem Event Name: APPCRASH
Application Name: SoftwareUpdate.exe
Application Version: 2.1.3.127
Application Timestamp: 4de6dd5a
Fault Module Name: OLEAUT32.dll
Fault Module Version: 6.0.6002.19216
Fault Module Timestamp: 5441bd96
Exception Code: c0000005
Exception Offset: 000049d6
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
Additional Information 1: fd00
Additional Information 2: ea6f5fe8924aaa756324d57f87834160
Additional Information 3: fd00
Additional Information 4: ea6f5fe8924aaa756324d57f87834160
iTunes has not been compatible with the Windows Vista Data Execution Prevention (DEP) framework since version 11.2 and along with its related components has seemed to get less reliable on Vista over time. I am not quite sure why Apple decided to completely revise the background task execution model beyond iTunes 11.1.5, it has resulted in unnecessary incompatibility with Windows Vista, and in cases, Windows 7 while all other programs designed for Windows NT 6+ run without error.
To be more complete, I have scanned system files (scannow) on the Vista x64 machine and they are all intact and without corruption. I also maintain a fully updated Windows environment. The hard disk containing the OS and Software Update/iTunes is also free of disk errors (chkdsk). Windows updates that most closely preceded the inconsistent crashing and update suggestions were: .NET Framework 4.5.2 and several Vista x64 Security Updates (KB3022777, KB3019215, KB3021674).
-
Jan 28, 2015 2:47 PM in response to dret58by dret58,I have also confirmed that the OLEAUT32.dll is in the correct location and properly registered.
-
Feb 3, 2015 4:48 PM in response to dret58by turingtest2,For general advice see Troubleshooting issues with iTunes for Windows updates.
The steps in the second box are a guide to removing everything related to iTunes and then rebuilding it which is often a good starting point unless the symptoms indicate a more specific approach. Review the other boxes and the list of support documents further down the page in case one of them applies.
Your library should be unaffected by these steps but there is backup and recovery advice elsewhere in the user tip.
If you are running 64-bit Windows and the above steps haven't helped try installing the version of iTunes that can be downloaded from this support document. iTunes 12.1 for Windows (64-bit — for older video cards)
tt2
-
Feb 3, 2015 5:58 PM in response to turingtest2by dret58,A complete uninstall and reinstall of iTunes and related components has not resolved the issue. Today I did another complete uninstall of iTunes 12.01 and related components and installed the latest 64-bit version of iTunes (12.1). The Software Update issue still persists. I have no trouble whatsoever installing updates for individual components using installer (.msi) files or installer packages, but the Software Update application is crashing or failing to diagnose updates correctly.
-
Feb 3, 2015 6:14 PM in response to dret58by turingtest2,I don't have any experience with the software update symptoms you describe. Ordinarily I would suggest flushing your browser's cache and blowing away the folder C:\Users\<USer>\AppData\Local\Apple\Apple Software Update but since mine is empty I'm not sure that is at the bottom of the problem. Apart from the issue with ASU are you able to get either the current or the previous build of iTunes to install and run?
tt2
-
Feb 3, 2015 8:26 PM in response to turingtest2by dret58,Both the previous build and current build of iTunes install and run properly, the well documented DEP incompatibility and crash upon exit notwithstanding.
No dice on the folder deletion and browser cache clear solution.
I think I have isolated a likely cause. As part of a batch of Windows Updates, which I installed on December 3, 2014, a Security Update (KB3006226) replaced system file oleaut32.dll with a new version (version date: 10/17/14) of the file. It also updated one or two more files relating to the OLE registration in the Windows operating system, and seemed to do so for many versions of Windows including: Windows 7, Windows 8, Windows 8.2, Windows Vista, and Server, etc. Under the OLE registration heading in the System Information program I find entries for many programs such as Excel, Word, a few science tools I use, etc, but no entry for Apple Software Update. I wonder if ASU, not having been updated itself in quite some time, is programmed to invoke a particular version of oleaut32.dll or is otherwise incompatible with the new version? The issues with ASU seemed to follow this update.
@turingtest2: Do you have any connections to Apple devs or support that would look into this issue?
Have any other Windows users, particularly those still using Vista, noticed this behavior and crash dialogue while using ASU?
-
Feb 4, 2015 12:04 AM in response to dret58by turingtest2,★HelpfulNor really my area of expertise, but my understanding is that Windows can support multiple versions of common libraries so that each application can use the version it was developed with. I have 18 copies on my C: drive.
I'm afraid I don't have an inside track to Apple. You can report problems via the relevant feedback form, e.g. iTunes Feedback, or sign up for a free Apple Developer Connection account and make use of Apple Bug Reporter. They don't generally talk back, but they do claim to read everything.
I've not noticed anyone else complaining of issues with ASU. In you shoes I might be tempted to simply uninstall the component and update iTunes by hand when I choose.
tt2
-
Feb 6, 2015 1:55 PM in response to turingtest2by dret58,Thanks much! I will follow up with the bug reporting and we shall see if a workaround or solution can be found. It is true that Windows supports the use of multiple versions of the same common library simultaneously, but not within the same directory of course! Also, programs must be written to look for a particular library in a particular location. In the case of ASU it seems to look for the version that is located in C:\Windows\system32. I tried extracting the original oleaut32.dll from my recovery disks and placing it within the program file folder for ASU to no avail. I was also unable to properly register the older version of oleaut32.dll within the system32 folder after removing the new version, it just over-wrote the version number to that of the new version, so the error persisted even still. Not sure if Apple or Microsoft will have much incentive to release a bug fix for such an old platform, Vista, unless oleaut32.dll was similarly updated on newer versions of Windows as well. Ahh well...
-
Feb 6, 2015 2:12 PM in response to dret58by turingtest2,I think it is more complicated than that, not that I really have a handle on the details. See here for example: http://en.wikipedia.org/wiki/Side-by-side_assembly. Suffice it to say that any given application might not always be using the version of the .dll you assume it would.
tt2
-
Feb 6, 2015 3:07 PM in response to turingtest2by dret58,Touche. I just checked my winsxs folder and have 12 versions of oleaut32.dll myself. I wonder if the ASU manifest is written to use the latest version of the file, whatever that may be, and now it's incompatible? Anyhow, these are intriguing lines from the wiki:
"On Windows Vista and later, sxstrace.exe can help to diagnose failures in the starting of applications due to SxS misconfiguration.
If a user wishes to override manifest-specified assemblies (for example, in the case of security patches applied to a library), a publisher configuration file can globally redirect assemblies. Digital signatures can ensure that the legitimacy of such redirection."
I feel for security purposes doing the later would not be a good idea. But I'll see if running the program proves diagnostic.
-
Mar 7, 2015 12:11 PM in response to dret58by Johnny DEP,Interesting thread. I'm running 32-bit Vista and cannot duplicate your issue at the moment. However it appears that a more recent version of oleaut32.dll was installed by a Windows update on February 13 (6.0.6002.19243, modified 11/25/14). Has the new dll solved your issue?
So have the recent changes to 64-bit iTunes put an end to BEX errors on 64-bit Vista? It's still crashing on 32-bit Vista I'm afraid.
