Problem since Windows 10 Anniversary Update

As my computer implemented the Windows 10 Anniversary Update, I cannot assign the TQ Axis in the FMGS_Config anymore.
After the Windows Update I had to installed die Skalarki TQ USB driver manually again because the driver has no signature. http://www.mycockpit.org/forums/atta...id=11792&stc=1

The Hardware Device is installed successful and I can calibrate the TQ Axis in the skalarki profiler, but when I run FMGS_Config and move the Lever to recognized for the assignment, the axis was not been identified. The Levers are also not shown in the dropdown box.

http://www.mycockpit.org/forums/atta...id=11791&stc=1

If I select the windows controller button in FMGS_Config, the Skalarki TQ is not shown as a game controller. The hardware category of this device is unknown.
http://www.mycockpit.org/forums/atta...id=11790&stc=1

Does anyone also had this issue and know how to fix it?
Best regards

Hi

I would contact Marcin for that.

Regards,
JL

Hi,

I will contact him, but I am afraid that he will not do much, because in the skalarki profiler the hardware is recognized.

Best regards

The windows anniversary update has not changed anything in regards to my software. If it ran before, it will ran after.
If you are sure the TQ works, is recognized etc... then I would look into antivirus or firewall issues. The update may have changed your firewall settings, so resetting them is a good idea.

The Problem is not caused by firewall or antivirus program. I will try to connect the TQ on an USB2 hub.
Had the TQ so far connected to a USB3 hub. Has worked before the anniversary update but I've seen
that the driver for the USB3 hub was updated by Windows.
My last hope is that this is the cause. A reset to the last buid I've already tried.
But unfortunately failed.

The trial with the usb2 hub was also not successful.
The last option is to make a new full installtaion of windows 10 without the anniversary update.
Next time I will disable the windows update for new features.
My recommendation: Never change a running system.

Quote:

---

Originally Posted by Fritz

As my computer implemented the Windows 10 Anniversary Update, I cannot assign the TQ Axis in the FMGS_Config anymore.
After the Windows Update I had to installed die Skalarki TQ USB driver manually again because the driver has no signature. http://www.mycockpit.org/forums/atta...id=11792&stc=1

The Hardware Device is installed successful and I can calibrate the TQ Axis in the skalarki profiler, but when I run FMGS_Config and move the Lever to recognized for the assignment, the axis was not been identified. The Levers are also not shown in the dropdown box.

http://www.mycockpit.org/forums/atta...id=11791&stc=1

If I select the windows controller button in FMGS_Config, the Skalarki TQ is not shown as a game controller. The hardware category of this device is unknown.
http://www.mycockpit.org/forums/atta...id=11790&stc=1

Does anyone also had this issue and know how to fix it?
Best regards

---

Devices are detected, but all drivers were removed from windows. This is well known, that Windows Anniversary update removes unsigned USB drivers. So you need to reinstall all USB drivers again. When you making calibration in FMGS_Config make sure your profile is running. You need p3d/FSX running as well.

Quote:

---

Originally Posted by Fritz

The trial with the usb2 hub was also not successful.
The last option is to make a new full installtaion of windows 10 without the anniversary update.
Next time I will disable the windows update for new features.
My recommendation: Never change a running system.

---

I have updated quite few systems recently and always problem was related to USB drivers, nothing else. Check Device Manager to make sure all devices have drivers installed.

I also had to reinstall MCDU driver (disabling the w10 signed drivers control) after last SO update and MCDU works ;)

Quote:

---

Originally Posted by skalarki

... You need p3d/FSX running as well.

---

Is it correct that the profiler communicate with the FMGS_Config via FSUIPC?
That is why P3D/FSX need to be running.
As I considered this, the axis of the TQ where present in the dropdown box and I could calibrate it.

Thanks for the help. I have not thought about it anymore.

Aditional information for someone who also had problems after the anniversary update:
At my computer, the com port from my FCU has changed from com 3 to com 4 and the USB IDs from the radios has also been changed. I had to adjust the IDX Device number in the sioc.ini file because the FO radio was suddenly the CPT radio.