NEED TO RUN TROUBLESHOOTER FOR WINDOWS 10 SO THAT I CAN UPGRADE TO WINDOWS 11

Ron Oliver 0 Reputation points
2026-11-11T14:16:57.0566667+00:00

That is actually the most revealing result yet.

If Windows shows update policies are active, but when you open Group Policy Editor everything says "Not Configured", then the policies are probably not coming from Local Group Policy anymore.

They may be coming from:

  • Registry-based policies left behind by old software or an old business setup.
  • A previous management configuration related to TRISTAR.
  • A Windows Update policy that wasn't properly removed.

At this point, I don't think you're imagining the TRISTAR connection. The behavior is consistent with a machine that was once managed and never completely cleaned up.

Here's what I'd do next

Let's use a Microsoft tool instead of digging through settings.

  1. Open a web browser.
  2. Search for "Windows Update Troubleshooter Windows 10".
  3. Run the Windows Update troubleshooter.
  4. Let it complete all repairs it offers.
  5. Restart the PC.

Then check whether:

  • Check for updates is available again.
  • The "managed by your organization" message changes.
  • I AM UNABLE TO RUN WINDOWS UPDATE TROUBLESHOOTER SO THAT I CAN UPGRADE TO WINDOWS 11.

My assessment

The evidence now strongly suggests:

  • ✅ Your PC is Windows 11 compatible.
  • ✅ Your hardware is not the problem.
  • ✅ Your Windows license is probably not the problem.
  • ❌ Windows Update is being controlled by policies that are no longer visible in Group Policy.
  • ❌ Those policies are likely what's preventing updates and the Windows 11 upgrade.

You've done a fantastic job working through this. We've ruled out TPM, Secure Boot, hardware compatibility, work-school accounts, and domain membership. That narrows it down to a Windows Update configuration issue.

Let's try the Windows Update troubleshooter next, and tell me exactly what it reports when it finishes.That is actually the most revealing result yet.

If Windows shows update policies are active, but when you open Group Policy Editor everything says "Not Configured", then the policies are probably not coming from Local Group Policy anymore.

They may be coming from:

  • Registry-based policies left behind by old software or an old business setup.
  • A previous management configuration related to TRISTAR.
  • A Windows Update policy that wasn't properly removed.

At this point, I don't think you're imagining the TRISTAR connection. The behavior is consistent with a machine that was once managed and never completely cleaned up.

Here's what I'd do next

Let's use a Microsoft tool instead of digging through settings.

  1. Open a web browser.
  2. Search for "Windows Update Troubleshooter Windows 10".
  3. Run the Windows Update troubleshooter.
  4. Let it complete all repairs it offers.
  5. Restart the PC.

Then check whether:

  • Check for updates is available again.
  • The "managed by your organization" message changes.

My assessment

The evidence now strongly suggests:

  • ✅ Your PC is Windows 11 compatible.
  • ✅ Your hardware is not the problem.
  • ✅ Your Windows license is probably not the problem.
  • ❌ Windows Update is being controlled by policies that are no longer visible in Group Policy.
  • ❌ Those policies are likely what's preventing updates and the Windows 11 upgrade.

You've done a fantastic job working through this. We've ruled out TPM, Secure Boot, hardware compatibility, work-school accounts, and domain membership. That narrows it down to a Windows Update configuration issue.

Let's try the Windows Update troubleshooter next, and tell me exactly what it reports when it finishes.

Windows for home | Windows 10 | Windows update
0 comments No comments

2 answers

Sort by: Newest
  1. Ramesh 183.6K Reputation points Volunteer Moderator
    2026-11-11T14:28:39.5+00:00

    Hi Ron,

    From Command Prompt admin, please run these commands to remove the update policies.

    reg delete "HKCU\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /f
    reg delete "HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\WindowsUpdate" /f
    reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /f
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\WindowsUpdate" /f
    net stop bits
    net stop wuauserv
    net start bits
    net start wuauserv
    

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-11T14:17:24.67+00:00

    On Windows 10, the Windows Update troubleshooter can be run in either of these ways:

    1. Start with the automated troubleshooter in the Get Help app.
    2. If needed, go to Start > Settings > Update & Security > Troubleshoot > Additional troubleshooters.
    3. Under Get up and running, select Windows Update > Run the troubleshooter.
    4. Restart the device after it finishes.
    5. Then go to Start > Settings > Update & Security > Windows Update > Check for updates.

    If the issue continues, run the troubleshooter again to check for additional errors.

    If Windows Update still does not offer Windows 11 even though PC Health Check shows the device is eligible, a supported workaround is to use the Windows 11 Installation Assistant to upgrade manually.

    If the problem is recurring Windows Update failures, Windows also has automatic troubleshooters that may run on affected devices, but those troubleshooters cannot be run manually. Their status can be checked in troubleshooting history:

    • For the recurring monthly security update issue: Start > Settings > Update & Security > Troubleshoot > View history.
    • For the troubleshooter that repairs Windows Update system files and settings on certain Windows 10 versions: Start > Settings > Update & Security > Troubleshoot > View troubleshooting history.

    If manual troubleshooting is needed beyond the troubleshooter, Microsoft documents an advanced reset of Windows Update components from an elevated Command Prompt. This requires administrator permissions and command-line work:

    • net stop bits
    • net stop wuauserv
    • ren %systemroot%\softwaredistribution softwaredistribution.bak
    • ren %systemroot%\system32\catroot2 catroot2.bak
    • net start bits
    • net start wuauserv

    Then restart the computer.

    Warning: renaming the SoftwareDistribution and Catroot2 folders is an advanced repair step and should be used only if comfortable working in Command Prompt as an administrator.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.