none
why serial port missing after state switched in windows 8/8.1 RRS feed

  • Question

  • env: windows 8/8.1, both x86 and x64

    hardware: qualcomm 6240 usb to serial port

    after driver installed, there are 3 serial ports listed in device manger: Diagnostics, NMEA and Modem, which just works fine as windows xp and win7

    however, after Diagnostics rebooted internally, windows 8 only enumed one port: Diagnostics it self, the other two ports are missing; and windows xp/7 enumed 3 ports as we expected

    any suggestions?

    thanks in advance


    Wednesday, December 18, 2013 3:49 AM

All replies

  • and we have checked the change of registry, some values are deleted after Diagnostics rebooted, like:

    HKLM\HARDWARE\DEVICEMAP\SERIALCOMM\\Device\QCUSB_COM8_1: "COM8"
    HKLM\HARDWARE\DEVICEMAP\SERIALCOMM\\Device\QCUSB_COM10_2: "COM10"
    HKLM\HARDWARE\DEVICEMAP\SERIALCOMM\\Device\QCUSB_COM12_3: "COM12"
    HKLM\SYSTEM\ControlSet001\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}\0015\DriverDesc: "USB Composite Device"
    HKLM\SYSTEM\ControlSet001\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}\0015\ProviderName: "Microsoft"
    HKLM\SYSTEM\ControlSet001\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}\0015\DriverDateData:  00 80 8C A3 C5 94 C6 01
    HKLM\SYSTEM\ControlSet001\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}\0015\DriverDate: "6-21-2006"
    HKLM\SYSTEM\ControlSet001\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}\0015\DriverVersion: "6.3.9600.16384"
    HKLM\SYSTEM\ControlSet001\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}\0015\InfPath: "usb.inf"
    HKLM\SYSTEM\ControlSet001\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}\0015\InfSection: "Composite.Dev.NT"
    HKLM\SYSTEM\ControlSet001\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}\0015\MatchingDeviceId: "USB\COMPOSITE"
    HKLM\SYSTEM\ControlSet001\Services\Modem\Enum\0: "USB\VID_0409&PID_046E&MI_02\6&36fbfddb&a&0002"
    HKLM\SYSTEM\ControlSet001\Services\pt16usbser\Enum\1: "USB\VID_0409&PID_046E&MI_01\6&36fbfddb&a&0001"
    HKLM\SYSTEM\ControlSet001\Services\pt16usbser\Enum\2: "USB\VID_0409&PID_046E&MI_02\6&36fbfddb&a&0002"
    HKLM\SYSTEM\CurrentControlSet\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}\0015\DriverDesc: "USB Composite Device"
    HKLM\SYSTEM\CurrentControlSet\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}\0015\ProviderName: "Microsoft"
    HKLM\SYSTEM\CurrentControlSet\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}\0015\DriverDateData:  00 80 8C A3 C5 94 C6 01
    HKLM\SYSTEM\CurrentControlSet\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}\0015\DriverDate: "6-21-2006"
    HKLM\SYSTEM\CurrentControlSet\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}\0015\DriverVersion: "6.3.9600.16384"
    HKLM\SYSTEM\CurrentControlSet\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}\0015\InfPath: "usb.inf"
    HKLM\SYSTEM\CurrentControlSet\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}\0015\InfSection: "Composite.Dev.NT"
    HKLM\SYSTEM\CurrentControlSet\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}\0015\MatchingDeviceId: "USB\COMPOSITE"
    HKLM\SYSTEM\CurrentControlSet\Services\Modem\Enum\0: "USB\VID_0409&PID_046E&MI_02\6&36fbfddb&a&0002"
    HKLM\SYSTEM\CurrentControlSet\Services\pt16usbser\Enum\1: "USB\VID_0409&PID_046E&MI_01\6&36fbfddb&a&0001"
    HKLM\SYSTEM\CurrentControlSet\Services\pt16usbser\Enum\2: "USB\VID_0409&PID_046E&MI_02\6&36fbfddb&a&0002"


    Wednesday, December 18, 2013 3:55 AM
  • I guess you should contact your hardware vendor, what you are describing here is a hardware / driver problem not a Desktop Development problem / question.

    Best regards

    Bordon

    Note: Posted code pieces may not have a good programming style and may not perfect. It is also possible that they do not work in all situations. Code pieces are only indended to explain something particualar.

    Wednesday, December 18, 2013 6:33 AM
  • Thanks 
    Thursday, December 19, 2013 3:12 AM