Windows 10: HLK Test fails for Windows Server 2016

Discus and support HLK Test fails for Windows Server 2016 in Windows 10 Drivers and Hardware to solve the problem; Hi All, We are running the HLK test on Windows Server 2016. For all the driver's oplock test is getting failed. Some drivers are not changed and the... Discussion in 'Windows 10 Drivers and Hardware' started by Sujay Upasani, Aug 9, 2019.

  1. HLK Test fails for Windows Server 2016


    Hi All,

    We are running the HLK test on Windows Server 2016. For all the driver's oplock test is getting failed. Some drivers are not changed and the test was passed for those drivers previously. But now with the same HLK setup the test is getting failed for those drivers also.

    Below is some information and screenshots.

    Revert in case of query.

    Thanks in the advance.

    Regards,

    Sujay Upasani.

    -----------------------------------------------------------------------------------------------------------

    Below is the Error message:

    Cause : Task "Run oplocks test" is Marked Failed From the LogFile

    Cause : Copying File "C:\hlk\JobsWorkingDir\Tasks\WTTJobRunB2D8636C-17B9-E911-8139-1C1B0D43B186\FileOplocks-NTFS.wtl.trace" Fails

    Cause : Cannot Find Pattern "C:\hlk\JobsWorkingDir\Tasks\WTTJobRunB2D8636C-17B9-E911-8139-1C1B0D43B186\FileOplocks-NTFS.wtl.trace"

    Cause : Error returned from EnableShareAccess to the root of "\WIN-MA572NA52QT\HLKLogs\8-7-2019\3C79C092-4C5D-4346-9009-AF0E731D7FBC\F26A7A5E-1CAB-4D02-9073-FC8B8E9C3285\BD737747-24E3-4E6B-885A-9749CC6B9075\"

    Cause : Task is Marked Failed as it had non-zero Fail Counts in the LogFile

    -----------------------------------------------------------------------------------------------------------


    From the log file:

    2412 6900 2019:8:9 8:53:21:845 Attempting to access \\WIN-MA572NA52QT\TaefBinaries as WIN-MA572NA52QT\HLKShareUser...

    2412 6900 2019:8:9 8:53:21:845 Net use \\WIN-MA572NA52QT\TaefBinaries (attempt 1 of 3)...

    2412 6900 2019:8:9 8:53:21:845 Net use to share \\WIN-MA572NA52QT\TaefBinaries failed with error code: hr = 800704c3

    2412 6900 2019:8:9 8:53:22:857 Net use \\WIN-MA572NA52QT\TaefBinaries (attempt 2 of 3)...

    2412 6900 2019:8:9 8:53:22:857 Net use to share \\WIN-MA572NA52QT\TaefBinaries failed with error code: hr = 800704c3

    2412 6900 2019:8:9 8:53:23:858 Net use \\WIN-MA572NA52QT\TaefBinaries (attempt 3 of 3)...

    2412 6900 2019:8:9 8:53:23:858 Net use to share \\WIN-MA572NA52QT\TaefBinaries failed with error code: hr = 800704c3

    2412 6900 2019:8:9 8:53:24:866 All share connection attempts failed.


    From the log file:2412 6900 2019:8:9 8:53:28:811 Error: 0x800704c3, Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again. CopyFile/Result Task::Start():HLK Test fails for Windows Server 2016 :(null)::CAUSE:Error returned from EnableShareAccess to the root of "\\WIN-MA572NA52QT\TaefBinaries\x64"

    ----------------------------------------------------------------------------------------------------------- HLK Test fails for Windows Server 2016 0d130d3a-38e0-444b-b32c-eaa22fc2ce08?upload=true.png HLK Test fails for Windows Server 2016 ca12fa08-2b51-4b96-9809-15b3025ff381?upload=true.png

    :)
     
    Sujay Upasani, Aug 9, 2019
    #1
  2. EddyRosar Win User

    Windows HLK - Router Testing on Windows 10

    I planned to perform Wireless Router Testing for Windows 10 using the HLK toolkit.

    As per the basic HLK requirement, I brought up the HLK Controller by installing the Controller + Studio in a Windows 2008 Server and have installed Clients from the Controller's share in 4 Windows 10 PCs

    As per this link, Wireless Router Testing Prerequisites,
    there should be configuration jobs and test jobs available for configuring and performing the “Router” Tests. But no jobs or Features were seen on the HLK manager under $\WDK Tests\Networking.

    Later I installed WDK for Windows 10 in the Controller (Windows 2008 Server) hoping to find some jobs/Features being populated under $\WDK Tests\Networking, but still no jobs or Features were listed.

    Being a beginner, I couldn’t assess if any additional package is missing or any configuration change or “Job/Feature imports” to be performed in HLK. Moreover couldn’t find any reference for it in the Documentation too.
     
    EddyRosar, Aug 9, 2019
    #2
  3. Vgnr Plar Win User
    HLK Studio

    Hello,

    Just changed the HLK SUT machine name and all the data is not showing up on HLK Studio anymore.

    The right server is under archived.

    How can I do to get the data back?

    -VP
     
    Vgnr Plar, Aug 9, 2019
    #3
  4. Nitin. Win User

    HLK Test fails for Windows Server 2016

    HLK Test Fail in Bring Up test win10x64 for A2DP profile Driver

    I am running HLK test on win10x64 for Bluetooth Profile Driver(A2DP)

    All Bring up test case :

    Bluetooth-BluetoothDeviceIDProfileVer13_1(Bring Up)

    Bluetooth-BluetoothHidLimitedDiscoverableMode(Bring Up)

    Bluetooth-HidInitiateReconnect1(Bring Up)

    Bluetooth-KeyboardSupportPasskeyAuthentication1(Bring Up)

    Bluetooth-SupportsBluetoothVer21_1(Bring Up)

    failing with error message

    Failed to gather the device address the provided WDKDeviceID:[0x80070490]

    Please help in resolving this issue

    Thanks in advance

    Please find the logs below

    Test Log Report - Complete Report
    Report Summary

    Test Results

    Description Total Pass Fail Warning Blocked Skipped Pass Rate

    4 3 1 0 0 0 75.00%

    TimeStamp Total Pass Fail Warning Blocked Skipped Pass Rate

    12/2/2015 10:24:08.940 AM 1 1 0 0 0 0 100.00%

    12/2/2015 10:24:09.585 AM 1 1 0 0 0 0 100.00%

    12/2/2015 10:30:55.474 AM 1 1 0 0 0 0 100.00%

    12/2/2015 10:31:16.570 AM 1 0 1 0 0 0 0.00%



    Machine, Process, and OS Information

    Machine Name OS Version Build BuildLab BuildDate Platform Language ServicePack Config

    Windows 10 Pro 6.3 10586.00 th2_release 151112-1900 AMD64 English (US) (REDMOND) n/a

    Base Time Process ID Thread ID Process Name

    12/2/2015 10:24:08.124 AM 6948 6992 C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    12/2/2015 10:24:08.372 AM 6948 4740 C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    12/2/2015 10:24:08.374 AM 6948 4644 C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    12/2/2015 10:24:09.244 AM 6676 4124 C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    12/2/2015 10:24:09.360 AM 6676 1340 C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    12/2/2015 10:24:09.360 AM 6676 3972 C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    12/2/2015 10:30:54.683 AM 5140 4256 C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    12/2/2015 10:30:55.135 AM 5140 4248 C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    12/2/2015 10:30:55.139 AM 5140 944 C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    12/2/2015 10:31:13.594 AM 2172 2092 C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    12/2/2015 10:31:16.218 AM 2172 2848 C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    12/2/2015 10:31:16.244 AM 2172 5444 C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe



    Report Details

    Complete Test Log

    Runtime 12/2/2015 10:24:08.124 AM _

    Runtime Index: 2572023962

    Machine: DESKTOP-E9DOM3E

    Process Name: C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    Process ID: 6948

    Thread ID: 6992

    Context _ _

    Context Index: 384048256

    Current: WTTLOG

    Parent: ROOT

    Message 12/2/2015 10:24:08.597 AM Device string in use: $LocalPub:WTTLogPFMode=user($LogFile:file="C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.wtl",writemode=append,encoding=unicode,EnableLvl=WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*)

    Message 12/2/2015 10:24:08.597 AM WTTLogger_CPP_th2_release; Version: 2.7.3479.0

    Computer 12/2/2015 10:24:08.605 AM _

    OS: Windows 10 Pro

    Version: 6.3.10586.00 AMD64

    Language: English (US) (REDMOND)

    Build String: th2_release-151112-1900

    Configuration: n/a

    MetadataRef 12/2/2015 10:24:08.663 AM _

    Runtime 12/2/2015 10:24:08.372 AM _

    Runtime Index: 1068166619

    Machine: DESKTOP-E9DOM3E

    Process Name: C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    Process ID: 6948

    Thread ID: 4740

    Context _ _

    Context Index: 3149459430

    Current: Microsoft::Hardware::Kits:HLK Test fails for Windows Server 2016 :DriverVerifierConfigUtil::Reset

    Parent: WTTLOG

    Start Test 12/2/2015 10:24:09.094 AM Microsoft::Hardware::Kits:HLK Test fails for Windows Server 2016 :DriverVerifierConfigUtil::Reset

    MetadataRef 12/2/2015 10:24:09.094 AM _

    MetadataRef 12/2/2015 10:24:09.094 AM _

    Runtime 12/2/2015 10:24:08.374 AM _

    Runtime Index: 1925313758

    Machine: DESKTOP-E9DOM3E

    Process Name: C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    Process ID: 6948

    Thread ID: 4644

    Message 12/2/2015 10:24:09.097 AM Running program with command line: 'verifier.exe /reset' WexTraceInfo ThreadId=5092 ProcessId=6916 TimeStamp=980593826



    Message 12/2/2015 10:24:09.166 AM Successfully reset DriverVerifier settings on the machine. WexTraceInfo ThreadId=5092 ProcessId=6916 TimeStamp=980721046



    End Test 12/2/2015 10:24:09.166 AM Microsoft::Hardware::Kits:HLK Test fails for Windows Server 2016 :DriverVerifierConfigUtil::Reset

    Result: Pass

    Pass/Fail Result Rollup Counts 12/2/2015 10:24:08.940 AM _

    Total: 1

    Passed: 1

    Failed: 0

    Blocked: 0

    Warned: 0

    Skipped: 0

    Runtime 12/2/2015 10:24:09.244 AM _

    Runtime Index: 1734387767

    Machine: DESKTOP-E9DOM3E

    Process Name: C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    Process ID: 6676

    Thread ID: 4124

    Context _ _

    Context Index: 384048256

    Current: WTTLOG

    Parent: ROOT

    Message 12/2/2015 10:24:09.444 AM Device string in use: $LocalPub:WTTLogPFMode=user($LogFile:file="C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.wtl",writemode=append,encoding=unicode,EnableLvl=WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*)

    Message 12/2/2015 10:24:09.444 AM WTTLogger_CPP_th2_release; Version: 2.7.3479.0

    Computer 12/2/2015 10:24:09.449 AM _

    OS: Windows 10 Pro

    Version: 6.3.10586.00 AMD64

    Language: English (US) (REDMOND)

    Build String: th2_release-151112-1900

    Configuration: n/a

    MetadataRef 12/2/2015 10:24:09.451 AM _

    Runtime 12/2/2015 10:24:09.360 AM _

    Runtime Index: 3720308370

    Machine: DESKTOP-E9DOM3E

    Process Name: C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    Process ID: 6676

    Thread ID: 1340

    Context _ _

    Context Index: 784764012

    Current: Microsoft::Hardware::Kits:HLK Test fails for Windows Server 2016 :DriverVerifierConfigUtil::Configure

    Parent: WTTLOG

    Start Test 12/2/2015 10:24:09.677 AM Microsoft::Hardware::Kits:HLK Test fails for Windows Server 2016 :DriverVerifierConfigUtil::Configure

    MetadataRef 12/2/2015 10:24:09.677 AM _

    MetadataRef 12/2/2015 10:24:09.677 AM _

    Runtime 12/2/2015 10:24:09.360 AM _

    Runtime Index: 149849393

    Machine: DESKTOP-E9DOM3E

    Process Name: C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    Process ID: 6676

    Thread ID: 3972

    Message 12/2/2015 10:24:09.678 AM SUCCEEDED(RuntimeParameters::TryGetValue(DRIVERVERIFIER_SETTINGS_PARAMETER, parameterValue)): 'DriverVerifierSettingsString' is a mandatory parameter WexTraceInfo ThreadId=4172 ProcessId=2420 TimeStamp=982421586

    WexContext Verify



    Message 12/2/2015 10:24:09.679 AM IsTrue(GetEnvironmentVariable(L"COMPUTERNAME", szComputerName, MAX_COMPUTERNAME_LENGTH) != 0): Could not retrieve COMPUTERNAME for the machine. Win32 ErrorCode: 122 WexTraceInfo ThreadId=4172 ProcessId=2420 TimeStamp=982423554

    WexContext Verify



    Message 12/2/2015 10:24:09.680 AM IsTrue((_wcslwr_s(szComputerName, wcslen(szComputerName) + 1) == 0)): Failed to convert COMPUTERNAME '' to lowercase WexTraceInfo ThreadId=4172 ProcessId=2420 TimeStamp=982425193

    WexContext Verify



    Message 12/2/2015 10:24:09.680 AM DriverVerifier parameters:

    Excluded MachinesHLK Test fails for Windows Server 2016 :()

    DVFlags: (0x209BB)

    DVDrivers: (btha2dpsink.sys wdf01000.sys)

    WexTraceInfo ThreadId=4172 ProcessId=2420 TimeStamp=982426419



    Message 12/2/2015 10:24:09.681 AM Setting VerifyHCKExcludeList WexTraceInfo ThreadId=4172 ProcessId=2420 TimeStamp=982427438



    Message 12/2/2015 10:24:09.681 AM Attempting to set registry key 'HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management\VerifyHCKExcludeList' with value '' WexTraceInfo ThreadId=4172 ProcessId=2420 TimeStamp=982428056



    Message 12/2/2015 10:24:09.682 AM Running program with command line: 'verifier.exe /flags 0x209BB /driver btha2dpsink.sys wdf01000.sys' WexTraceInfo ThreadId=4172 ProcessId=2420 TimeStamp=982429609



    Message 12/2/2015 10:24:09.695 AM DV will be enabled on machine '' since it is not included in exempt list: WexTraceInfo ThreadId=4172 ProcessId=2420 TimeStamp=982452898



    Message 12/2/2015 10:24:09.695 AM Attempting to set registry key 'HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriversSuppress' with value '' WexTraceInfo ThreadId=4172 ProcessId=2420 TimeStamp=982454190



    Message 12/2/2015 10:24:09.696 AM Disabled rule persistence behavior is not set. WexTraceInfo ThreadId=4172 ProcessId=2420 TimeStamp=982455930



    Message 12/2/2015 10:24:09.696 AM No rules are disabled for Driver Verifier. WexTraceInfo ThreadId=4172 ProcessId=2420 TimeStamp=982456722



    End Test 12/2/2015 10:24:09.697 AM Microsoft::Hardware::Kits:HLK Test fails for Windows Server 2016 :DriverVerifierConfigUtil::Configure

    Result: Pass

    Pass/Fail Result Rollup Counts 12/2/2015 10:24:09.585 AM _

    Total: 1

    Passed: 1

    Failed: 0

    Blocked: 0

    Warned: 0

    Skipped: 0

    Runtime 12/2/2015 10:30:54.683 AM _

    Runtime Index: 1627071048

    Machine: DESKTOP-E9DOM3E

    Process Name: C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    Process ID: 5140

    Thread ID: 4256

    Context _ _

    Context Index: 384048256

    Current: WTTLOG

    Parent: ROOT

    Message 12/2/2015 10:30:55.009 AM Device string in use: $LocalPub:WTTLogPFMode=user($LogFile:file="C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.wtl",writemode=append,encoding=unicode,EnableLvl=WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*)

    Message 12/2/2015 10:30:55.009 AM WTTLogger_CPP_th2_release; Version: 2.7.3479.0

    Computer 12/2/2015 10:30:55.031 AM _

    OS: Windows 10 Pro

    Version: 6.3.10586.00 AMD64

    Language: English (US) (REDMOND)

    Build String: th2_release-151112-1900

    Configuration: n/a

    MetadataRef 12/2/2015 10:30:55.037 AM _

    Runtime 12/2/2015 10:30:55.135 AM _

    Runtime Index: 1432678918

    Machine: DESKTOP-E9DOM3E

    Process Name: C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    Process ID: 5140

    Thread ID: 4248

    Context _ _

    Context Index: 553147124

    Current: Microsoft::Hardware::Kits:HLK Test fails for Windows Server 2016 :DriverVerifierConfigUtil:HLK Test fails for Windows Server 2016 :pass

    Parent: WTTLOG

    Start Test 12/2/2015 10:30:55.906 AM Microsoft::Hardware::Kits:HLK Test fails for Windows Server 2016 :DriverVerifierConfigUtil:HLK Test fails for Windows Server 2016 :pass

    MetadataRef 12/2/2015 10:30:55.906 AM _

    MetadataRef 12/2/2015 10:30:55.907 AM _

    Runtime 12/2/2015 10:30:55.139 AM _

    Runtime Index: 780298494

    Machine: DESKTOP-E9DOM3E

    Process Name: C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    Process ID: 5140

    Thread ID: 944

    Message 12/2/2015 10:30:55.913 AM Disabled rule persistence behavior is not set. WexTraceInfo ThreadId=4208 ProcessId=4212 TimeStamp=683163780



    Message 12/2/2015 10:30:55.914 AM No rules are disabled for Driver Verifier. WexTraceInfo ThreadId=4208 ProcessId=4212 TimeStamp=683166956



    Message 12/2/2015 10:30:55.916 AM No operation is needed. Passed trivially. WexTraceInfo ThreadId=4208 ProcessId=4212 TimeStamp=683169641



    End Test 12/2/2015 10:30:55.915 AM Microsoft::Hardware::Kits:HLK Test fails for Windows Server 2016 :DriverVerifierConfigUtil:HLK Test fails for Windows Server 2016 :pass

    Result: Pass

    Pass/Fail Result Rollup Counts 12/2/2015 10:30:55.474 AM _

    Total: 1

    Passed: 1

    Failed: 0

    Blocked: 0

    Warned: 0

    Skipped: 0

    Runtime 12/2/2015 10:31:13.594 AM _

    Runtime Index: 1982960823

    Machine: DESKTOP-E9DOM3E

    Process Name: C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    Process ID: 2172

    Thread ID: 2092

    Context _ _

    Context Index: 384048256

    Current: WTTLOG

    Parent: ROOT

    Message 12/2/2015 10:31:13.882 AM Device string in use: $LocalPub:WTTLogPFMode=user($LogFile:file="C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.wtl",writemode=append,encoding=unicode,EnableLvl=WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*)

    Message 12/2/2015 10:31:13.882 AM WTTLogger_CPP_th2_release; Version: 2.7.3479.0

    Computer 12/2/2015 10:31:13.886 AM _

    OS: Windows 10 Pro

    Version: 6.3.10586.00 AMD64

    Language: English (US) (REDMOND)

    Build String: th2_release-151112-1900

    Configuration: n/a

    MetadataRef 12/2/2015 10:31:13.889 AM _

    Runtime 12/2/2015 10:31:16.218 AM _

    Runtime Index: 1050776918

    Machine: DESKTOP-E9DOM3E

    Process Name: C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    Process ID: 2172

    Thread ID: 2848

    Message 12/2/2015 10:31:19.131 AM SUCCEEDED(RadioControllerTestClassInit()) WexTraceInfo ThreadId=2432 ProcessId=5212 TimeStamp=722184685

    WexContext Verify



    Message 12/2/2015 10:31:19.134 AM IsTrue(fResult != FALSE): Finding a Radio Controller WexTraceInfo ThreadId=2432 ProcessId=5212 TimeStamp=722191876

    WexContext Verify



    Error 12/2/2015 10:31:19.151 AM Failed to gather the device address the provided WDKDeviceID: [0x80070490] WexTraceInfo ThreadId=2432 ProcessId=5212 TimeStamp=722197845



    File: Line: -1

    Error Type:

    Error Code: 0x0

    Error Text: Error 0x00000000

    Runtime 12/2/2015 10:31:16.244 AM _

    Runtime Index: 2623372152

    Machine: DESKTOP-E9DOM3E

    Process Name: C:\hlk\JobsWorkingDir\Tasks\WTTJobRun488B0A38-B898-E511-B704-B083FE6BDD0F\Te.exe

    Process ID: 2172

    Thread ID: 5444

    Error 12/2/2015 10:31:19.181 AM Setup fixture 'BluetoothHLK:HLK Test fails for Windows Server 2016 :pairedDeviceValidator::Test_Init' for the scope 'BluetoothHLK:HLK Test fails for Windows Server 2016 :pairedDeviceValidator' failed. WexTraceInfo ThreadId=5444 ProcessId=2172 TimeStamp=722228312

    WexContext TAEF



    File: Line: -1

    Error Type:

    Error Code: 0x0

    Error Text: Error 0x00000000

    Context _ _

    Context Index: 289888607

    Current: BluetoothHLK:HLK Test fails for Windows Server 2016 :pairedDeviceValidator::Test_BluetoothDeviceIDProfileVer13_1

    Parent: WTTLOG

    Start Test 12/2/2015 10:31:19.184 AM BluetoothHLK:HLK Test fails for Windows Server 2016 :pairedDeviceValidator::Test_BluetoothDeviceIDProfileVer13_1

    End Test 12/2/2015 10:31:19.188 AM BluetoothHLK:HLK Test fails for Windows Server 2016 :pairedDeviceValidator::Test_BluetoothDeviceIDProfileVer13_1

    Result: Fail

    Pass/Fail Result Rollup Counts 12/2/2015 10:31:16.570 AM _

    Total: 1

    Passed: 0

    Failed: 1

    Blocked: 0

    Warned: 0

    Skipped: 0
     
    Nitin., Aug 9, 2019
    #4
