WDK: 8.1
VS: 2013 Pro
Host OS: Win 7 x64
Target OS: Win 10 Enterprise N x64
Provisioning fails at installing WDTF (Windows Driver Test Framework):
Log shows:
Initialize: Computer:
Progress event: Current: 11, Max: 17, Message: "Installing driver test framework"
GetMachinePropertiesFromService: Computer Name: DESKTOP-OFDQ6IA
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.3.9600.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: False
Initialize: Computer: DESKTOP-OFDQ6IA
InternalRunTest: Host Computer: ROBI-WIN7
InternalRunTest: Host Architecture: x86
InternalRunTest: Host 64bit Operating System: True
InternalRunTest: Host Operating System Version: 6.1.7601.65536
InternalRunTest: Process Administrator Privilege: True
Initialize: Computer: DESKTOP-OFDQ6IA
GetMachinePropertiesFromService: Computer Name: DESKTOP-OFDQ6IA
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.3.9600.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: False
ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"#Name='Installing driver test framework'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_driver_test_framework_00009.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*" /runas:Elevated
[14:04:20:990]: [Installing driver test framework] Command Line:
te.exe "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"#Name='Installing driver test framework'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_driver_test_framework_00009.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*" /runas:Elevated
Initialize: Computer:
Initialize: Computer:
Created new result:
Path: C:\Users\robi\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing driver test framework 00009.xml
Log Path: C:\Users\robi\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing driver test framework 00009.log
Computer: DESKTOP-OFDQ6IA
Test Binary: msiexec.exe
Test Name: Installing driver test framework
Test Display Name: Installing driver test framework
Initialize: Computer:
RemoteExecute: Binary: msiexec.exe
RemoteExecution: Arguments: /i "%SystemDrive%\DriverTest\Setup\Windows Driver Testing Framework (WDTF) Runtime Libraries-x64_en-us.msi" /qb- KITTARGET=1 /l*v "%SystemDrive%\DriverTest\Logs\Windows Driver Testing Framework (WDTF) Runtime Libraries-x64_en-us.msi_install.log"
Initialize: Computer:
RemoteExecute: Process creation return code: 0
RemoteExecute: Process exit code: 1603
Result completed
Test process exit code: 1603
Result status updated: Fail
Installing manually results in same error. Windows Feature Pack for Win 10 N has been installed.
Ok, I fixed it by running:
WDK 8.1 + VS2013 Pro + Target OS Win 8.1 Pro
Then provisioning went ahead without problems...
Related
I'm on windows 7 64 bit and every time I run vs_Community.exe after downloading it, it stops working and the problem details show this:
Problem Event Name: APPCRASH
Application Name: vs_setup_bootstrapper.exe
Application Version: 2.7.3132.26759
Application Timestamp: 9b581caf
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7c78c
Exception Code: c06d007e
Exception Offset: 000000000000a49d
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: 7283
Additional Information 2: 72836eb6216b49be15302fdb224c1b5d
Additional Information 3: 3a01
Additional Information 4: 3a018db631e662ba3d328203cc490b3a
It worked on windows 7 32 bit just fine so it can't be the fact that I'm on windows 7.
After installing latest haxe toolkit (3.2.0), I have tried to install some libraries to start work on my project. But library manager (haxelib.exe) seems not working properly on my computer. It always crashes and windows showing alert:
The application was unable to start correctly (0xc000000d). Click OK
to close the application
I have also installed toolkit on wife computer and everything working fine. Wife has Windows 7 x64. On my computer is installed Windows 8.1 x64.
In Windows event viewer I found logs:
(Error description)
Faulting application name: haxelib.exe, version: 0.0.0.0, time stamp: 0x5128e2cf
Faulting module name: ntdll.dll, version: 6.3.9600.17936, time stamp: 0x55a68dd1
Exception code: 0xc000000d
Fault offset: 0x0009d4f2
Faulting process id: 0x1710
Faulting application start time: 0x01d0f85f90454af3
Faulting application path: C:\HaxeToolkit\haxe\haxelib.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: d9781581-6452-11e5-82b6-94de80bc77ca
Faulting package full name:
Faulting package-relative application ID:
(Information)
Fault bucket 116025787538, type 5
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: haxelib.exe
P2: 0.0.0.0
P3: 5128e2cf
P4: ntdll.dll
P5: 6.3.9600.17936
P6: 55a68dd1
P7: 0009d4f2
P8: c000000d
P9: 00000000
P10:
Attached files:
C:\Users\stanosky\AppData\Local\Temp\WER95F7.tmp.WERInternalMetadata.xml
C:\Users\stanosky\AppData\Local\Temp\WERA1B0.tmp.appcompat.txt
C:\Users\stanosky\AppData\Local\Temp\WERA1E0.tmp.dmp
C:\Users\stanosky\AppData\Local\Temp\WERA21F.tmp.WERDataCollectionFailure.txt
These files may be available here:
C:\Users\stanosky\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_haxelib.exe_2b43177c7b6b1557ce91e7560961d98719c3f54_0b7bc880_0bf3a5b6
Analysis symbol:
Rechecking for solution: 0
Report Id: d9781581-6452-11e5-82b6-94de80bc77ca
Report Status: 4104
Hashed bucket: f45888bea7f3cfaa0a11620b03ca7f6a
Any ideas what is going wrong with my computer/windows?
It turns out that my computer was infected by rootkit. It injects some bits of code into Windows dll files and that caused malfunction of haxelib.exe. I have removed it and my problem has gone.
When executing a newly built "Hello World" console application in CMD or PowerShell inside ConEmu (frames and tabulates everything), the application will fail with "MyApp has stopped working" after printing "Hello World".
Execution in a regular CMD/PowerShell works fine.
Setup:
Windows 7 Enterprise
Visual Studio 2015
ConEmu 150816
.Net 4.5.2
Problem details/signature:
Problem Event Name: APPCRASH
Application Name: PerforceSSOClient.exe
Application Version: 1.0.0.0
Application Timestamp: 55e5acb4
Fault Module Name: nvd3d9wrap.dll
Fault Module Version: 9.18.13.3182
Fault Module Timestamp: 5280d7e2
Exception Code: c00000fd
Exception Offset: 0000583d
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1030
Additional Information 1: c859
Additional Information 2: c859befd7e6cd7469e4e4ec59e24adda
Additional Information 3: fd58
Additional Information 4: fd581380868e58459acc52bac65d582b
The crash is caused by the nVIDIA driver dll nvd3d9wrap.dll. You use the driver version 331.82. Try to use the latest driver 355.82:
32Bit: http://www.nvidia.com/download/driverResults.aspx/90493/en-us
64Bit: http://www.nvidia.com/download/driverResults.aspx/90494/en-us
I run a Windows application which suddenly crashes in between since last week.
It shows following error:
Description:
Stopped working
The following Windows Event is logged in the Event Viewer:
Problem signature:
Problem Event Name: APPCRASH
Application Name: abc.exe
Application Version: 1.0.0.0
Application Timestamp: 510fbb25
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.18015
Fault Module Timestamp: 50b8479b
Exception Code: e053534f
Exception Offset: 0000000000009e5d
OS Version: 6.1.7601.2.1.0.274.10
Locale ID: 1033
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
The system OS is Windows Server 2008 R2.
downgrade from .net framework 4.7.2 or 4.8 to 4.6.2
I've got an application we use at our company.
All of our Windows XP PCs and Windows 7 PCs use it.
I can run it in the debugger under Visual Studio 2008 and build the Installer that all of the other PCs use to install it with, but I can not get it to run after installing on my PC (the installation shows no errors).
Under Event Viewer > Windows Logs > Application, two (2) events are fired:
The Error thrown when I try to run the installed application:
Faulting application name: Suite.exe, version: 2.2.21.0, time stamp: 0x4d389f32
Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b802
Exception code: 0xc00000fd
Fault offset: 0x00000000000076cf
Faulting process id: 0x1424
Faulting application start time: 0x01cbb8f485a2a9d8
Faulting application path: C:\Program Files\Aaon Coil Products, Inc\ACP Software Suite\Suite.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: c58bd590-24e7-11e0-b398-00248103a942
An Informational message fires up immediately after with Windows Error Reporting:
Fault bucket 28268826, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Suite.exe
P2: 2.2.21.0
P3: 4d389f32
P4: ntdll.dll
P5: 6.1.7600.16559
P6: 4ba9b802
P7: c00000fd
P8: 00000000000076cf
P9:
P10:
Attached files:
C:\Users\cp-jpool\AppData\Local\Temp\WER492A.tmp.WERInternalMetadata.xml
These files may be available here:
C:\Users\cp-jpool\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Suite.exe_e131a0d577e0788f7db9b54fd53b35e27d8860e2_11df4dea
Analysis symbol:
Rechecking for solution: 0
Report Id: c58bd590-24e7-11e0-b398-00248103a942
Report Status: 0
This repeats every time I try to run the application I made with this PC ...on this PC, but no where else.
Could someone give me some idea of what's going on and how to fix it?
Do you get prompted to elevate Visual Studio when you run it?
If so, try running the app elevated.
Basically, isolate what's different between the two:
Can you run it in Visual Studio without debugging? Including when you set it to "Release"?
How about if you build and install it as "Debug" then start it and try to attach to it as it crashes? (You can set the JIT debugger via the registry here: http://msdn.microsoft.com/en-us/library/5hs4b7a6.aspx)
Good luck!
It turned out that my application uses a control that does not run on 64-bit environments.
Apparently, the debugger in VS2008 will not throw an error whenever one of these old style DLLs fails.