debug the oleaut32.dll version

I am looking for a place to get a debug version of the oleaut32.dll file to disable caching for BSTR allocations.

Advise please, where I can find a. I have Win7 and WinXP


Because the problem is related to the type BSTR I suggest you to post the question on the MSDN forums for assistance.

I hope this helps!

Tags: Windows

Similar Questions

  • Lsass.exe - Unable to locate component. This application has failed to start because the oleaut32.dll file not found

    Original title: oleaut32.dll xp

    My system XP pro/sp3 does not start normally, without danger or with the original sys disk. I get a message
    Isass.exe - Unable to locate component. This application has failed to start because the oleaut32.dll file not found. reinstalling the application may fix this problem.
    However, I can't in the operating system to do a re-install.
    Any suggestions?

    If c:\windows\system32\oleaut32.dll is missing, you will see messages like this:

    Lsass.exe - Unable to locate component
    This application has failed to start because the OLEAUT32.dll file not found.  Reinstalling the application may fix this problem.

    If the missing file is the only problem, you might have to do a reinstall to fix.

    There should be a copy of Oleaut32.dll in the c:\windows\system32\dllcache folder, so if you can get in the XP Recovery Console, you can just replace it - then you are going to have to start on something to do.

    Once started in the XP Recovery Console, you must enter this command at the prompt:

    Copy c:\windows\system32\dllcache\oleaut32.dll c:\windows\system32

    If the file is not in the dllcache folder (it should really be), depending on your installation, this command can work:

    Copy c:\windows\servicepackfiles\i386\oleaut32.dll c:\windows\system32

    Answered in the affirmative if invited to replace any existing file.

    I don't know what the Microsoft Support Engineer think that KB307545 or KB922371 will help you.  I think that the MSE is just throw a few things to try and some links.  You don't describe symptoms consistent with the need to use one of these methods.   I would say the MSE has never seen this problem before, made no attempt to reproduce the problem, and has no idea how to fix this.

    If your CD does not start in the Recovery Console, or if you don't know what kind of CD do you have to do a CD of XP Recovery Console and boot on it (no media XP required).

    Here's how:

    Boot into the Recovery Console Windows using an XP bootable installation CD.

    If you have no XP bootable media (or aren't sure you have) create a bootable XP Recovery CD of Console and do not forget.

    This is not the same as recovery disks that might have come with the acquisition of the system store.

    You can make a bootable Recovery Console CD by downloading an ISO file and burn it to a CD.

    The ISO bootable image file you need to download is called:

    xp_rec_con. ISO

    Download the ISO from here:

    Use a new CD and this simple and free program to burn your ISO file and create your bootable CD:

    When you install ImgBurn, DO NOT install the Ask toolbar.

    Here are some instructions for ImgBurn:

    It would be a good idea to test your bootable CD on a computer running.

    You may need to adjust the computer BIOS settings to use the CD-ROM drive as the first device to boot instead of the hard drive.  These adjustments are made before Windows tries to load.  If you miss it, you will need to restart the system again.

    When you start on the CD, follow the instructions:

    Press any key to boot from CD...

    Installing Windows... going to pronounce.

    Press 'R' to enter the Recovery Console.

    Select the installation that you want to access (usually 1: C:\WINDOWS)

    You may be asked to enter the password (usually empty).

    You should be in the folder C:\WINDOWS.  It's the same as the

    C:\Windows folder that you see in Solution Explorer.

    The Recovery Console allows base as file commands: copy, rename, replace, delete, chkdsk, fixboot, fixmbr, cd, etc.

    For a list of the commands in the Recovery Console, type help at the prompt of commands or read on here XP Recovery Console:

    After replacing the file, remove the CD and type 'exit' to leave the RC and restart the computer.

    You have not to set the BIOS to boot the disk HARD since the CD won't be.

  • "The program can't start because the OLEAUT32.dll file is missing from your computer. Try reinstalling the program to fix this problem.

    Someone knows how to fix this error keeps coming and stop loading applications?

    Hi DuaneXX,

    ·         You did changes to the computer before the show?

    ·         What programs do you speak?

    Follow these steps:

    Step 1: Start the computer in safe mode and check if the problem persists.

    Start your computer in safe mode

    Step 2: If the problem does not persist in safe mode, perform a clean boot to see if there is a software conflict as the clean boot helps eliminate software conflicts.

    Note: After completing the steps in the clean boot troubleshooting, follow the link step 7 to return the computer to a Normal startupmode.

  • Oleaut32.dll seems to be on the computer but the 3rd party install can't find it

    A brief history. I got the Itunes error for months. I lived with him (after failed it several attempts at correction). To do this, I'll post the following event log error. Now I am trying to install software for a video camera and it can not find the file oleaut32.dll (this time in the System32 directory). I bought and run the RegServe software to solve registry problems (which was supposed to go to fix this). Now, I'm getting several other errors in the event log (unrelated to the errors of the oleaut32.dll file) after the execution of this software. I tried to repair Itunes after the register of difficulty in case he had to just update its links. No luck. No luck on installing the camera software. I installed optional updates from Microsoft incase they might also need this dll file and therefore would set the record link. No luck. (but no installation failure).

    Here is the series of errors in the log of events from when I tried to fix itunes:

    Application MsiExec.exe, version 4.5.6002.18005, time stamp 0x49e01c42, module OLEAUT32.dll, version 6.0.6002.18005, time stamp 0x49e037da, exception code 0xc0000006, offset error 0x0006c7e7, 0x9f4, failed failed application start 0x01cae48391384bf1 process id.


    Windows cannot access the file C:\Windows\SysWOW64\oleaut32.dll to one of the following reasons: there is a problem with the network connection, the file is stored on the disc or the storage drivers installed on this computer. or the drive is missing. Windows has closed the installer program for Windows® because of this error.

    : Program Windows® installation

    File: C:\Windows\SysWOW64\oleaut32.dll

    The error value is listed in the additional data section.

    User action

    1. open the file again. This could be a temporary problem that can be corrected when the program runs again.

    2. If the file is still not accessible and

    -C' is on the network, your network administrator must verify that there is not a problem with the network and that the server can be contacted.

    -C' is on a removable disk, for example, a floppy disk or a CD-ROM, check that the disc is inserted into the computer.

    3. check and repair file system by running CHKDSK. To run CHKDSK, click Start, run, type CMD and then click OK. At the command prompt, type CHKDSK /F and then press ENTER.

    4. If the problem persists, restore the file from a backup copy.

    5 determine whether other files on the same drive can be opened. If this is not the case, the disc could be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for assistance.

    Additional data

    Error value: C000009C

    Disc type: 3


    Fault bucket 5215083, type 5

    Name of the event: InPageCoFire

    Answer: no

    Cabin ID: 0

    Signature of the problem:

    P1: c000009c

    P2: 00000003

    P3: oleaut32.dll








    Attached files:


    These files are available here:


    I'm not terribly computer literate, but I can not follow :) if someone could help me please. We just got back from holiday and have lots of pictures on this camera, that we want to download. I think that if I can fix it a mistake oleaut32 that it will solve all? Oh, I tried the chkdsk command and it will not work up to what my next reboot because the disc is in use... and I do not search the forums for all notes with this file name, but was the only one with windows update issues and I was afraid to try because my updates were actually on the job so far.


    Update: now IE is the error and hanging (attempt to close):

    Failed application iexplore.exe, version 8.0.6001.18904, time stamp 0x4b835fec, failed module OLEAUT32.dll, version 6.0.6002.18005

    error trying to install the camera software:

    Application Setup.exe_InstallShield (R), version, time stamp 0x3b95f860, module OLEAUT32.dll, version 6.0.6002.18005, time stamp 0x49e037da, exception code 0xc0000006, offset error 0x0006f828, 0xee4, failed failed application start 0x01cae4c22a7ac136 process id.

    When I tried to run chkdsk on reboot, it continues to give me the message of direct access is not make the record (or something of the sort) and then abandons the chkdsk

    seems to be fixed by a sfc/scannow (who said that he could not address all the wrong file)...

  • I want to download this file missed: oleaut32.dll

    I want to download this file missed: oleaut32.dll

    You see messages like this:

    Lsass.exe - Unable to locate component
    This application has failed to start because the OLEAUT32.dll file not found.  Reinstalling the application may fix this problem.

    If you click OK, you will see:

    Userinit.exe - Unable to locate component
    This application has failed to start because the OLEAUT32.dll file not found.  Reinstalling the application may fix this problem.

    If you click OK, you will see:

    Explorer.exe - Unable to locate component
    This application has failed to start because the OLEAUT32.dll file not found.  Reinstalling the application may fix this problem.

    I put a copy of my file oleaut32.dll XP Pro Service Pack 3 on my Skydrive and you can download it, but it should be already at least another copy on your system so that you shouldn't have to download to solve the above problem.

    Here is the link:! 191

    Now you can download.

    You run AVG?

    Is it just a fantasy of mine that the MS Answers forum will never ask for basic system information when a new question is asked?  I don't even have to fill out a questionnaire when I take my dog to the vet.

  • Event ID: 1000 Faulting application devenv.exe, version 8.0.50727.762, stamp 45716759, failed module gdiplus.dll, version 5.2.6001.22319, time stamp 4a841b37, debug? 0, address of failure 0x0001bf5e

    My repeateedly of crash of visual studio 2005 in 10-20 minutes

    with the following error

    Event ID: 1000

    Failing application devenv.exe, version 8.0.50727.762, time stamp 45716759, failed module gdiplus.dll, version 5.2.6001.22319, time stamp 4a841b37, debug? 0, address failure 0x0001bf5e.

    Event ID: 1023

    .NET runtime version 2.0.50727.3615 - engine error fatal execution (7A2E1122) (0)

    Hi ashnov,

    1. did you of recent changes on the computer?

    2 when was the last time it was working fine?

    Method 1

    I suggest that you install the updated drivers for the graphics card on the computer by visiting the card manufacturer or the manufacturer of the computer Web site to download and install the drivers, check if it helps.

    How to manage devices in Windows XP

    Method 2

    If the previous step fails, then I suggest that you do the system restore and check if it works.

    How to restore Windows XP to a previous state

    Method 3

    I suggest that scan you SFC on the computer that would be a system file corrupt on the computer search and replace.

    The analysis may take some time, so be patient. Windows allows to fix corrupt or missing files it finds. If the information of the installation CD is required to fix the problem, you may be asked to insert your Windows XP installation CD.

    Description of Windows XP and Windows Server 2003 System File Checker (Sfc.exe)

    Method 4

    If the steps above fail, then reinstall the program and check if that helps.

  • Call Java DAQmx.dll: Y at - it a new version of the DAQmx.dll NET c# for CLR 4.0 library

    I need to use the API of NET c# in a java program, so I tried to use Jni4net library to fill the dll in Java. I get errors however, because the version of daqmx.dll that I have been built against CLR 2.0.50727. Is there a version of the dll for CLR 4.0 (corresponding to .NET 4.0 or higher)?

    If someone know another way to call the java daqmx.dll?


    I eventually found the version I had to work.

    I have the DAQmx.dll assembly. I got an old software project developed for the device, I'm working on that. I guess that the original developer obtained from the disk of National Instruments.

    Thank you

  • Install RDCman 2.2 the use Remote Desktop on windows server 2003 fails with the error: incompatible version of c:\windows\system32\mstscax.dll

    2.2 RDCman install remote desktop on windows 2003 server util fails with the error: incompatible version of c:\windows\system32\mstscax.dll


    Hi Mordi26:

    This could be because windows server 2003 is not updated with the latest version of the Terminal Server client. With terminal services client 6.0 update... It should solve the problem. Here is the link to download:

  • Debug the Version Works, published the Version Does not

    I have a strange problem. I have a desktop in Flex app that works on Mac and Windows. I use IntelliJ to develop the application, and when I debug the application on Mac and Windows using IntelliJ, it works as expected. However, on Windows when I publish the application and run it, it crashes every time after completed certain steps in the application. As this happens not during debugging it, I have no way to determine the cause. Could there be something in their own country worng with the AIR 3.7 and 3.8 Runtime that is not happenning when you run the application using ADL?

    Lee, you know a few api will work on mode debug, but not worked on the final version?

    For example:

    You can load a swf without loaderContext parameter resource file before AIR3.7. It is worked .but. If you use AIR3.7 +... .you should load swf as follows

    "var loaderContext:LoaderContext = new LoaderContext (false null, ApplicationDomain.currentDomain),

    Loader.Load (url, loaderContext);


    It's just a reminder to you.

  • Impossible to debug the example provided with the SDK projects

    Hey there.
    Just recently I started learning the SDK AE. After reading the first two pages of the Guide to the software development kit, I decided to try to build/debug examples of projects in visual studio.
    I tried with the model project "Skeleton" and with the "Resizer effect" project, but the two I can't seem to make it work.

    I set the environment variable AE_PLUGIN_BUILD_DIR for the correct path, and I also made sure visual studio debug using AfterFX.exe
    However, if I try to launch the visual studio debugging (F5)... nothing happens. After effects opens, but nothing happens after that.

    I checked my output log and... Well well full of messages like:

    "AfterFX.exe" (Win32): loaded "C:\Program Files\Adobe\Adobe after effects CC 2015\Support Files\AudioFilters.dll. Cannot find or open the PDB file.

    "AfterFX.exe" (Win32): loaded "C:\Program Files\Adobe\Adobe after effects CC 2015\Support Files\ProjectConverterHost.dll. Cannot find or open the PDB file.

    "AfterFX.exe" (Win32): loaded "C:\Program Files\Adobe\Adobe after effects CC 2015\Support Files\TransmitHost.dll. Cannot find or open the PDB file.

    "AfterFX.exe" (Win32): loaded "C:\Program Files\Adobe\Adobe after effects CC 2015\Support Files\DisplaySurface.dll. Cannot find or open the PDB file.

    "AfterFX.exe" (Win32): loaded "C:\Program Files\Adobe\Adobe after effects CC 2015\Support Files\FLT.dll. Cannot find or open the PDB file.

    "AfterFX.exe" (Win32): loaded "C:\Program Files\Adobe\Adobe after effects CC 2015\Support Files\RG.dll. Cannot find or open the PDB file.
    There are many more of these erros... basically for each DLL in the \Support Files\ folder.

    At the end of my output log, I have the following:

    < 5060 > < AppVers > < 5 > App Version = Version

    < 5060 > < AppDirs > < 5 > App Dir = C:\Program Files\Adobe\Adobe After Effects CC 2015\Support Files

    The executable < 5060 Dir > < AppDirs > < 5 > = C:\Program Files\Adobe\Adobe After Effects CC 2015\Support Files

    Resources < 5060 > < AppDirs > < 5 > Dir = C:\Program Files\Adobe\Adobe After Effects CC 2015\Support Files

    Package < 5060 > < AppDirs > < 5 > Dir = C:\Program Files\Adobe\Adobe After Effects CC 2015\Support Files

    < 5060 > < AppDirs > < 5 > Plugin Dir = C:\Program Files\Adobe\Adobe after effects CC Files\Plug-ins 2015\Support

    < 5060 > < AppDirs > < 5 > required Dir = C:\Program Files\Adobe\Adobe after effects CC 2015\Support Files\Required

    "AfterFX.exe" (Win32): loaded "C:\Program Files\Adobe\Adobe after effects CC 2015\Support Files\aeres1.dll. Cannot find or open the PDB file.

    "AfterFX.exe" (Win32): unloaded "C:\Program Files\Adobe\Adobe after effects CC 2015\Support Files\aeres1.dll.

    The program ' [3244] AfterFX.exe "ended with code 0 (0x0).

    Can someone tell me what I'm missing?

    Well, it is normal that if you launch AE in the debugger, nothing different happens if you launch AE normally. Which means that you must create or load a project and apply your plugin, so you can stop in the debugger (unless you want to catch global initialization, which is made on the loading of the program).

    With regard to the PDB messages in the journal, which is quite ok, as the Adobe dll plugin obviously would not come with debug information.

    The plugins you've compiled are born actually in the correct path? They are available in the menu effects in AE? It is the first thing to check, because when there is not this plugin, debugging is not available :-)

    I interpreted your question so that your .aex files are actually present and visible on EI, you just can't break into the debugger when one of them is used.

    So for your plugin, you must make sure that it contains debug information, otherwise you will not be able to debug.

    Please check the following settings for your project in Visual Studio:

    "C/C++" - "Debug Information Format" value "Program Database"

    "C/C++ - preprocessor"-"Preprocessor Definitions" string contains the "_DEBUG" set

    "C/C++ - Code generation '-'Runtime Library' is defined is ' / MTd ' or ' / MDd" (this is the most common error when unable to debug!)

    ' Linker - debugging - 'generate debugging information' set to 'Yes "".

  • Midas.dll version no while version than expected 10.0.2151

    Hello, starting to loose faith Thinapp after struggling for a while, I hope someone can help.

    I am currently Thinapp an application called Sats Barnehage made by IST. He needs Borland Database Engine in the background, and that seems to work very well I get the question on the user name and password that authenticates indeed correctly.

    However, the Sats software throws a mistake the second I have connection about midas.dll that this is not the correct version, but it seems its not able to not to get the information from the DLL itself as the error with module SAIS NO version before tell me what she expects.

    The file is supposed to be in C:\Windows\syswow64 and I see its place properly in the packaged aswell 32-bit environment like all the registry keys in thinapp correctly pointing to % % SystemSystem

    It works fine on the machine, we capture the package with so it's not a problem with the version of the operating system or environment.

    Enforcement does not at all with Thinapp 4.7.3 so its packaged with 4.6.1.

    I tried the Wow64 = 0 and VirtualizeExternalOutOfProcessCOM = 0 so that the part of ExternalDLLs where I specify file midas.dll unsuccessfully to loading.

    Also tried to go into cmd for debug and register dll start application etc. without success.

    Any suggestion is appreciated.

    VMware KB: Using the ExternalDLLs parameter in Package.ini for ThinApp configuration file

    I tried to use ExternalDLLs =; as described on the page, but when you use ExternalDLLs = inject.dll; injectme2.dll without the <> it worked fine.

  • error AVCFPlayerSetclientEnforcedExternalProjectionMethod is not found in the AVFoundationCF.dll dynamic link library

    I tried to update my iTunes this weekend.  Now, I can't open it I get this error: AVCFPlayerSetclientEnforcedExternalProjectionMethod is not found in the AVFoundationCF.dll dynamic link library is on a Windows 7 computer.  I tried to re - install outside of iTunes and repair.  But no luck.  Should I uninstall iTune and then re-install?  Help.

    These errors can usually be fixed by removing the offending dll, then fix the component it is programs and features Control Panel. AVFoundationCF.dll belongs to Apple Application Support and are normally in

    • C:\Program Files\Fichiers Files\Apple\Apple Application Support or
    • C:\Program Files (x 86) \Common Files\Apple\Apple Application Support

    where the name of the Program Files folder may vary depending on the region.

    For general advice, see troubleshooting problems with iTunes for Windows updates.

    The steps described in the second case are a guide to remove everything related to iTunes and then rebuild what is often a good starting point, unless the symptoms indicate a more specific approach. Review other cases and a list of documents to support further down the page, in which case one of them applies.

    More information area has direct links with the current and recent if you have problems to download, must revert to a previous version or want to try the version of iTunes for Windows (64-bit-for old video cards) as a workaround for the problems of performance or compatibility with third-party software.

    Your library must be affected by these measures, but it is also related to backup and recovery advice if necessary.


  • My error console is always empty, even though I know that there are errors. Work in point 3.6. I noticed the problem around version 8.

    I'm a developer of web application using Windows XP. I work a lot in Javascript and depend on the error console to help debug my code.

    I have updated several times since the 3.6 version, when E.C. still worked. not sure when it stopped, but certainly by the version 8.

    Is there some ports it uses that would affect a victim?

    Any ideas would be more useful.

    No problem here with this error appears in the error Console Firefox 11.

    Error: a is not defined
    Source File:
    Line: 7

    Have you tried resetting the prefs?

    Create a new profile as a test to see if your profile is the source of the problems.

    See "basic troubleshooting: a new profile:

    If this new profile works then you can transfer files from the old profile to the new profile, but make sure not to copy corrupted files.


  • Equium A100 (PSAA4E) the system DLL, user32. DLL has been moved in memory - HHCTRL.ocx

    I have a Toshiba SATELLITE A100 (PSAA4E)
    At the start of this notebook get the following message:

    "The system DLL, user32. DLL has been moved in memory.
    The application will not work correctly. The relocation occurred because the DLL C:\WINDOWS\system32\HHCTRL.ocx
    occupied an area of address reserved for windows DLL system.
    The vendor supplying the DLL should be contacted for a new DLL. »

    The audio drivers from RealTek and the latest version
    I don't really know why it happened.
    Any help would be appreciated.
    In addition, any body knows why my voice on Skype seems to be deformed with a high noice height even if the hearing quality is correct.

    Post edited by: Landric

    Thanks for the comments
    I see you found this thread:

    The same solution was already posted in the thread suggested.

  • When I run the exe file, it should load the niscope_32.dll why?


    I used scope in my program functions,

    and then I did it in the exe file and the installation file,

    but when I make them to another computer,

    To load the niscope_32.dll, what should I do?

    Hi ylongwu,

    You will need to install the driver OR-Scope on the deployment computer so that the code you can call the driver. You can download the driver from our Web site at drivers and updates the link below by searching our driver OR-Scope and choosing the appropriate version. I also recommend that you include the NOR-Scope driver as an extra Installer for your executable. In the setup of window construction there is a category called additional installers where you can choose the drivers and execution engines to install with your executable file. I've included a screenshot to show what it will look like for LabVIEW 8.x.

    Drivers and updates

Maybe you are looking for