iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
If Cross Device Experience Host stays pending, fails with an error, or is requested when you open Windows 11 mobile-device settings, work through these fixes in order: restart Windows, check the Microsoft Store update queue, reset the Store cache with WSReset.exe, try the package through WinGet, and only then consider broader Windows repair steps. The package ID reported for this component is 9NTXGKQ8P7N0. Store controls and package availability vary by Windows build, so a missing Store listing or troubleshooter does not necessarily mean you overlooked a step.
First identify which installation problem you have
“Cross Device Experience Host won’t install” can describe several different states. The right first move depends on what Windows is actually doing.
A Microsoft Store installation is stuck on Pending
This usually appears in the Microsoft Store queue after Windows or a Settings feature requests the component. A pending item can be waiting behind another Store download, paused by the Store, or blocked while the component is still running. A restart is the least disruptive way to clear a possible in-use condition.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows reports a failed update
Windows Update or Settings may show a failure instead of a Store queue entry. One Windows 11 Home 24H2 report identifies package ID 9NTXGKQ8P7N0-MicrosoftWindows.CrossDevice and error 0x80073D02. In that particular Q&A answer, the suggested explanation was that the component was running while Windows tried to update it. That is a case-specific diagnosis, not proof that every installation failure has the same cause.
#1 Best Overall
- 1.1 GHz (boost up to 2.4GHz) Intel Celeron N5030 Quad-Core
A mobile-device setting asks for the host, but no package is visible
Some users encounter the request after enabling Allow this PC to access your mobile devices and opening Manage Devices. A community report says selecting Add Device then initiated a Store update. Treat that route as an option when those controls are present; Windows builds and feature rollouts do not all expose the same labels or listing.
These states can overlap. For example, Settings can continue asking for the host while WinGet reports that the package is already installed, or the Store can show no searchable listing even though an update was requested from Add Device. Do not use the absence of one screen as proof that the package is missing from Windows. First record where the request appeared and whether Windows supplied an error code.
Before changing anything, record the state of Windows
Write down the exact message before retrying. Include whether the item is pending, the complete error code, and where you saw it (Microsoft Store, Settings, or Windows Update). This prevents a successful-looking retry from hiding the original failure and gives you useful information if you need support.
Recommended Free Tools
- Open Settings > System > About and note the Windows edition, version, and OS build. The reported
0x80073D02case was on Windows 11 Home 24H2; your build may behave differently. - Note whether Microsoft Store opens normally and whether you are signed in to the account used for Store apps.
- Close document editors, phone-linking windows, and other apps that could be using Windows’ cross-device features before attempting an update.
- If you eventually need a Windows repair upgrade, make a current backup of important files first. That is a substantial system operation, unlike the cache reset and restart steps below.
Also note whether other Store applications update successfully. If unrelated apps are downloading normally, the problem may be limited to this package or its registration. If the entire Store queue is stalled, start with the queue and cache steps rather than repeatedly selecting the mobile-device setting.
Fix 1: Restart Windows, then retry the installation
A restart is the safest first attempt when an update may be blocked by a running component. The rationale comes from advice in a case involving 0x80073D02; Microsoft has not established that an in-use process is the cause of every Cross Device Experience Host failure.
- Save your work and close all open applications.
- Open Start > Power and select Restart. Do not choose Shut down if you rely on Fast Startup and want a full refresh of the current session.
- After signing back in, wait a minute for background Store and Windows Update services to start.
- If the original prompt came from mobile-device settings, open Settings, return to the page that requested the host, and select the available retry, update, or Add Device control.
- If the request came from Microsoft Store, open the Store and check whether the pending item resumes. If it remains pending, continue to the Store-queue step rather than repeatedly restarting.
A restart does not repair a damaged Store cache or a broader Windows servicing problem. Its value is that it removes a transient process lock without uninstalling anything or changing system configuration. If the same error returns immediately after the restart, preserve the code and move on; several restart cycles are unlikely to add useful information.
Fix 2: Check the Microsoft Store update queue
Cross Device Experience Host is delivered as a Store package in the reports that identify it. A Store update can therefore be waiting even when the Settings page only says that a mobile-device feature needs an additional component.
- Open Microsoft Store from the Start menu.
- Look for Library, Downloads, or Downloads and updates. Microsoft has changed these labels between Store versions, so use the equivalent page that lists app updates if your version uses different wording.
- Select Get updates or the page’s refresh control, if shown. Let other queued Store updates finish or pause them temporarily so you can see whether the Cross Device package advances.
- If Cross Device Experience Host appears, allow the update to complete. Keep the Store open until the status changes from pending to installed or an explicit error appears.
- Return to the Windows feature that requested the host and test it again.
When the request originated in mobile-device settings, you can also return to Manage Devices and select Add Device if that control is available. One community report says this action initiated the Store update. It is a route to try, not a required sequence for every edition or rollout.
Rank #2
- 256 GB SSD of storage.
- Multitasking is easy with 16GB of RAM
- Equipped with a blazing fast Core i5 2.00 GHz processor.
Do not assume that the component must appear in a searchable Store catalog. Community answers conflict on whether a direct listing is visible, and Store availability can change with the Windows build and rollout. If the queue has no matching item, move to the cache reset or WinGet route instead of searching indefinitely.
Fix 3: Reset the Microsoft Store cache with WSReset.exe
Microsoft Community Support advice for a Store download failure includes WSReset.exe. This command clears the Microsoft Store cache and may reopen the Store. It is a troubleshooting attempt, not a guaranteed repair, and it does not remove your installed applications or personal files.
- Press Windows key + R to open the Run dialog.
- Enter
WSReset.exeexactly, then press Enter. - A blank command window may remain visible for a while. Do not close it while the reset is running.
- When the process finishes, Microsoft Store may open automatically. If it does not, launch it from Start.
- Open the Store’s Library or equivalent downloads page, refresh updates, and retry the Cross Device Experience Host installation.
The reset is deliberately narrow: it targets Store cache state rather than removing the Cross Device package or changing all user accounts. Sign in again only if Store asks you to, and then repeat the update check once. If the same pending state returns, capture a screenshot or the exact wording before trying another route.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →If the command returns immediately without opening Store, or the Store itself will not launch, note that result. Repeating the reset normally will not fix a damaged Windows servicing stack or a blocked account sign-in; those symptoms point toward Windows Update checks and, if necessary, escalation.
Fix 4: Try the package through WinGet
WinGet provides a command-line route to a Microsoft Store package when the Store interface does not expose a useful listing. Microsoft Learn describes the command this way: “The install command of winget installs the specified application.” The package ID reported by the community cases is 9NTXGKQ8P7N0.
Use the documented ID and Store source syntax
- Open Windows Terminal or Command Prompt. Running as administrator is not normally required for a per-user Store install; if Windows asks for elevation, use an account that is allowed to install Store apps.
- Run this command:
winget install --id 9NTXGKQ8P7N0 -s msstore- Read the package agreement and confirmation prompts. Confirm only if the displayed package is the Cross Device component you intended to install.
- Wait for WinGet to report completion, an existing installation, or an error. Then restart Windows once more and test the original Settings feature.
The shorter form winget install 9NTXGKQ8P7N0 appears in community replies, but specifying --id and -s msstore makes the intended Store package and source explicit. WinGet’s catalog and the package’s current Store state can vary, so a command that is syntactically correct may still return no package or no applicable update.
Interpret common WinGet results
- Installed already: The package may be present even though Settings continues to request it. One reported case had this mismatch; reinstalling the same package is not guaranteed to clear the prompt.
- No newer version available: WinGet sees an installed version and has nothing newer in its current source. This does not prove that the Windows feature is healthy.
- No package found: Check that the Microsoft Store source is available and that the ID was copied exactly. Store catalog or regional availability may differ from the report.
- Installation fails with another code: Preserve the complete output, including the code and source line. Do not jump directly to broad AppX removal commands.
WinGet is useful when the graphical Store path is missing, but it is not a bypass for every Store policy or account problem. A successful command also does not guarantee that an older Settings prompt will disappear immediately. Test the feature after restarting, then report both the command result and the Settings behavior if they disagree.
Fix 5: Check Windows Update, then escalate only for broader problems
If the Store and WinGet routes fail, determine whether Windows itself has pending servicing work. An incomplete cumulative update or a system component problem can prevent a Store-delivered component from registering correctly.
Rank #3
- 14" diagonal, 1366x768 resolution, HD BrightView LED, Glossy NON-TOUCH Display
- Open Settings > Windows Update.
- Select Check for updates and install updates that Windows offers. Restart when prompted, even if the Cross Device item is not named in the list.
- After the restart, repeat the relevant Store or WinGet check once. Capture any new error rather than cycling through the same commands.
- If Windows currently provides a Store Apps troubleshooter, you may run it from the troubleshooting area and follow its findings. Later users report that this troubleshooter and the Store listing cited in an older answer are absent on their systems, so do not treat either UI item as universal.
Check whether Windows Update itself is stuck on another download or asks for a restart. Finish that work first where possible. The goal is not to force-install the host with unrelated commands, but to remove a broader servicing condition that could be preventing registration.
When an in-place repair upgrade is justified
A Windows in-place upgrade is a substantial repair step, not a routine Cross Device Experience Host fix. One user reported following an agent’s recommendation because the Windows version was old and later said the immediate issue was moot, while planning to monitor it. That single experience does not establish the upgrade as a proven remedy for this component.
Consider this escalation only when the installation failure accompanies persistent Windows Update errors, multiple damaged system components, or an obviously outdated Windows installation, and only after safer steps have failed. Use Microsoft’s current Windows setup media and choose the option that preserves personal files and applications when it is offered. Back up important data first, keep the device on reliable power, and allow enough time for several restarts. Do not begin a repair upgrade solely because the Store package is pending once.
The trade-off is disruption: the first four routes are short, reversible troubleshooting attempts, while an in-place upgrade is lengthy and system-wide. It may consume considerable time even when it does not resolve a package-specific prompt, so document the original error and confirm that the broader repair is justified before starting.
Compare the five routes before choosing the next step
| Route | Where it runs | Disruption | What it can address | Important limitation |
|---|---|---|---|---|
| Restart | Windows power menu | Low; closes the current session | A transient process lock or unfinished background registration | Does not repair cache, catalog, or system corruption |
| Store update check | Microsoft Store Library or downloads page | Low | A queued or paused Store delivery | Labels and package visibility vary by build |
WSReset.exe |
Run dialog | Low | Store cache and download-state problems | Not a guaranteed fix for Windows servicing errors |
| WinGet command | Terminal or Command Prompt | Low to moderate | A Store package install when the UI is unhelpful | Package ID, source, account, and catalog state must line up |
| In-place repair upgrade | Windows Setup | High; lengthy and system-wide | Persistent Windows component or update corruption | Case-based escalation, not a confirmed CDEH-specific cure |
There is no supported hardware purchase that is part of this sequence. A new phone, cable, or replacement accessory does not address the Windows package state described here, and the troubleshooting routes use Windows, Microsoft Store, or WinGet rather than a third-party repair product.
What not to do as a first-line fix
The available reports do not establish clean booting, disabling security software, or removing the package for every user as necessary steps. Avoid turning a narrowly scoped Store problem into a wider system change without a specific diagnosis.
- Do not run
Remove-AppxPackage -AllUserscasually. The-AllUsersscope can remove a package across user accounts, and the reported cases do not establish that removal is required. - Do not disable antivirus or firewall protection merely because the Store is pending. If security software is suspected, use its documented, temporary troubleshooting mode and restore protection immediately; obtain a specific error first.
- Do not assume a new phone, cable, or Bluetooth accessory will install this Windows component. The documented problem is the Windows software package, not a proven hardware defect.
- Do not repeat WinGet indefinitely after it says the package is already installed. That result can coexist with a Settings prompt and calls for collecting evidence rather than forcing removal.
If none of the five fixes works
Collect a compact record before asking Microsoft support or posting in a Windows forum. Include the Windows edition, version and build; whether the Store queue was pending or produced an error; the complete error code; the exact WinGet output, if used; and whether WSReset.exe reopened the Store. Mention whether the problem affects one Windows account or every account on the PC.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Also describe the trigger precisely: for example, “Settings requested Cross Device Experience Host after I enabled Allow this PC to access your mobile devices,” or “Windows Update failed with 0x80073D02 on Windows 11 Home 24H2.” This distinction helps responders separate a Store delivery problem from a missing Settings control or a broader servicing failure.
Rank #4
- 【Efficient Performance】 Powered by Intel Core i3 processor (2 cores, 4 threads, up to 3.4GHz) with 12GB RAM and 256GB SSD. Handles multitasking, office software, online classes, and HD video streaming smoothly. Integrated Intel UHD Graphics 620
- Backlit Keyboard & Complete Package】Comes with a cool backlit keyboard. Comes with awebcam, dual stereo speakers (8Ω/1.0W each), DC charger, and user manual – ready for late-night studying, online classes, video conferencing, and daily productivity
- 【Vibrant Display】 15.6-inch Full HD (1920x1080) anti-glare screen with 16:9 aspect ratio delivers crisp images and vivid colors – perfect for studying, watching lectures, or entertainment. Thin-bezel design maximizes viewing area
- 【Fast Connectivity & Expansion】 Equipped with WiFi 6 (802.11ax) and Bluetooth 5.2 for stable, high-speed wireless. Features 3 x USB 3.0, HDMI 2.1, Type-C (supports PD3.0 fast charging), and a TF card slot expandable up to 2TB – easily connect external monitors, mice, drives, or expand storage for all your files
- 【Long Battery Life & Portable】 Built-in 11.55V 5000mAh/57.75Wh high-capacity battery delivers approximately 7 hours of mixed-use battery life – enough for a full day of classes and assignments. Lightweight at just 1.63kg (3.6 lbs) and 19.5mm thin, plus a compact packing size – easily slips into a backpack for campus, library, or coffee shop
Keep the sequence conservative: restart first, inspect the Store queue, reset its cache, try the documented WinGet command, and reserve a repair upgrade for evidence of wider Windows damage. The component may be running, queued, already installed, or unavailable in the current Store rollout, and each state requires a different next action.
Frequently Asked Questions
What is the Cross Device Experience Host package ID?
The package ID reported in Windows 11 community cases is 9NTXGKQ8P7N0. A related package string appears as 9NTXGKQ8P7N0-MicrosoftWindows.CrossDevice. Store availability and installed state can vary by Windows build.
Why does Windows show error 0x80073D02?
One Windows 11 Home 24H2 case received 0x80073D02. The answer in that case suggested the component was running while Windows tried to update it. Treat that as a case-specific explanation, restart, and preserve the exact error rather than assuming every failure has the same cause.
What should I do if WinGet says Cross Device Experience Host is already installed?
Restart Windows and test the original mobile-device setting again. A reported case had WinGet showing the package as installed while Settings continued requesting it, so an installed result does not guarantee that the prompt will clear.
Why can’t I find Cross Device Experience Host in Microsoft Store?
The component may not have a visible searchable listing on your build, or the Store rollout may expose it only through an update request. Check Library or Downloads, try the Add Device path if available, and use the documented WinGet command rather than assuming you missed a required listing.
Is WSReset.exe safe for this problem?
WSReset.exe resets Microsoft Store cache and may reopen the Store; it does not remove personal files or installed applications. It is a troubleshooting attempt, not a guaranteed fix for Windows servicing or account problems.
Should I perform a Windows in-place upgrade just to install this component?
No. An in-place repair upgrade is a substantial, time-consuming escalation mentioned in one case, not a proven Cross Device Experience Host remedy. Consider it only after safer steps fail and the PC also has persistent Windows Update or broader component problems; back up important files first.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The Bottom Line
Start with a restart, then check the Microsoft Store queue, reset its cache with WSReset.exe, and try winget install --id 9NTXGKQ8P7N0 -s msstore. Record every error and build number. Reserve an in-place repair upgrade for broader Windows problems, not a single pending package.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
