microsoft
CmdPal: Command palette breaks Gamepass games updates
Microsoft PowerToys version
0.90.1
Installation method
PowerToys auto-update
Area(s) with issue?
Command Palette
Steps to reproduce
For about 2 weeks I was fighting with Gamepass issue. Games installed fine but when updating download process hang eventually giving code 0x80070020. After reading around I've found this Reddid post suggesting that I should check what's locking appmanifest.xml in game installation folder. Few clicks in File Locksmith later revealed that culprit is cmdpal.exe. Disabling command palette in powertoys settings and reboot fixed my issue.
✔️ Expected Behavior
Gamepass games should update fine regardless if powertoys are installed
❌ Actual Behavior
cmdpal.exe is locking .xml files in gamepass game folders causing updates to fail.
Additional Information
Windows 11, all latest updates from windows update. Not running powertoys as an admin.
Other Software
No response
Just came across it with issues updating DOOM: The Dark Ages, really confusing why would this app lock the appmanifest.xml, even restarting the PC and doing nothing but trying to update the game still does not work. It does not need to disable it, I simple closed the app, updated, then started it again.
my issue was with avowed updating. only way it worked was to disable command palette.
think I'm going to wait a little while longer to use it since they're still fixing quite a few bugs and powertoys run still works fine & doesn't affect gamepass game updates
Same issue here with every game in the XBox app. It's been the same for the last 3 weeks I was getting a 0x80070020 error. I uninstalled powertoys and it resolved it. Windows 11 24h2 with latest update of PowerToys.
I came across the same problem a while ago and only today found out what the source was, see my issue #39622.
To provide additional context from my issue without adding everything else: I solved it by opening the game's folder in File Locksmith, which showed me Command Palette was using the folder and allowed me to end its process. Afterwards, I could update my games. Not only that: after I manually disabled and enabled Command Palette, I still could update everything. It seems like it's just sometimes getting into Xbox games' folders and just keeping a lock without letting go?
(I'm on the newest version of PowerToys (91.1) and Win10 Pro 64bit)
Currently on v0.91 of PowerToys and this bug actually prevented me from updating any Xbox/Windows Store game (all of which are not installed on the C drive). I honestly didn't even know it was Command Palette until just now after several MONTHS of this issue plaguing my system.
For a while my only hope to update these programs/games was to reboot my system and pray I get it to update before whatever was causing it prevented me from going forward.
Found out about that today. Thought I was going crazy. This is pretty problematic :D
this needs to be linked from the Microsoft KB for https://support.xbox.com/en-GB/help/errors/error-code-80070020
Couldn't update Forza because of this tool. Thanks to a rediit post I came accross this bug.
I don't get why with every game update, some kind of microsoft bug is casuing it not to update. This time it's this tool, next time it's Windows Update itself. Before it was some delivery service.
I don't get it. STEAM ALWAYS WORKS. Why is everything at Microsoft always a big fail. Not sometimes, but ALWAYS.
can confirm about this bug. this actually led to me reinstall a lot of my games in the past few weeks, until I found this is apparently a bug with command pallete which i never use anyway. disabling it immediately fixed all my issues
@webstylecenter I'm not sure the general Microsoft hate is appropriate in this specific instance because PowerToys is normally an exceptionally well working piece of software (and afaik it's not a fully official in-house developed software like most MS software). It also doesn't feel like typical MS software specifically because it normally "just works".
But I agree that this is a really bad problem to have. I also have probably re-installed around 400GB of games over this.
I can confirm this. It took quite a while to figure out why I was getting error 0x80070020 when trying to repair games in the XBox app. Quitting PowerToys immediately fixed this issue.
I found out about this in a reddit post, never occurred to me that the command palette was the one interfering with the Xbox games updates. After disabling games started updating properly
Leaving some sysinfo if that helps
Version: 0.91.1
Processor AMD Ryzen 7 9800X3D 8-Core Processor 4.70 GHz Installed RAM 64.0 GB (61.6 GB usable) System type 64-bit operating system, x64-based processor
Edition Windows 11 Pro Version 24H2 Installed on 13/12/2024 OS build 26100.4061 Experience Windows Feature Experience Pack 1000.26100.84.0
This seems to have been fixed for me since I upgraded to latest 0.92 version of power toys. Had 3 different games update without issues while command palette was running
@holandes22 when I tested it before the last update, it sometimes let me download many updates, sometimes even a full day of updates. But then it would suddenly break. I'd let this issue open for a bit longer to be sure.
@Panossa After the update it worked every time for me (different days, between reboots)
But yeah, make sense to keep it open and see if others can confirm is now fixed
After upgrading to 0.92, this issue has been fixed for me. I had been unable to download game updates on the Xbox app (PC Game Pass), but I can now do so without issue.
Hey folks, wanted to check in to see if people are still running into this issue?
I'm not having the issue but the latest patch which rolled out just recently have yet to fully test but apps seem to still be updating Xbox store content
Edit : Updated a few games today issue seems resolved with the most recent so hasn't come back under 0.94.2
Can't really tell since I haven't updated a game since my last comment here but since no other person has reported anything after all this time (this issue is quite easy to find), I'd assume it's fixed?
Cool, I'll close the issue for now and we can re-open in case folks run into it again in the future!