Windows10 Driver Problem

MattMatt Posts: 5New Member
The following driver file is invalid and won't work on Windows 10 as is.

File:
Win10_32_20160307\Win10_32\20160307\Step4-DummyDriver(Manual)\UP_DDriver\UP_DDriver.inf

The solution is to open it in notepad and remove the substitute character at the end of the file. This invalid character is present in both the 32 and 64 bit Windows 10 1.1 driver downloads.

The driver applies to the following device hardware IDs:
ACPI\VEN_8086&DEV_2288
ACPI\VEN_8086&DEV_2289
ACPI\VEN_HAD0&DEV_22A8


Just throwing this out there in case anyone else runs into it.

Comments

  • Jimmy MotJimmy Mot Posts: 13New Member
    that is strange

    i just installed it without problems

    i followed the instructions in the file

    but it still shows a unknown driver

    apparently no one knows what this is

    i refer to another of my posts here on this forum
  • MattMatt Posts: 5New Member
    If the device you're looking at is anything like the one I ran into, there appears to not be a Windows driver. I rolled it into the inf file I referenced above, since I had to edit and resign it anyway...

    All this achieves is removing the yellow hardware bang from device manager.

    My UP_DDriver.inf file, now reads:


    [Version]
    Signature="$WINDOWS NT$"
    Class=System
    Provider=%String0%
    CatalogFile=UP_DDriver.cat
    DriverVer=01/14/2016,6.0.5736.1

    [Manufacturer]
    %String1%=AAEON_SYS,NTAMD64

    [AAEON_SYS]
    %String2%=NO_DRV,ACPI\VEN_8086&DEV_2288
    %String3%=NO_DRV,ACPI\VEN_8086&DEV_2289
    %String4%=NO_DRV,ACPI\VEN_HAD0&DEV_22A8
    %String5%=NO_DRV,ACPI\VEN_ADC&DEV_081C

    [AAEON_SYS.NTAMD64]
    %String2%=NO_DRV,ACPI\VEN_8086&DEV_2288
    %String3%=NO_DRV,ACPI\VEN_8086&DEV_2289
    %String4%=NO_DRV,ACPI\VEN_HAD0&DEV_22A8
    %String5%=NO_DRV,ACPI\VEN_ADC&DEV_081C

    [DriverInstall.NT]

    [DriverInstall]

    [NO_DRV]

    [NO_DRV.Services]
    AddService = , %SPSVCINST_ASSOCSERVICE% ; null service install

    [Strings]
    String0="AAEON Technology Inc."
    String1="AAEON Technology Inc."
    String2="AAEON DEV_2288"
    String3="AAEON DEV_2289"
    String4="AAEON DEV_22A8"
    String5="TI ADC081C021 ADC"
    SPSVCINST_ASSOCSERVICE = 0x00000002
  • Dan O'DonovanDan O'Donovan Posts: 218Emutex mod
    For anyone who is wondering:

    These are PWM controllers on the CherryTrail SoC (connected to HAT header pins 32 and 33):
    String2="AAEON DEV_2288"
    String3="AAEON DEV_2289"

    This is a device entry in the ACPI table which was added to enable HDMI Audio on Linux, but isn't actually needed now (as far as I know):
    String4="AAEON DEV_22A8"

    This is an 8-bit ADC on the UP board, connected internally to I2C bus #3 and externally to HAT header pin 7:
    String5="TI ADC081C021 ADC"
  • jwilfongjwilfong Posts: 2New Member

    This is an old thread but I wanted to add what worked for me...

    Disable Windows 10 enforcement of driver signatures, then follow the instructions in the included doc file. Windows 10 enforcement of driver signatures will be reenabled automatically when you reboot after installing the driver.

    To disable:
    1. Click the windows Start menu and select Settings
    2. Click Update and Security
    3. Click on Recovery
    4. Click Restart now under Advanced Startup
    5. Click Troubleshoot
    6. Click Advanced options
    7. Click Startup Settings (if this does not appear, there should be a link for more options. It will then appear.
    8. Click Restart (Restarting will bring up another screen with various startup options)
    9. On the Startup Settings screen, press 7 or F7 to disable driver signature enforcement.

    Now, follow the included instructions for installation and the responses shown in the document will match what you see. Once you install the driver and restart the computer again the driver signature enforcement will b re-enabled.

Sign In or Register to comment.