Thema:

HLK Test fails for Windows Server 2016

Loading...
  1. HLK Test fails for Windows Server 2016 - Similar Threads - HLK Test fails

  2. Windows server 2016 failed to add features and roles

    in Windows 10 Installation and Upgrade
    Windows server 2016 failed to add features and roles: Hello, so I'm getting a failed to install features and roles because the reference assembly could not be found, 0x80073701, I was wondering if anybody has come across this issue, I need to set up a vpn, but it fails to install remote access...
  3. WIndow server 2016 error

    in Windows 10 BSOD Crashes and Debugging
    WIndow server 2016 error: Dear Microsoft Team, We finded the problem on our server, the error is: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID...
  4. Windows Server 2016 BSODs

    in Windows 10 BSOD Crashes and Debugging
    Windows Server 2016 BSODs: I'm having many BSODs since the start of the year in my home Server. Many of them are MEMORY related and the last one is KERNEL related. Any help will be appreciated Minidumps: https://1drv.ms/f/s!AmdF71SjCBatjxjeU85M7vqgovju Thanks! (I didnt find the Server 2016...
  5. Windows Server 2016 Updates

    in Windows 10 Installation and Upgrade
    Windows Server 2016 Updates: Hi, I am having windows server 2016 (version 1607) & OS build (14393.187) - KB 3189866 dated 13th Sep 2016. I have to update it to KB 4487026 dated 12th Feb 2019 OS Build (14393.2791). Is it required to install all the previous windows updates from 13th sep 2016 till 12th...
  6. Windows Server 2016 and Remote printers

    in Windows 10 Drivers and Hardware
    Windows Server 2016 and Remote printers: I'm trying to get remote printers to work over shared remote desktop sessions on Windows Server 2016. They were working before, now they are not, and they continue to reset themselves after I set them up. Before the remote laptops connecting were Windows 7 Pro machines, now...
  7. Windows 10/ Server 2016

    in Windows 10 Customization
    Windows 10/ Server 2016: Win10/Server 2012, 2016 are so freaking painful to work with. I am not happy with MS at all! https://answers.microsoft.com/en-us/windows/forum/windows_10-start-win_desk/windows-10-server-2016/d311abdc-d1fb-4f39-b9b7-8943624e0dac
  8. Help setting up Hyper-V to test Windows Server 2016

    in Windows 10 Virtualization
    Help setting up Hyper-V to test Windows Server 2016: Hi there @ I can't answer your specific questions on HYPER-V but I know all about "Breaking Netflix" - even the Dog starts barking madly. !!!! I don't think there's any major problem to having a server on a home LAN (I have 2 Linux servers on a LAN plus a whole slew of...
  9. Final public test builds of Windows Server 2016 and System Center 2016

    in Windows 10 News
    Final public test builds of Windows Server 2016 and System Center 2016: Microsoft is making available today to testers its final public technical previews of Windows Server 2016 and System Center 2016. Technical Preview 5 (TP5) of both products are available for download on April 27. Both of these previews are considered "feature-complete" at...
  10. SharePoint Server 2016 and Project Server 2016 RC available

    in Windows 10 News
    SharePoint Server 2016 and Project Server 2016 RC available: Building on our announcement of SharePoint Server 2016 Beta 2 in November, we’re pleased to announce the availability of SharePoint Server 2016 Release Candidate (RC). SharePoint Server 2016 RC is mostly feature complete and represents an important milestone for customers and...