I have had this twice now.

I try to add a new USB device but for some reason it fails to work with
the program it should, even though the device is at least partially
detected by W10.

Leave to mulch for some time (probably until after the next W10 update)
and suddenly it springs to life.

Too many variables, too little time for a detailed diagnostic but it does
seem strange.

Now wondering if anyone else has seen this.

Cheers

Dave R

--
AMD FX-6300 in GA-990X-Gaming SLI-CF running Windows 10 x64

On 16/08/2023 16:17, David wrote:
> I have had this twice now.
>
> I " a new USB device but for some reason it fails to work with
> the program it should, even though the device is at least partially
> detected by W10.
>
> Leave to mulch for some time (probably until after the next W10 update)
> and suddenly it springs to life.
>
> Too many variables, too little time for a detailed diagnostic but it does
> seem strange.
>
> Now wondering if anyone else has seen this.
>
> Cheers
>
>
>
> Dave R
>
>

All sounds a bit vague to me.

What's the device ? - and are you provding some sort of driver for it,
or expecting it to work by the "magic" of Windows Plug and Pray

I have had similar experiences with a couple of graphics cards running
in dual screen mode.

Also, I have had experience with multi channel sound cards which Windows
never properly detect, and as a result never work with "the program they
should" (Cubase) until you get in there and spoon feed it a proper ASIO
driver

As you say ... too many variables

--
random signature text inserted here

On Wed, 16 Aug 2023 17:52:09 +0100, Abandoned_Trolley wrote:

> On 16/08/2023 16:17, David wrote:
>> I have had this twice now.
>>
>> I " a new USB device but for some reason it fails to work with the
>> program it should, even though the device is at least partially
>> detected by W10.
>>
>> Leave to mulch for some time (probably until after the next W10 update)
>> and suddenly it springs to life.
>>
>> Too many variables, too little time for a detailed diagnostic but it
>> does seem strange.
>>
>> Now wondering if anyone else has seen this.
>>
>> Cheers
>>
>>
>>
>> Dave R
>>
>>
>>
> All sounds a bit vague to me.
>
>
> What's the device ? - and are you provding some sort of driver for it,
> or expecting it to work by the "magic" of Windows Plug and Pray
>
> I have had similar experiences with a couple of graphics cards running
> in dual screen mode.
>
> Also, I have had experience with multi channel sound cards which Windows
> never properly detect, and as a result never work with "the program they
> should" (Cubase) until you get in there and spoon feed it a proper ASIO
> driver
>
>
>
> As you say ... too many variables

Two devices.

First was a GPS receiver tested on 2 * W10 (this laptop and an All-In-One).
IIRC it worked in W7 but not W8.1. Drivers supplied by manufacturer and
installed. Their test software worked but Windows would not recognise it
as a GPS device so not available to e.g. web browsers.

Second was a serial adapter cable coupled to a blood glucose monitor which
used to work under W7 until support was withdrawn.

This one tested on the laptop, desktop (now upgraded to W10).
Also didn't work on W8.1.
Latest drivers downloaded from manufacturer but no joy.
I could see the serial device being detected, but communication with the
glucose monitor from the web site didn't work.

This second one has just started working after the latest round of W10
updates in the last week.

Cheers

Dave R

--
Dell Latitude 7280 with Full HD and Thunderbolt (woo hoo)

On 17/08/2023 15:11, David wrote:
> On Wed, 16 Aug 2023 17:52:09 +0100, Abandoned_Trolley wrote:
>
>> On 16/08/2023 16:17, David wrote:
>>> I have had this twice now.
>>>
>>> I " a new USB device but for some reason it fails to work with the
>>> program it should, even though the device is at least partially
>>> detected by W10.
>>>
>>> Leave to mulch for some time (probably until after the next W10 update)
>>> and suddenly it springs to life.
>>>
>>> Too many variables, too little time for a detailed diagnostic but it
>>> does seem strange.
>>>
>>> Now wondering if anyone else has seen this.
>>>
>>> Cheers
>>>
>>>
>>>
>>> Dave R
>>>
>>>
>>>
>> All sounds a bit vague to me.
>>
>>
>> What's the device ? - and are you provding some sort of driver for it,
>> or expecting it to work by the "magic" of Windows Plug and Pray
>>
>> I have had similar experiences with a couple of graphics cards running
>> in dual screen mode.
>>
>> Also, I have had experience with multi channel sound cards which Windows
>> never properly detect, and as a result never work with "the program they
>> should" (Cubase) until you get in there and spoon feed it a proper ASIO
>> driver
>>
>>
>>
>> As you say ... too many variables
>
> Two devices.
>
> First was a GPS receiver tested on 2 * W10 (this laptop and an All-In-One).
> IIRC it worked in W7 but not W8.1. Drivers supplied by manufacturer and
> installed. Their test software worked but Windows would not recognise it
> as a GPS device so not available to e.g. web browsers.
>
> Second was a serial adapter cable coupled to a blood glucose monitor which
> used to work under W7 until support was withdrawn.
>
> This one tested on the laptop, desktop (now upgraded to W10).
> Also didn't work on W8.1.
> Latest drivers downloaded from manufacturer but no joy.
> I could see the serial device being detected, but communication with the
> glucose monitor from the web site didn't work.
>
> This second one has just started working after the latest round of W10
> updates in the last week.
>
> Cheers
>
>
> Dave R
>

