none
UpdateDriverForPlugAndPlayDevices fails with 0xe0000203 since Windows 10 1809 RRS feed

  • Question

  • Hi,

    I have a signed 64-bit non-PnP KMDF driver, build with WDK 7600.16385.1, that runs under Windows 7..10. For the driver installation, I use a console application (devinst.exe), down stripped from the MS devcon sample code.

    The driver installation works without any problem till Windows 10 1803.

    Since Windows 10 1809, the driver installation fails when devinst.exe calls UpdateDriverForPlugAndPlayDevicesW(). GetLastError return the error code 0xe0000203 ERROR_NO_DRIVER_SELECTED.

    The devinst.exe call looks like:

    devinst.exe  -i C:\MEN\ErtcSmb\Drivers\AMD64\13bb0370_smbpci.inf root\MEN_SMBPCI_FCH_SMBUS

    with is functional the same as the devon call: 

    devcon.exe  install C:\MEN\ErtcSmb\Drivers\AMD64\13bb0370_smbpci.inf root\MEN_SMBPCI_FCH_SMBUS

    devcon.exe from the WDK for Windows 10, version 1809, produces the same error code as devinst.exe at the UpdateDriverForPlugAndPlayDevicesW() function call.

    When I install the driver under 1803 and upgrade then to 1809, the driver works fine. So the problem is "only" the installation under 1809.

    I compared the setupapi.dev.txt log file from 1803 with 1809. The logs are identical until:

    [1803]

    sto: {Setup Import Driver Package - exit (0x00000000)} 16:37:05.751 dvi: Searching for hardware ID(s): dvi: root\men_smbpci_fch_smbus dvi: Class GUID of device remains: {3d9f85af-e5e4-4b14-aab9-c01473275b9b}. dvi: {Plug and Play Service: Device Install for ROOT\MEN\13BB0370_SMBPCI+INF&ROOT-MEN_SMBPCI_FCH_SMBUS} 
    ...

    [1809]

         sto:      {Setup Import Driver Package - exit (0x00000000)} 14:17:32.202
         dvi:      Searching for hardware ID(s):
         dvi:           root\men_smbpci_fch_smbus
         ndv: {Update Device Driver - exit(e0000203)}
    !!!  ndv: Failed to install device instance 'ROOT\MEN\13BB0370_SMBPCI+INF&ROOT-MEN_SMBPCI_FCH_SMBUS'. Error = 0xe0000203
         dvi: {DIF_DESTROYPRIVATEDATA} 14:17:32.258
         dvi:      Class installer: Enter 14:17:32.266
         dvi:      Class installer: Exit
         dvi:      Default installer: Enter 14:17:32.280
         dvi:      Default installer: Exit
         dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 14:17:32.294
    <<<  Section end 2019/01/11 14:17:32.300
    <<<  [Exit status: FAILURE(0xe0000203)]
    

    Have you any idea what can cause the error code 0xe0000203 ERROR_NO_DRIVER_SELECTED from UpdateDriverForPlugAndPlayDevices until Windows 10 1809?

    Regards,

    Dieter



    Dieter

    Friday, January 11, 2019 3:16 PM

Answers

  • Hi,

    Thank you for noticing this issue, this is a bug in a utility routine that occurs when the first character of an install section is a *.  This will be fixed in the upcoming release of Windows, but you can work around the issue by changing the section names so the first character is not a *.

    • Proposed as answer by Tim Roberts Saturday, January 19, 2019 11:25 PM
    • Marked as answer by Dieter Pfeuffer Monday, January 21, 2019 8:01 AM
    Friday, January 18, 2019 11:25 PM

