this post was submitted on 21 Nov 2025
971 points (97.6% liked)

Technology

78003 readers
3401 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] mech@feddit.org 233 points 1 month ago* (last edited 1 month ago) (36 children)

Microsoft says that it is working on a fix but, for now, has provided a couple of workarounds to deal with the issue. First, Microsoft says that restarting the Shell Infrastructure host (SIHost.exe) service will help restore the missing Immersive Shell packages. This can be done with the following commands:

Add-AppxPackage -Register -Path 'C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\appxmanifest.xml' -DisableDevelopmentMode  
Add-AppxPackage -Register -Path 'C:\Windows\SystemApps\Microsoft.UI.Xaml.CBS_8wekyb3d8bbwe\appxmanifest.xml' -DisableDevelopmentMode  
Add-AppxPackage -Register -Path 'C:\Windows\SystemApps\MicrosoftWindows.Client.Core_cw5n1h2txyewy\appxmanifest.xml' -DisableDevelopmentMode  

Second, a PowerShell logon script has been shared that essentially blocks Explorer from launching prematurely until the required packages are fully provisioned. The batch script for that is given below:

@echo off  
REM Register MicrosoftWindows.Client.CBS  
powershell.exe -ExecutionPolicy Bypass -Command "Add-AppxPackage -Register -Path 'C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\appxmanifest.xml' -DisableDevelopmentMode"
REM Register Microsoft.UI.Xaml.CBS  
powershell.exe -ExecutionPolicy Bypass -Command "Add-AppxPackage -Register -Path 'C:\Windows\SystemApps\Microsoft.UI.Xaml.CBS_8wekyb3d8bbwe\appxmanifest.xml' -DisableDevelopmentMode"  
REM Register MicrosoftWindows.Client.Core  
powershell.exe -ExecutionPolicy Bypass -Command "Add-AppxPackage -Register -Path 'C:\Windows\SystemApps\MicrosoftWindows.Client.Core_cw5n1h2txyewy\appxmanifest.xml' -DisableDevelopmentMode"  

I swear to god, if I hear "Windows just works" one more goddamn time...

[–] 1995ToyotaCorolla@lemmy.world 2 points 1 month ago

“Linux is an objectively worse OS because you have to run all kinds of weird commands in an esoteric command line to even get it to work right”

Meanwhile: windows just works! You just have to run this batch file from some guy on GitHub, download this powershell script from some woman on MSDN, apply these reg hacks, and run this freeware debloat tool, and it’s smooth sailing after that. Well, at least until the next cumulative update which will make you repeat this process all over again. Oh whoops, something you did broke the install. Better sfc /scannow or clean install and try again!

load more comments (35 replies)