"used to work under W7 until support was withdrawn" sort of suggests
that it might be pre W10 "legacy" ?

If thats the case then the only think I can think of is that the
installation program could be run in W7 compatbility mode ?

While you are in there you could run the compatibility troubleshooter ?

Its something that seems to have worked for me with a couple of NVidia
graphics cards but might just be another rabbit hole ...

--
random signature text inserted here

On Fri, 18 Aug 2023 07:52:56 +0100, Abandoned_Trolley wrote:

> On 17/08/2023 15:11, David wrote:
>> On Wed, 16 Aug 2023 17:52:09 +0100, Abandoned_Trolley wrote:
>>
>>> On 16/08/2023 16:17, David wrote:
>>>> I have had this twice now.
>>>>
>>>> I " a new USB device but for some reason it fails to work with the
>>>> program it should, even though the device is at least partially
>>>> detected by W10.
>>>>
>>>> Leave to mulch for some time (probably until after the next W10
>>>> update)
>>>> and suddenly it springs to life.
>>>>
>>>> Too many variables, too little time for a detailed diagnostic but it
>>>> does seem strange.
>>>>
>>>> Now wondering if anyone else has seen this.
>>>>
>>>> Cheers
>>>>
>>>>
>>>>
>>>> Dave R
>>>>
>>>>
>>>>
>>> All sounds a bit vague to me.
>>>
>>>
>>> What's the device ? - and are you provding some sort of driver for it,
>>> or expecting it to work by the "magic" of Windows Plug and Pray
>>>
>>> I have had similar experiences with a couple of graphics cards running
>>> in dual screen mode.
>>>
>>> Also, I have had experience with multi channel sound cards which
>>> Windows never properly detect, and as a result never work with "the
>>> program they should" (Cubase) until you get in there and spoon feed it
>>> a proper ASIO driver
>>>
>>>
>>>
>>> As you say ... too many variables
>>
>> Two devices.
>>
>> First was a GPS receiver tested on 2 * W10 (this laptop and an
>> All-In-One).
>> IIRC it worked in W7 but not W8.1. Drivers supplied by manufacturer and
>> installed. Their test software worked but Windows would not recognise
>> it as a GPS device so not available to e.g. web browsers.
>>
>> Second was a serial adapter cable coupled to a blood glucose monitor
>> which used to work under W7 until support was withdrawn.
>>
>> This one tested on the laptop, desktop (now upgraded to W10).
>> Also didn't work on W8.1.
>> Latest drivers downloaded from manufacturer but no joy.
>> I could see the serial device being detected, but communication with
>> the glucose monitor from the web site didn't work.
>>
>> This second one has just started working after the latest round of W10
>> updates in the last week.
>>
>> Cheers
>>
>>
>> Dave R
>>
>>
>
> "used to work under W7 until support was withdrawn" sort of suggests
> that it might be pre W10 "legacy" ?
>
>
> If thats the case then the only think I can think of is that the
> installation program could be run in W7 compatbility mode ?
>
> While you are in there you could run the compatibility troubleshooter ?
>
> Its something that seems to have worked for me with a couple of NVidia
> graphics cards but might just be another rabbit hole ...

Noting that as stated both devices are now working under W10.

For the BG monitor the drivers are up to date.
The web site refused to update the drivers under W7 because W7 was no
longer supported.
Drivers were updated under W10.
Even Viewer under W10 showed that the drivers were being associated with
the serial device, and the serial device was being identified.

Again, there seems no logical reason for it not to work.

Also no logical reason for it suddenly to start working.

Cheers

Dave R

--
Dell Latitude 7280 with Full HD and Thunderbolt (woo hoo)