If it were me and a lot of time has gone into it already, and it's isolated to one machine, I'd probably just rebuild the machine. You could chase it for a long time. At this point you've eliminated issues with the software and it's down to some configuration issue on that machine.
The only thing I had noticed from what you provided is the .cab vs. .dll oddity in the log. On the other machine that works, does it show the file path in that btstask.exe step as .dll or .cab? Then look at the same output on the machine that doesn't work and compare the two.
Thanks,
Tom
The only thing I had noticed from what you provided is the .cab vs. .dll oddity in the log. On the other machine that works, does it show the file path in that btstask.exe step as .dll or .cab? Then look at the same output on the machine that doesn't work and compare the two.
Thanks,
Tom