A): If the PC does not run with the card or the card is mistakenly detected in “Device Manager”, or if there is a yellow exclamation mark on the driver, or if “Device Manager” reports an error code “Code 10 - The device cannot start”, the card is in conflict with another device in your computer.

B): In most cases, this conflict can be solved by moving the card to another PCI (PCIe) slot, with the BIOS assigning other free resources to the card. If the move does not help, try the card separately, with no additional cards inserted. If the card cannot be moved to another slot, you can reset the BIOS of the computer (by jumper on the board or pulling out the backup battery, we recommend that you note all the original settings and reset everything to the required values). This will cause the IRQ, DMA, and I/O resources to be redistributed.

A): If the copy speed is approximately 35 MB/s, it means that the connection between the controller and the connected device is working only in the USB 2.0 mode. Some types of USB 3.0 devices may have a problem with proper detection.

B): Make sure that the connected device is USB 3.0 compatible. Please check if an additional power supply to the controller is connected (the power reduction is not included, the card is powered by a standard power connector that is part of each source; we recommend avoiding Molex connectors and splitters that often cause problems). The error could be caused by, for example, the old firmware of the device you want to connect, some manufacturers provide a new firmware to their products, which could solve this situation. Alternatively, try replacing the USB 3.0 cable that may be damaged. When testing, do not use USB 3.0 extensions that could also cause this problem.

A): Booting from an additional USB card is not possible because each card has a different chip. The BIOS of the motherboard does not contain information that will allow to "see" the connected USB device. Detection of attached devices occurs only after the additional card drivers have been booted when the operating system starts running.

B): When using the integrated USB from the motherboard, of course, the BIOS is programmed to include information about the chip of the controller used for USB on the motherboard. Therefore, the motherboard BIOS "sees" the connected USB device and therefore can boot from it.

A): Please check your BIOS settings. Power Management Setup – Wake Up Event Setup – Resume by PCI-E Device (individual items may vary by MB type) should be set to disabled.

B): If this does not help, try updating your motherboard BIOS and check the ACPI item when still in the BIOS If not even this helps, move the controller card to another PCIe slot (may also be x16 - slots differ only in the number of lines). It is possible that the card is in conflict with another device on your computer. For some types of BIOS, you can do this directly by enabling Force Update ESCD (Reset Configuration Data etc.) in the PnP & PCI Configurations menu. This will cause the IRQ, DMA, and I/O resources to be redistributed.

A): The VBScript is incorrectly registered in your Windows installation.

B): To fix the problem and download the patch go to Microsoft site: https://blogs.technet.microsoft.com/fixit4me/2009/01/30/register-windows-script-engine-fix-it-live/