All replies

  • Hi,

    I didn't see any obvious changes to this codepath and I couldn't reproduce this on my end.  Could you share the INF you're trying to install?  I should be able to reproduce this issue

    Thursday, January 17, 2019 12:33 AM
  • @Dieter, have you deleted your previous post in other forum (VC++?)

    If only my memory serves, the log posted there was longer and contained some sort of signature problem before  Error = 0xe0000203 ?

    -- pa

    Thursday, January 17, 2019 2:15 AM
  • Hello Pavel,

    I posted the issue only in this forum.


    Dieter


    Thursday, January 17, 2019 7:02 AM
  • Hello Zac,

    meanwhile, I discovered that this problems affects also other drivers from our company. Therefore, I add the mt.inf of our MT test driver, that is much smaller than the 13bb0370_smbpci.inf:

    ; identifier: MEN_INF_MDIS5 APB-NO-OVERWRITE
    ;
    ; MDIS5 AMD64 INF file for mt
    ;
    ;    Author: Generated by mdiswiz V2.01.023 from mt.xml
    ;      Date: 2013-10-30 (pkg2inf.cpp rev. 2.6)
    ;
    ;    > > > DO NOT EDIT THIS FILE! < < <
    ;
    ; (c) Copyright 2013 by MEN Mikro Elektronik GmbH, Nuremberg, Germany
    ;
    
    [Version]
    Signature="$Windows NT$"
    Class="MDIS5 devices"
    ClassGUID={C82FF067-7D62-4801-B5FC-D01C6F2E7696}
    Provider=%MEN%
    DriverPackageDisplayName="MDIS5 driver package for MDIS Test driver MT"
    DriverVer=10/30/2013,2.12.1.4
    CatalogFile=mt.cat
    
    [SourceDisksNames]
    1="MEN mt - MDIS5 driver package for MDIS Test driver MT"
    2="MEN 13MD05-70 - MDIS5 System Package for Windows"
    
    [SourceDisksFiles]
    WdfCoInstaller01009.dll=2
    mt.xml=1
    men_mt.sys=1
    men_mt_nohw.sys=1
    
    [DestinationDirs]
    DefaultDestDir=12   ; Drivers directory
    Xml_Files=17,MEN    ; INF file directory\MEN (for XML)
    WdfCoInst_Files=11  ; System directory
    
    ;;
    ;; Class installation section
    ;;
    [ClassInstall32.NTamd64]
    AddReg=AddClassReg
    
    [AddClassReg]
    HKR,,,,"MDIS5 devices"
    HKR,,Icon,,100
    HKR,,Installer32,,"men_mdis_clinst.dll,MdisClassInstaller"
    
    ;;
    ;; Device list
    ;;
    [Manufacturer]
    %MEN%=MEN,NTamd64
    [MEN.NTamd64]
    "MT - MT Test Device (default lock mode)"=*MT*, MMOD&NO_AUTOID
    "MT_NOHW - MT Test Device (default lock mode, without any hardware access)"=*MT_NOHW*, MMOD&NO_AUTOID
    ; The following entry ist required for manual installation without HW (Carrier, M-Module)
    "MT_NOHW - MT Test Device (default lock mode, without any hardware access)"=*MT_NOHW*, root\mt
    
    [ControlFlags]
    ; ExcludeFromSelect must not be set to '*',
    ;  otherwise no manual installation without HW (Carrier, M-Module) is possible! 
    ExcludeFromSelect=MMOD&NO_AUTOID
    
    ;;
    ;; *MT* section
    ;;
    [*MT*]
    CopyFiles=Xml_Files,*MT*_Files
    
    [*MT*_Files]
    men_mt.sys
    
    [*MT*.Services]
    AddService=men_mt,0x00000002,*MT*_Service_Inst,EventLog_Inst
    
    [*MT*_Service_Inst]
    ServiceType=0x1
    StartType=0x3
    ErrorControl=0x1
    ServiceBinary=%12%\men_mt.sys
    
    [*MT*.HW]
    AddReg=*MT*_HW_AddReg
    
    [*MT*_HW_AddReg]
    HKR,,PackDescFile,%REG_SZ%,"mt.xml"
    HKR,,ModelName,%REG_SZ%,"MT"
    HKR,Descriptor,ID_CHECK,%REG_DWORD%,0
    
    ;; WDF specifics
    [*MT*.CoInstallers]
    AddReg=WdfCoInst_AddReg
    CopyFiles=WdfCoInst_Files
    
    [*MT*.Wdf]
    KmdfService=men_mt, WdfLib
    
    ;;
    ;; *MT_NOHW* section
    ;;
    [*MT_NOHW*]
    CopyFiles=Xml_Files,*MT_NOHW*_Files
    
    [*MT_NOHW*_Files]
    men_mt_nohw.sys
    
    [*MT_NOHW*.Services]
    AddService=men_mt_nohw,0x00000002,*MT_NOHW*_Service_Inst,EventLog_Inst
    
    [*MT_NOHW*_Service_Inst]
    ServiceType=0x1
    StartType=0x3
    ErrorControl=0x1
    ServiceBinary=%12%\men_mt_nohw.sys
    
    [*MT_NOHW*.HW]
    AddReg=*MT_NOHW*_HW_AddReg
    
    [*MT_NOHW*_HW_AddReg]
    HKR,,PackDescFile,%REG_SZ%,"mt.xml"
    HKR,,ModelName,%REG_SZ%,"MT_NOHW"
    HKR,Descriptor,ID_CHECK,%REG_DWORD%,0
    
    ;; WDF specifics
    [*MT_NOHW*.CoInstallers]
    AddReg=WdfCoInst_AddReg
    CopyFiles=WdfCoInst_Files
    
    [*MT_NOHW*.Wdf]
    KmdfService=men_mt_nohw, WdfLib
    
    ;;
    ;; Common section
    ;;
    [Xml_Files]
    mt.xml
    
    ;; Event logging
    [EventLog_Inst]
    AddReg=EventLog_AddReg
    
    [EventLog_AddReg]
    HKR,,EventMessageFile,%REG_EXPAND_SZ%,"%%SystemRoot%%\System32\IoLogMsg.dll;%%SystemRoot%%\System32\men_evlg.dll"
    HKR,,TypesSupported,%REG_DWORD%,7
    
    ;; WDF specifics
    [WdfCoInst_AddReg]
    HKR,,CoInstallers32,0x00010000, "WdfCoInstaller01009.dll,WdfCoInstaller"
    [WdfCoInst_Files]
    WdfCoInstaller01009.dll
    
    [WdfLib]
    KmdfLibraryVersion=1.9
    
    ;;
    ;; String section
    ;;
    [Strings]
    REG_DWORD=0x00010001
    REG_SZ=0x00000000
    REG_EXPAND_SZ=0x00020000
    REG_BINARY=0x00000001
    COPYFLG=0x00000060
    MEN="MEN Mikro Elektronik"

    Here is the complete log message from setupapi.dev.log:

    >>>  [Device Install (UpdateDriverForPlugAndPlayDevices) - root\mt]
    >>>  Section start 2019/01/16 13:52:34.991
          cmd: "C:\MEN\ErtcSmb_Copy\Drivers\AMD64\devinst.exe" -i C:\MEN\MT\mt.inf root\mt
         ndv: INF path: C:\MEN\MT\mt.inf
         ndv: Install flags: 0x00000005
         ndv: {Update Device Driver - ROOT\MEN\MT+INF&ROOT-MT}
         ndv:      Search options: 0x00000080
         ndv:      Searching single INF 'C:\MEN\MT\mt.inf'
         dvi:      {Build Driver List} 13:52:35.039
         dvi:           Searching for hardware ID(s):
         dvi:                root\mt
         sig:           {_VERIFY_FILE_SIGNATURE} 13:52:35.063
         sig:                Key      = mt.inf
         sig:                FilePath = c:\men\mt\mt.inf
         sig:                Catalog  = c:\men\mt\mt.cat
    !    sig:                Verifying file against specific (valid) catalog failed.
         sig:           {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 13:52:35.129
         sig:           {_VERIFY_FILE_SIGNATURE} 13:52:35.139
         sig:                Key      = mt.inf
         sig:                FilePath = c:\men\mt\mt.inf
         sig:                Catalog  = c:\men\mt\mt.cat
         sig:                Success: File is signed in Authenticode(tm) catalog.
         sig:           {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 13:52:35.189
         dvi:           Created Driver Node:
         dvi:                HardwareID   - root\mt
         dvi:                InfName      - c:\men\mt\mt.inf
         dvi:                DevDesc      - MT_NOHW - MT Test Device (default lock mode, without any hardware access)
         dvi:                Section      - *MT_NOHW*
         dvi:                Rank         - 0x00ff0000
         dvi:                Signer Score - Authenticode
         dvi:                DrvDate      - 10/30/2013
         dvi:                Version      - 2.12.1.4
         dvi:      {Build Driver List - exit(0x00000000)} 13:52:35.251
         dvi:      {DIF_SELECTBESTCOMPATDRV} 13:52:35.257
         dvi:           Using exported function 'MdisClassInstaller' in module 'C:\WINDOWS\system32\men_mdis_clinst.dll'.
         dvi:           Class installer == men_mdis_clinst.dll,MdisClassInstaller
         dvi:           Class installer: Enter 13:52:35.277
         dvi:           Class installer: Exit
         dvi:           Default installer: Enter 13:52:35.289
         dvi:                {Select Best Driver}
         dvi:                     Class GUID of device remains: {c82ff067-7d62-4801-b5fc-d01c6f2e7696}.
         dvi:                     Selected Driver:
         dvi:                          Description - MT_NOHW - MT Test Device (default lock mode, without any hardware access)
         dvi:                          InfFile     - c:\men\mt\mt.inf
         dvi:                          Section     - *MT_NOHW*
         dvi:                {Select Best Driver - exit(0x00000000)}
         dvi:           Default installer: Exit
         dvi:      {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 13:52:35.345
         ndv:      Force Installing Driver:
         ndv:           Inf Name       - mt.inf
         ndv:           Driver Date    - 10/30/2013
         ndv:           Driver Version - 2.12.1.4
         sto:      {Setup Import Driver Package: c:\men\mt\mt.inf} 13:52:35.391
         inf:           Provider: MEN Mikro Elektronik
         inf:           Class GUID: {C82FF067-7D62-4801-B5FC-D01C6F2E7696}
         inf:           Driver Version: 10/30/2013,2.12.1.4
         inf:           Catalog File: mt.cat
         sto:           {Copy Driver Package: c:\men\mt\mt.inf} 13:52:35.439
         sto:                Driver Package = c:\men\mt\mt.inf
         sto:                Flags          = 0x00000007
         sto:                Destination    = C:\Users\men\AppData\Local\Temp\{5aecad2d-d78b-2d4b-a337-936cdb5f1808}
         sto:                Copying driver package files to 'C:\Users\men\AppData\Local\Temp\{5aecad2d-d78b-2d4b-a337-936cdb5f1808}'.
         flq:                Copying 'c:\men\mt\men_mt.sys' to 'C:\Users\men\AppData\Local\Temp\{5aecad2d-d78b-2d4b-a337-936cdb5f1808}\men_mt.sys'.
         flq:                Copying 'c:\men\mt\men_mt_nohw.sys' to 'C:\Users\men\AppData\Local\Temp\{5aecad2d-d78b-2d4b-a337-936cdb5f1808}\men_mt_nohw.sys'.
         flq:                Copying 'c:\men\mt\mt.cat' to 'C:\Users\men\AppData\Local\Temp\{5aecad2d-d78b-2d4b-a337-936cdb5f1808}\mt.cat'.
         flq:                Copying 'c:\men\mt\mt.inf' to 'C:\Users\men\AppData\Local\Temp\{5aecad2d-d78b-2d4b-a337-936cdb5f1808}\mt.inf'.
         flq:                Copying 'c:\men\mt\WdfCoInstaller01009.dll' to 'C:\Users\men\AppData\Local\Temp\{5aecad2d-d78b-2d4b-a337-936cdb5f1808}\WdfCoInstaller01009.dll'.
         flq:                Copying 'c:\men\mt\mt.xml' to 'C:\Users\men\AppData\Local\Temp\{5aecad2d-d78b-2d4b-a337-936cdb5f1808}\mt.xml'.
         sto:           {Copy Driver Package: exit(0x00000000)} 13:52:35.543
         pol:           {Driver package policy check} 13:52:35.561
         pol:           {Driver package policy check - exit(0x00000000)} 13:52:35.563
         sto:           {Stage Driver Package: C:\Users\men\AppData\Local\Temp\{5aecad2d-d78b-2d4b-a337-936cdb5f1808}\mt.inf} 13:52:35.565
         inf:                {Query Configurability: C:\Users\men\AppData\Local\Temp\{5aecad2d-d78b-2d4b-a337-936cdb5f1808}\mt.inf} 13:52:35.571
    !    inf:                     Found legacy AddReg operation defining class installers (Installer32). Code = 1307
    !    inf:                     Driver package 'mt.inf' is NOT configurable.
         inf:                {Query Configurability: exit(0x00000000)} 13:52:35.578
         flq:                Copying 'C:\Users\men\AppData\Local\Temp\{5aecad2d-d78b-2d4b-a337-936cdb5f1808}\men_mt.sys' to 'C:\WINDOWS\System32\DriverStore\Temp\{fa25864f-de4b-134c-b412-a46e1e466bad}\men_mt.sys'.
         flq:                Copying 'C:\Users\men\AppData\Local\Temp\{5aecad2d-d78b-2d4b-a337-936cdb5f1808}\men_mt_nohw.sys' to 'C:\WINDOWS\System32\DriverStore\Temp\{fa25864f-de4b-134c-b412-a46e1e466bad}\men_mt_nohw.sys'.
         flq:                Copying 'C:\Users\men\AppData\Local\Temp\{5aecad2d-d78b-2d4b-a337-936cdb5f1808}\mt.cat' to 'C:\WINDOWS\System32\DriverStore\Temp\{fa25864f-de4b-134c-b412-a46e1e466bad}\mt.cat'.
         flq:                Copying 'C:\Users\men\AppData\Local\Temp\{5aecad2d-d78b-2d4b-a337-936cdb5f1808}\mt.inf' to 'C:\WINDOWS\System32\DriverStore\Temp\{fa25864f-de4b-134c-b412-a46e1e466bad}\mt.inf'.
         flq:                Copying 'C:\Users\men\AppData\Local\Temp\{5aecad2d-d78b-2d4b-a337-936cdb5f1808}\WdfCoInstaller01009.dll' to 'C:\WINDOWS\System32\DriverStore\Temp\{fa25864f-de4b-134c-b412-a46e1e466bad}\WdfCoInstaller01009.dll'.
         flq:                Copying 'C:\Users\men\AppData\Local\Temp\{5aecad2d-d78b-2d4b-a337-936cdb5f1808}\mt.xml' to 'C:\WINDOWS\System32\DriverStore\Temp\{fa25864f-de4b-134c-b412-a46e1e466bad}\mt.xml'.
         sto:                {DRIVERSTORE IMPORT VALIDATE} 13:52:35.659
         sig:                     {_VERIFY_FILE_SIGNATURE} 13:52:35.685
         sig:                          Key      = mt.inf
         sig:                          FilePath = C:\WINDOWS\System32\DriverStore\Temp\{fa25864f-de4b-134c-b412-a46e1e466bad}\mt.inf
         sig:                          Catalog  = C:\WINDOWS\System32\DriverStore\Temp\{fa25864f-de4b-134c-b412-a46e1e466bad}\mt.cat
    !    sig:                          Verifying file against specific (valid) catalog failed.
         sig:                     {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 13:52:35.729
         sig:                     {_VERIFY_FILE_SIGNATURE} 13:52:35.732
         sig:                          Key      = mt.inf
         sig:                          FilePath = C:\WINDOWS\System32\DriverStore\Temp\{fa25864f-de4b-134c-b412-a46e1e466bad}\mt.inf
         sig:                          Catalog  = C:\WINDOWS\System32\DriverStore\Temp\{fa25864f-de4b-134c-b412-a46e1e466bad}\mt.cat
         sig:                          Success: File is signed in Authenticode(tm) catalog.
         sig:                     {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 13:52:35.755
         sto:                {DRIVERSTORE IMPORT VALIDATE: exit(0x00000000)} 13:52:35.771
         sig:                Signer Score  = 0x0F000000 (Authenticode)
         sig:                Signer Name   = MEN Mikro Elektronik GmbH
         sto:                {DRIVERSTORE IMPORT BEGIN} 13:52:35.777
         sto:                {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 13:52:35.779
         cpy:                {Copy Directory: C:\WINDOWS\System32\DriverStore\Temp\{fa25864f-de4b-134c-b412-a46e1e466bad}} 13:52:35.781
         cpy:                     Target Path = C:\WINDOWS\System32\DriverStore\FileRepository\mt.inf_amd64_6862f33e8ef4b999
         cpy:                {Copy Directory: exit(0x00000000)} 13:52:35.789
         idb:                {Register Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\mt.inf_amd64_6862f33e8ef4b999\mt.inf} 13:52:35.791
         idb:                     Created driver package object 'mt.inf_amd64_6862f33e8ef4b999' in DRIVERS database node.
         idb:                     Created driver INF file object 'oem4.inf' in DRIVERS database node.
         idb:                     Registered driver package 'mt.inf_amd64_6862f33e8ef4b999' with 'oem4.inf'.
         idb:                {Register Driver Package: exit(0x00000000)} 13:52:35.797
         idb:                {Publish Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\mt.inf_amd64_6862f33e8ef4b999\mt.inf} 13:52:35.799
         idb:                     Activating driver package 'mt.inf_amd64_6862f33e8ef4b999'.
         cpy:                     Published 'mt.inf_amd64_6862f33e8ef4b999\mt.inf' to 'oem4.inf'.
    !    idb:                     Driver INF match for 'oem4.inf' already exists under 'MMOD&NO_AUTOID'.
         idb:                     Indexed 4 device IDs for 'mt.inf_amd64_6862f33e8ef4b999'.
         sto:                     Flushed driver database node 'DRIVERS'. Time = 0 ms
         sto:                     Flushed driver database node 'SYSTEM'. Time = 16 ms
         idb:                {Publish Driver Package: exit(0x00000000)} 13:52:35.823
         sto:                {DRIVERSTORE IMPORT END} 13:52:35.828
         dvi:                     Flushed all driver package files to disk. Time = 16 ms
         sig:                     Installed catalog 'mt.cat' as 'oem4.cat'.
         sto:                {DRIVERSTORE IMPORT END: exit(0x00000000)} 13:52:35.851
         sto:           {Stage Driver Package: exit(0x00000000)} 13:52:35.853
         sto:      {Setup Import Driver Package - exit (0x00000000)} 13:52:35.871
         dvi:      Searching for hardware ID(s):
         dvi:           root\mt
         ndv: {Update Device Driver - exit(e0000203)}
    !!!  ndv: Failed to install device instance 'ROOT\MEN\MT+INF&ROOT-MT'. Error = 0xe0000203
         dvi: {DIF_DESTROYPRIVATEDATA} 13:52:35.907
         dvi:      Class installer: Enter 13:52:35.913
         dvi:      Class installer: Exit
         dvi:      Default installer: Enter 13:52:35.925
         dvi:      Default installer: Exit
         dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 13:52:35.935
    <<<  Section end 2019/01/16 13:52:35.945
    <<<  [Exit status: FAILURE(0xe0000203)]

    Thanks for your support!


    Dieter


    Thursday, January 17, 2019 7:29 AM
  • !    sig:                Verifying file against specific (valid) catalog failed.

    This is bad. Should not occur.

    Does the other INF file contain weird characters (&) in the HW ID too?

    -- pa

    Thursday, January 17, 2019 8:08 PM
  • >> !    sig:                Verifying file against specific (valid) catalog failed.
    >This is bad. Should not occur.

    I think it doesn't matter, because:
    1. I get the same warning under Win10 1803 where the driver can be installed without problems
    2. Some other working drivers from different vendors report this warning in 
    setupapi.dev.log
    3. Excerpt from a message in the OSR community: "That's ignorable. You will get that until your package is signed by WHQL.". See Driver Signing Issue with Windows 7 64-Bit Install
    4. Microsoft says "These are just warnings to indicate that the cat file has not been verified yet." See Troubleshooting Driver Signing Installation

    >Does the other INF file contain weird characters (&) in the HW ID too?

    We have the "&" in nearly all our HW IDs in INF files since ages.
    For the installation of the MT driver I use the "
    root\mt" HW ID.
    I removed for testing all HW IDs with "&" but got the same error. 


    Dieter

    Friday, January 18, 2019 7:06 AM
  • Hi,

    Thank you for noticing this issue, this is a bug in a utility routine that occurs when the first character of an install section is a *.  This will be fixed in the upcoming release of Windows, but you can work around the issue by changing the section names so the first character is not a *.

    • Proposed as answer by Tim Roberts Saturday, January 19, 2019 11:25 PM
    • Marked as answer by Dieter Pfeuffer Monday, January 21, 2019 8:01 AM
    Friday, January 18, 2019 11:25 PM
  • Hi Zac,

    thanks for your answer, you solved my problem!
    I replaced the '*' character with '+' then the driver installation succeeded.

    Unfortunately, we are using the *<name>* layout for better readability in nearly all our INFs. About fifty driver packages are affected by this problem. So I'm lucking forward, that the bug in the routine will be fixed in the next Windows release.

    Thanks again for your support! 


    Dieter

    Monday, January 21, 2019 8:12 AM