Since the KB3081424 and KB2993928 updates, my Ps3 Fightstick stopped working properly. The stick is detected by windows and shows up in the devices and printers as 'PC USB Wired Stick 8838', which is consistent with what I had before and worked fine yesterday before the update. I know for a fact that this stick uses USB 1.1 and therefore requires UHCI compliant hardware. My computer has both USB 2.0 and 3.0 ports, the USB 2.0 not being UHCI compliant and the USB 3.0 being xHCI compliant which is why I was using the latter to connect the stick. The problem: Windows, that is the game controller settings properties test interface, is not picking up any input from the stick.
This is what used to happen when trying to make the stick work on a USB 2.0. My guess is that the update broke something in the USB 3.0 xHCI support. I tried: - The automatic troubleshooting method, which tells me to change the stick from USB 3.0 to USB 2.0 (which does not work - same symptoms and no solution from the automatic troubleshooter).
Uninstalling KB3081424, which does not help. I don't seem to have the option of uninstalling KB2993928. Uninstalling/reinstalling the device. Hi, Thank you for posting your query on Microsoft Community. KB2993928 update is related to ASP.net, and KB3081424 updates is to enhance the functionality of Windows 10.
Therefore, I suggest you update your Universal bus controller drivers in the compatibility mode. Follow the steps to update the audio drivers:. Press Windows key + X key and click Device Manager. Expand the Universal Bus Controller.
Right-click on the Universal Bus Controller and click on Update driver software. Restart the computer and check. I would also recommend you to click on the below link and try the steps provided in this link, see if this helps. Hope this helps.
Please respond if you have further related queries. Regards, Jesinta Rozario. While the fix seemed to have worked, the USB 1.1 support broke again today after the latest NVidia graphic driver update. After Uninstalling/reinstalling the usb controllers, i tried different versions of the ASMedia drivers ranging from 1.16.16 in compatibility mode to 1.16.26.1 and nothing seems to have an effect. I should be able to get the fightstick to work again in a week or so by getting a replacement PCB and modding it, but I'd really like to have support for USB 1.1 working as it should be. Hello Erihpax, Thank you for posting your query in Microsoft Community. I understand the inconvenience caused to you.
I will be glad to assist you with your issue. What is the make and model of your computer? As the steps given by Jesinta didn't work for you, I suggest you to update your BIOS and check if it helps. The steps given by Jesinta didn't work for you might be because of the difference in motherboard, So I would need the make and model of your computer. Keep us updated with the status of the issue.
We will be glad to assist you.
Installing Windows on a Mac should be a piece of cake with Bootcamp, but that rarely is the case. In fact, I would personally say that Boot Camp Assistant is one of the worst apps that comes with OS X and unlike the rest, it doesn’t work seamlessly. A few of its drawbacks:. It only supports a drive with a single partition. It often throws very obscure error messages with limited detail. It re-downloads 1.6 GB Windows drivers every single time it runs.
These are placed under /Library/Application Support/BootCamp/WindowsSupport.dmg and deleted and re-downloaded each time Boot Camp Assistant starts processing. This post did take a lot of work to complie and I did bone my hard drive a few times while trying certain ideas, so please throw out a thanks if it helped you out:) Disclaimer: This guide below contains procedures which can potentially destroy your partitions and data.
I accept no responsibility for such loss so please proceed at your own risk. Update (2016-07-20): I have updated this post with further improvements relating to downloading of Boot Camp drivers and ensuring that a Hybrid MBR is not used (which would cause issues when installing Windows).
What You Will Need. An 8 GB or larger USB stick. A copy of the. A valid Windows 10 license. A downloaded copy of Downloading Boot Camp Drivers. Start Boot Camp Assistant.
Select Action / Download Windows Support Software. Choose your Downloads directory, enter your password and then click Save This will be the only step that we will use Boot Camp Assistant for. Diskutil list FAT32 You’ll see your USB drive in the output and it should look something like this: /dev/disk2 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: FDiskpartitionscheme.16.0 GB disk2 1: DOSFAT32 FAT32 16.0 GB disk2s1 Once you have kicked off unetbootin, grab a snack while the Windows ISO is copied to the USB stick. This process takes around 15 minutes to complete. Finishing Up When this has completed, you may right click on the USB stick in Finder, select Rename “FAT32” and rename it as you like (I’ll call mine “WINDOWS 10”). Finally, copy the WindowsSupport in your Downloads directory to the Windows 10 USB stick so it’s easy to get to after our installation. Partitioning Your Drive In Disk Utility, select your internal hard drive on the left panel, and click on Partition.
Click the + button and create a new partition of your desired size for your Windows installation and name it as you wish (I’ll call mine “BOOTCAMP”). Ensure that the Format is set to MS-DOS (FAT) and click on Apply. Ensuring that a Hybrid MBR is not used Huge thanks to Rod’s post from the superuser post titled.
Once you add a FAT32 partition with either Boot Camp Assistant or Disk Utility, your disk is converted into a hybrid GPT / MBR disk which is actually not supported by newer versions of Windows. In this step, we revert this additional change made by Disk Utility by switching back to a pure GPT partition table. Dowload the latest version of by browsing to the version, then gdisk-binaries and clicking the file with the.pkg extension (e.g. Install GPT fdisk by running the installer you downloaded. Open a Terminal and check the state of your MBR. Sudo gdisk /dev/disk0 If your MBR partition is set to hybrid, please continue with step 4, otherwise if it is set to protective, you may skip the rest of this section.
Simply type q and hit return to exit GPT fdisk. Type p to view the existing partition table and verify you’re working on the correct disk. Type x to enter the expert menu. Type n to create a fresh protective MBR. Type w to save your changes and confirm the change when asked. Type q to exit GPT fdisk. Run GPT fdisk to show your disk layout.
GPT fdisk (gdisk ) version 1.0.1 Warning: Devices opened with shared lock will not have their partition table automatically reloaded! Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Installing Windows Disconnecting All Devices From USB Ports This step is critical as I have had rather serious problems during Windows installation when certain external drives are connected. Unplug everything from your Mac except your keyboard (if wired) and your bootable Windows USB stick (which we prepared earlier). If your Mac contains multiple physical drives, you will need to disconnect all disks except the one which you intend to install Windows on or you may encounter the following error: Windows could not prepare the computer to boot into the next phase of installation. To install Windows, restart the installation.
Booting From the USB Stick Ensure that the USB stick containing the Windows installer is inserted and then restart your Mac while holding down the option (alt) key. You should now be presented with a list of bootable drives. Select the USB drive (usually titled “EFI Boot”) to begin installing Windows.
Correcting Your Windows Hard Disk Partition When you are asked Where do you want to install Windows?, select the Windows partition created earlier (which I called “BOOTCAMP”) and click Delete. Next, select the chunk of Unallocated Space and click on New to create a proper Windows NTFS partition. Note: OS X only supports creation of FAT filesystems, so this is why we need to re-create the partition ourselves during install. Completing the Installation Allow the installer to complete and boot into Windows.
Installing Boot Camp Support Software Once Windows is up and running, install the Boot Camp Support software running WindowsSupport/BootCamp/Setup.exe on your USB stick. Note: The installer takes a little while to show up, so please be patient. You may encounter a known issue whereby the Boot Camp Support Software installer locks up while installing Realtek audio.
If this occurs, you will need to open Task Manager and kill the RealtekSetup.exe process. After the installer has completed, answer No when prompted to reboot and install the Realtek drivers manually by running%USERPROFILE% AppData Local Temp RarSFX0 BootCamp Drivers RealTek RealtekSetup.exe. If you can’t find this file, check any other directories starting with RARSFX under%USERPROFILE% AppData Local Temp. Once complete, reboot Windows. What You Will Need to Configure Windows.
The latest version of. The (see README for a download link) Configuring Windows Mapping Your Mac Keyboard Install and run SharpKeys and then configure the following mappings to correct your Mac keyboard so that it behaves like a regular Windows keyboard: Function: F13 - Special: PrtSc Special: Left Alt = Special: Left Windows Special: Left Windows = Special: Left Alt Special: Right Alt = Special: Right Windows Special: Right Windows = Special: Right Alt Note: for F13, you’ll need to select Press a key and click F13 on your keyboard. Switching to Natural Scrolling If you wish to flip scrolling direction to match that on OS X, run FlipWheel.exe and then click on Flip All. Enabling Num Lock on Boot Paste the following into a file named Enable NumLock on Boot.reg then import this into the registry to enable NumLock when Windows boots up (it doesn’t by default). Windows Registry Editor Version 5.00 HKEYUSERS.DEFAULT Control Panel Keyboard 'InitialKeyboardIndicators'='80000002' Completing Configuration That’s it, give your machine one last reboot and you’ll have a fully working Windows 10 installation. Note: I have found Apple’s Magic Mouse to be extremely unreliable using the Boot Camp drivers from Apple. As such, I recommend purchasing a Logitech (or similar) mouse for use in Windows.
I have no trouble plugging the wireless receiver for my Logitech mouse into one of the USB ports of my wired Apple Keyboard and it’s so tiny that you can’t see it at all. Cleaning up a Windows Installation Removing the Windows Partitions If you decide to remove Windows, you may find that Disk Utility doesn’t allow you to delete the two partitions that have been created by the Windows installer. This happens due to the fact that the first small partition created is of a type called Microsoft Reserved which OS X’s Disk Utility doesn’t support. The safest way to delete these partitions is through the Windows installer.
So simply boot from your USB stick as we did before and when you reach the Where do you want to install Windows? Question, you may delete your “BOOTCAMP” partition and the small 16 MB partition of type MSR (Reserved) just above the BOOTCAMP partition.
Once done, simply quit the installer by clicking the X in the top right corner of each Window and reboot back into OS X. Removing the Boot Entry Even though we have removed the Windows partition, a boot entry will still be present when holding down option (alt) during boot. You may remove these items by running the following in your Terminal.