Controller issues

By Lord Nite
in Xbox

 Share

Recommended Posts

Experienced

Lord Nite

Posted
Posted

When I installed the 1904 update, I had a strange issue crop up. My controller would show as connected, but I couldn't use it at all. I was able to use my media remote to control the Xbox, but that was about it.

 

I did reset the Xbox twice. It would fix the issue for a few minutes, but it would start again. I removed The Division 2 beta thinking that was affecting it, but the controller would stop working after a few minutes regardless. I have left the insider program and reverted back to 1902 and haven't had an issue since.

 

Had anyone else encountered this?

Link to comment
https://www.neowin.net/forum/topic/1380381-controller-issues/
Share on other sites
  • 10 months later...
Experienced

Lord Nite

Posted
  • Author
Posted

I know this is a dead post, but I wanted to update with my discovery just in case someone else has this issue.

 

I discovered that the WiFi board on the XBox died.  It's a moderate process to replace, but it can be done with the right tools.

 

WiFi board replacement guide (ifixit.com)

  • 11 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Posts

    • Browser vendors pen open letter to Microsoft saying "enough is enough"

      By The Norwegian Drone Pilot · Posted

      The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. Sure, the way Microsoft is pushing Microsoft Edge on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more

      By David Uzondu · Posted

      JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • Browser vendors pen open letter to Microsoft saying "enough is enough"

      By haxasaur · Posted

      That stupid annoying Sign in with Google on all these sites now... get the fk outta here
    • Cuktech 10 Ultra charger review: big display, four ports, 110W total power

      By Elliot B. · Posted

      I was just being silly based on David Uzondu's comment ☺️
    • Still using Classic Outlook? Microsoft highlights 15 reasons to switch to New Outlook

      By rseiler · Posted

      The unified inbox, when it arrives, will be a powerful argument for those who have > 1.

  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later

  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!