Skip to content

Fix FwLite auto-update by rolling back AppInstaller namespace to 2018 - #2615

Open
hahn-kev-bot wants to merge 1 commit into
developfrom
claude/fwlite-xml-namespace-fix-70ccba
Open

Fix FwLite auto-update by rolling back AppInstaller namespace to 2018#2615
hahn-kev-bot wants to merge 1 commit into
developfrom
claude/fwlite-xml-namespace-fix-70ccba

Conversation

@hahn-kev-bot

@hahn-kev-bot hahn-kev-bot commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator

running Get-AppxPackageAutoUpdateSettings -PackageFamilyName FwLiteDesktop_01zkby2q2skmg on my machine said that automatic background updates were not enabled when using the app installer with a root namespace 2021. Changing it to 2018 fixed that. I'm still waiting to see when windows actually runs an update check, but it does say it will check every 24 hrs now.


AI summary

The generated .appinstaller file declared its root namespace as http://schemas.microsoft.com/appx/appinstaller/2021. Per Microsoft's AppInstaller schema reference, the root namespace version dictates the minimum OS required to parse the file at all — the 2021 namespace requires Windows 11 21H2 (build 22000). On Windows 10 and older Windows 11 builds, the App Installer can't parse the file, so the update check silently fails and auto-update never happens.

The only UpdateSettings elements we use — AutomaticBackgroundTask (min Windows 10 1803) and ForceUpdateFromAnyVersion (min 1903) per the update settings docs — long predate 2021 and are valid unprefixed under the 2018 namespace (matching Microsoft's own documented examples). Rolling the root namespace back to 2018 restores compatibility down to Windows 10 1803 while keeping every element we rely on.

Change is a single-line namespace swap in FwLiteReleaseService.GenerateAppInstaller. No test asserted the namespace string; the one test that parses the generated XML only reads the root Uri attribute and is unaffected.

Note: only FwLite testers are on this update track today, so no broad-fleet impact. Installs already pinned to the 2021-namespace file recover once an App Installer that can parse the corrected file fetches it; any truly stuck may need a manual reinstall.

Test plan

  • Existing FwLiteReleaseServiceTests still pass (XML parse + Uri assertion unaffected)
  • Verify a Windows 10 install successfully picks up an update via the regenerated .appinstaller

The 2021 root namespace forces a minimum OS of Windows 11 21H2 (build
22000) to even parse the .appinstaller file, so auto-update silently
breaks on Windows 10 and older Windows 11. The only UpdateSettings
elements we use (AutomaticBackgroundTask, ForceUpdateFromAnyVersion)
date to 1803/1903 and are valid unprefixed under the 2018 namespace,
which restores Windows 10 1803+ compatibility.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Team

Run ID: c5252157-9fc0-4d3b-945f-984d0f0f74d6


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added the 📦 Lexbox issues related to any server side code, fw-headless included label Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

📦 Lexbox issues related to any server side code, fw-headless included

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants