When trying to install a driver using Microsoft Driver Package Installer DPInst I got error 0xE0000247.
I tried to check the error code with Visual Studio Lookup Tool but the tool doesn't know this error code. Also MSDN doesn't help here.
How can I lookup the meaning of this error ?
Below a fragment of my DPINST.LOG file:
INFO: Install option set: Running in quiet mode. Suppressing Wizard and OS popups.
INFO: Install option set: legacy mode on.
INFO: Install option set: Suppressing EULA.
INFO: Install option set: Force install if driver is not better.
INFO: Install option set: Suppress Add or Remove Programs entries.
INFO: Found driver package: 'C:\Program Files (x86)\MyApp\my_driver.inf'.
INFO: Preinstalling 'C:\Program Files (x86)\MyApp\my_driver.inf' ...
INFO: ENTER: DriverPackagePreinstallW
INFO: RETURN: DriverPackagePreinstallW (0xE0000247)
INFO: Returning with code 0x80010000
Straight from SetupAPI.h (irrelevant lines omitted):
#define APPLICATION_ERROR_MASK 0x20000000
#define ERROR_SEVERITY_ERROR 0xC0000000
#define ERROR_DRIVER_STORE_ADD_FAILED (APPLICATION_ERROR_MASK|ERROR_SEVERITY_ERROR|0x247)
So your error is ERROR_DRIVER_STORE_ADD_FAILED which is a generic error code returned by SetupCopyOEMInf which in turn is called by DriverPackagePreinstall internally.
The cause of this error is poorly documented but doesn't seem to be related to any specific type of error (hence I called it "generic"). The name itself suggests that the driver could not be added to the driver store (or the DIFx driver store for OS versions prior to Windows Vista) which could have various reasons (insufficient access rights, validation of the driver package failed, ...).
From personal experience I can tell you that most of the time when this error occurs there is a problem with the certificate used to sign the driver package on 64-bit Windows. (Which should really be one of the CERT_E_* error codes, but well...)
Related
I am new to python, I am trying to install Anaconda.
While Installation I am Getting Error _Conda.exe stopped working.
Please Help me With this.
Thanks in Advance.
I did some searches on google regarding this problem,but not getting Exact solution for this.I did uninstalled all my previous python software. Also tried by Deleting Existing Path= in Environment Variables also turned off antivirus and windows defender while installation but none of this solved my problem.
Here is the Error Details
Problem signature:
Problem Event Name: APPCRASH
Application Name: _conda.exe
Application Version: 0.0.0.0
Application Timestamp: 5b8e98f9
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18247
Fault Module Timestamp: 521eaf24
Exception Code: c0000005
Exception Offset: 0000000000027689
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 9fdb
Additional Information 2: 9fdba2a63f4c2dea094e8a8465242f54
Additional Information 3: ed92
Additional Information 4: ed92830c2b0ac5dd397a2c4181ba244e
I also had the error pop-up conda.exe stopped working while installing Anaconda 3 (2020.02.0.0) in Windows 8.1 and this is what worked for me:
Go to My Computer > Properties > Advanced System Settings > Environment Variables and search if there are related user environment variables from previous Conda or other Python packages installations:
Variables PYTHONHOME or even a PYTHONPATH may have been created by any Python distribution.
Variables starting by CONDA_* (for example CONDA_DEBUG) created in previous installation tries.
Delete this user environment variables. If you are not sure about this step, note the variables you delete in order to be able to set them again later if this does not work.
Temporarily disable your antivirus during installation (this is recommended in Anaconda documentation).
Start your installation again.
This Error occurred to me while installing "Anaconda3-2020.02-Windows-x86",
my short answer is to install "VS C++ Redist", I installed version 2019 and it worked fine for me and solved the problem.
.
Here is how I came to that conclusion:
I tried to reproduce the problem by executing the same command the installer executed to generate the same error, first I used windows Task Manager to find the command arguments passed to "_conda.exe", Then I started CMD and executed the following line:
"C:\ProgramData\Anaconda3\_conda.exe" constructor --prefix "C:\ProgramData\Anaconda3" --extract-conda-pkgs
This generated an error regarding a DLL file "api-ms-win-core-localization-l1-2-0.dll" that is usually included with the C++ runtimes.
ps. I usually use Sereby's AiO Runtimes to install all runtimes at once!
I downloaded bitcloud, the atmel zigbee stack and I am trying to compile one of the default applications, ZLLDemo.
It is located currently at:
C:\Users\Ryan\Desktop\BitCloud_MEGARF_3_1_0\Applications\ZLLDemo\atmelStudio_projects\ATmega256RFR2.cproj
Everytime I try to compile the application I get a windows message screen for "mkdir.exe" error 0xc0000142. In the Output screen I see the line "make: *** [directories] Error -1073741502"
This same error and error code occurs later in the build process for cp.exe if I manually make the folders myself.
I have tried the following things to fix the error:
Change folder and contents to different owners, everyone having full
privileges
run make command manually from a command prompt window as admin
clean solution before retrying
all other examples files
ran directly from C: as "C:\BitCloud_MEGARF_3_1_0\Applications\ZLLDemo\atmelStudio_projects\ATmega256RFR2.cproj" - as per general suggestion for the windows error I tried
"sfc /scannow" in case mkdir had somehow been corrupted
Changed AppInitDLLs Reg key to 0 to load all DLLs at start of application
Disabled Internet security
Does this have a general fix or is there perhaps something else at work here? General compilations work, its just external ones. My friend did the same and it seems to work just fine for him.
Windows 8.1
Atmel Studio 6.2
Avrfreaks had a solution that I finally found here.
Their solution is to download an old version of the msys file for winavr. Which means that their is something more than likely wrong with the latest version of winavr for windows 8.1
sebastor wrote:
I found solution.
Copy this file:
http://www.madwizard.org/download/electronics/msys-1.0-vista64.zip
to utils\bin directory (WinAVR)
Has any one encountered the error: Could not create Java Virtual Machine error while installing IBM Websphere ILog JRules Studio 7.1.1? I have Windows 7 64 bit OS but this error could happen on any Windows machine. By default IBM ships the package for 32 bit so our installation team tried with 32 bit JDK 6 (with many minor versions) for many days but could not figure out. I have posted my own solution below. Check this out and save your life.
You usually start installation by running JRules_V711_CZLX7ML.exe file on windows. It will extract all resources on your temp directory and you might encounter error: "Could Not Create Java Virtual Machine". Just follow these steps and it "might" solve your problem:
1. Go to your temp directory by typing "%temp%" in Start-> Run or Windows Explorer.
2. Look for directory something like: I1403739667. Go inside this directory.
3. Open command prompt and go to I1403739667/Windows/resource/jre/bin
4. Run command: java -version
5. If you see following error, go further otherwise you might have some other problems:
JVMJ9VM011W Unable to load j9jpi24: The specified module could not be found.
Error: could not load Mercury Interactive support. Please run the setup again.
If the problem persists please contact Mercury's Customer support.
JVMJ9VM011W Unable to load j9jpi24: The specified module could not be found.
JVMJ9VM015W Initialization error for library jvmhook(-3): JVM_OnLoad failed
Could not create the Java virtual machine.
This happens if you have installed HP Quick Test Professional which used to be Mercury before HP bought over.
Right click on your computer icon on desktop and look for following environment variable: IBM_JAVA_OPTIONS
Either rename it to IBM_JAVA_OPTIONS_DONOTUSE or delete it.
Try installing again.
NOTE: I had tried to by pass this error by changing the vm property in Rule Studio.lax file to use JDK 6 32 bit installed on my windows machine and was able to install successfully but there were just too many Rules compilation errors which would not make any sense. So NEVER try to use your own JDK. You have to use the IBM JDK shipped as part of Rule Studio.
I tried to install WinDivert in my machine (Windows 7 64-bit OS). I tried with both 32-bit and 64-bit version. However, I failed at both of the cases and received the error message: "error: failed to open Divert device (110)". I followed Section 2 (Steps 2.1 and 2.2) of the tutorial: http://reqrypt.org/windivert-doc.html. I used "Free Build Environment" (x86/x64). I invoked wddk-build.bat. Then I signed the driver as it has been shown in the document (just as it is written). I restarted the machine and tried to run "netdump" and "netfilter" from "install/WDDK/..." from the command prompt. However, nothing works for me. Even I tried with the MS Visual Studio 10 (masvc-build.bat). What is the issue, I am suffering with?
WinDivert 110 error usually indicates that the driver failed to load. This can be caused by a number of different things. The checklist for a WinDivert (110) errors would be:
Make sure that you are using the 64-bit driver only for 64-bit systems, and the 32-bit only for 32-bit systems
Make sure the driver is properly signed (or test-signed with Windows test-mode enabled)
Make sure the WinDivert driver files (WinDivert.sys, WinDivert.inf, WdfCoInstaller*.dll) are in your program's directory when DivertOpen() is called.
Make sure you are running the program with Administrator privileges.
Usually one of the above is causing the problem.
EDIT: Some stubborn 110 errors can be fixed by manually stopping/starting the WinDivert service, e.g. by running the following commands as Administrator:
sc stop WinDivert1.0
sc delete WinDivert1.0
EDIT (2): Note that WinDivert (110) errors have been replaced with more meaningful error codes in version 1.0.3 and above.
I'm trying to debug a 32 bit process dump from a process that ran on an x64 machine. I'm running an x86 version of windbg on my x64 laptop. I've followed the recommendations here, but I'm still getting this:
0:000> .cordll -ve -u -l
CLR DLL status: No load attempts
0:000> !clrstack
CLRDLL: C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscordacwks.dll:4.0.30319.17020 f:8
doesn't match desired version 4.0.30319.237 f:8
CLRDLL: Loaded DLL c:\symbols\public\mscordacwks_x86_x86_4.0.30319.237.dll\4DD234A8670000\mscordacwks_x86_x86_4.0.30319.237.dll
Failed to load data access DLL, 0x80004005
Verify that 1) you have a recent build of the debugger (6.2.14 or newer)
2) the file mscordacwks.dll that matches your version of clr.dll is
in the version directory
3) or, if you are debugging a dump file, verify that the file
mscordacwks_<arch>_<arch>_<version>.dll is on your symbol path.
4) you are debugging on the same architecture as the dump file.
For example, an IA64 dump file must be debugged on an IA64
machine.
You can also run the debugger command .cordll to control the debugger's
load of mscordacwks.dll. .cordll -ve -u -l will do a verbose reload.
If that succeeds, the SOS command should work on retry.
If you are debugging a minidump, you need to make sure that your executable
path is pointing to clr.dll as well.
As far as I can determine, mscordacwks_x86_x86_4.0.30319.237.dll is successfully loaded, but I still get the error. What am I missing?
I resolved the issue by using ProcDump to get 32bit dump of the 32bit process that was running on a 64bit machine. I can successfully examine that using 32bit windbg. There are more details in this blog post.
It looks like you have a 32-bit dump file - otherwise the error would look like
CLR DLL status: ERROR: Unable to load DLL mscordacwks_AMD64_x86_2.0.50727.3053.dll, Win32 error 0n87
At least that's according to the blog post “Failed to load data access DLL, 0x80004005” – OR – What is mscordacwks.dll? on the Notes from a dark corner blog.
Note the mix of AMD64_x86 vs the x86_x86 in your error message.
For me, it's always because I don't have the correct version of mscordacwks. It's also possible windbg can't find it. See my answer to Problem debugging hang-dump in windbg for one method I've used to find/extract the correct version from security patches. To get windbg to load it, I set set the image path for windbg to point to the directory I've stored it in.