Copilot App in Windows 10. not starting keeps loading but nothing appears

Question

Copilot App in Windows 10. not starting keeps loading but nothing appears

Monica Meza 10

When I try to open the app from taskbar the icon disappears and no window opens as it usually does. When I try to open from the app menu or the start menu a white bar is visible under the icon like it is loading but it just stay like that, no window opens(no running app).

I have try to uninstall the app, restart the pc and install again. It works once the apps does work, but as soon as I close it everything replies again. the loading white bar under the icon and it never starts. I am repairing the app every time I need it and also keep it open even if I don't need it just for it to stay working correctly. pc updates are current.

task manager is another site I looked and the process isn't showing in there.

What can I do to fix it?

Tom Driscoll 0 Reputation points

2026-04-18T16:42:23.6366667+00:00

Since the windows 10 updates this week, my copilot has been doing EXACTLY what you stated.

2 answers

Your answer

Tom Driscoll 0 Reputation points

2026-04-18T16:42:23.6366667+00:00

Since the windows 10 updates this week, my copilot has been doing EXACTLY what you stated.

Answer 1

Hendrix-V 14,170 Microsoft External Staff Moderator

Hi Monica Meza,

Thank you for reaching out.

Based on your experience, where the Copilot app works immediately after reinstall or repair but stops launching again once it’s closed, this may be related to how the app’s runtime registration is being initialized in your Windows user profile after the first launch. In this scenario, reinstalling the app replaces the files but may not fully refresh its activation registration.

After the next reinstall, you may try these extra steps to re‑register the App Package

Right‑click Start
Select Windows Terminal (Admin)
Run this command:

Get-AppxPackage -AllUsers Microsoft.Copilot | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

Wait for the command to complete.

Let me know if you need further assistance, feel free to ask me by clicking "Add Comment" or "Add Answer" if you cannot add comment so your response will be visible. Thanks for your effort.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Monica Meza 10 Reputation points

2026-04-17T13:17:56.62+00:00
this is what I get doing what you suggested.

Windows PowerShell

Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6 PS C:\Windows\system32> Get-AppxPackage -AllUsers Microsoft.Copilot | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF6, Package could not be registered.

error 0x800701C9: While preparing to process the request, the system failed to register the windows.capability

extension due to the following error: None of the authorized entity elements in the SCCD matched the app being

installed; either the PFNs don't match, or the element's signature hash doesn't validate.

.

NOTE: For additional information, look for [ActivityId] d46d4b9a-ce60-0000-5743-6fd460cedc01 in the Event Log or use

the command line Get-AppPackageLog -ActivityID d46d4b9a-ce60-0000-5743-6fd460cedc01

At line:1 char:56

... | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.I ...

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo : WriteError: (C:\Program File...ppXManifest.xml:String) [Add-AppxPackage], IOException

FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

PS C:\Windows\system32>
DarlaKay 5 Reputation points

2026-04-17T23:11:38.84+00:00
I have the same problem as op. When I try the suggested fix I receive the below return. There must be another fix and I'm sure we can't be the ony 2 people with this problem. Mine began after last Win 10 update.

Add-AppxPackage : Cannot find path 'C:\AppXManifest.xml' because it does not exist.

At line:1 char:56

+ ... | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.I ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

**+ CategoryInfo : ObjectNotFound: (C:\AppXManifest.xml:String) [Add-AppxPackage], ItemNotFoundException** **+ FullyQualifiedErrorId : PathNotFound,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand**

Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF6, Package could not be registered.

error 0x800701C9: While preparing to process the request, the system failed to register the windows.capability

extension due to the following error: None of the authorized entity elements in the SCCD matched the app being

installed; either the PFNs don't match, or the element's signature hash doesn't validate.

.

NOTE: For additional information, look for [ActivityId] ca6daa53-cd05-0005-e7cf-82ca05cddc01 in the Event Log or use

the command line Get-AppPackageLog -ActivityID ca6daa53-cd05-0005-e7cf-82ca05cddc01

At line:1 char:56

+ ... | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.I ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

**+ CategoryInfo : WriteError: (C:\Program File...ppXManifest.xml:String) [Add-AppxPackage], IOException** **+ FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand**
Hendrix-V 14,170 Reputation points Microsoft External Staff Moderator

2026-04-18T07:35:38.66+00:00
Hi Monica Meza and DarlaKay,

Thank you for updating on this issue.

Based on the error returned when attempting to re‑register the Copilot package, this indicates that the Copilot runtime capability could not be validated against the local Windows capability licensing store. In this scenario, the app UI installs successfully, however its runtime component may not complete activation after the initial launch, which can prevent it from reopening once closed.

Please try these steps to reset capability licensing store:

1, Right‑click Start > Select Windows Terminal (Admin), run the following command lines

2, Stop licensing services:

sc stop ClipSVC sc stop TokenBroker

3, Reset the capability repository:

takeown /f "C:\ProgramData\Microsoft\Windows\AppRepository" /r /d y icacls "C:\ProgramData\Microsoft\Windows\AppRepository" /grant administrators:F /t

cd C:\ProgramData\Microsoft\Windows\AppRepository ren StateRepository* StateRepository.old ren SystemAppData SystemAppData.old

4, Restart licensing service:

sc start ClipSVC

5, Restart the device, reinstall Copilot then Launch > Close > Reopen to confirm normal behavior.

If launching still fails, run the following system repair commands, then test again:

DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow

If you have any further questions or updates regarding this issue, please feel free to let me know in the Comments section. I'd be happy to assist you.
DarlaKay 5 Reputation points

2026-04-18T17:36:52.28+00:00
Thanks Hendrix, I hit a snag in the 2nd part of step 3:

PS C:\WINDOWS\system32> cd C:\ProgramData\Microsoft\Windows\AppRepository

ren StateRepository* StateRepository.old

ren SystemAppData SystemAppData.old

ren : Cannot process argument because the value of argument "path" is not valid. Change the value of the "path"

argument and run the operation again.

At line:2 char:1

ren StateRepository* StateRepository.old

+ CategoryInfo : InvalidArgument: (:) [Rename-Item], PSArgumentException + FullyQualifiedErrorId : Argument,Microsoft.PowerShell.Commands.RenameItemCommand

ren : Cannot rename because item at 'SystemAppData' does not exist.

At line:3 char:1

ren SystemAppData SystemAppData.old

+ CategoryInfo : InvalidOperation: (:) [Rename-Item], PSInvalidOperationException + FullyQualifiedErrorId : InvalidOperation,Microsoft.PowerShell.Commands.RenameItemCommand

PS C:\ProgramData\Microsoft\Windows\AppRepository>
Tom Driscoll 0 Reputation points

2026-04-18T18:29:12.3366667+00:00

This same exact issue with copilot started for me following the Windows 10 updates this week
Brian Buehler 10 Reputation points

2026-04-19T01:56:11.12+00:00
I have the same problem. I decided to download from the site and not the store and watched it as it installed and saw it place the start menu link in the programs and then it vanished. I got this answer from Copilot when I explained what happened.

when it was installing on windows 10 it did and then it disappeared when it was adding the ability to access app settings with a right click

Ahh, now your comment makes perfect sense — you’re describing something that did happen on Windows 10 during the early Copilot rollout. And yes, what you saw is real:

⭐ On Windows 10, Copilot did briefly create a normal Start Menu shortcut

During the early preview builds, Windows 10 placed a temporary .lnk file here:

Code

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Copilot.lnk

It behaved like a normal Start Menu entry because Windows 10 didn’t yet have the deeper shell integration that Windows 11 uses.

⭐ Why it disappeared

When Microsoft updated Copilot on Windows 10 to support:

right‑click access to App settings

deeper integration with Edge WebView2

system‑level protocol handling

…the old .lnk shortcut became unnecessary and was removed.

After that update, Copilot switched to the same model Windows 11 uses:

No .exe

No Start Menu .lnk file

Launched via protocol handler, not a file path

So the shortcut vanished because the app transitioned from a traditional-style entry to a system component.when it was installing on windows 10 it did and then it disappeared when it was adding the ability to access app settings with a right click

Ahh, now your comment makes perfect sense — you’re describing something that did happen on Windows 10 during the early Copilot rollout. And yes, what you saw is real:

⭐ On Windows 10, Copilot did briefly create a normal Start Menu shortcut

During the early preview builds, Windows 10 placed a temporary .lnk file here:

Code

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Copilot.lnk

It behaved like a normal Start Menu entry because Windows 10 didn’t yet have the deeper shell integration that Windows 11 uses.

⭐ Why it disappeared

When Microsoft updated Copilot on Windows 10 to support:

right‑click access to App settings

deeper integration with Edge WebView2

system‑level protocol handling

…the old .lnk shortcut became unnecessary and was removed.

After that update, Copilot switched to the same model Windows 11 uses:

No .exe

No Start Menu .lnk file

Launched via protocol handler, not a file path

So the shortcut vanished because the app transitioned from a traditional-style entry to a system component.

My guess is that for Windows 10, the link in the Programs file was nessessary for the start menu link to work. I first moved the link to the desktop before it could be erased and when it finished, the link worked. Could you fix it so when it installs it doesn't delete?
Tom Driscoll 0 Reputation points

2026-04-19T02:34:49.6866667+00:00

Reinstalling only gives you functional copilot for one use. The taskbar shortcut will vanish within moments and the start menu entry will have a progress bar under it and no longer open until you reinstall or uninstall and reinstall.
Brian Buehler 10 Reputation points

2026-04-19T03:37:38.6633333+00:00

I installed it one last time and then opened the following folders: Program Files (x86), Microsoft, Copilot, Application and then copied and pasted a shortcut to mscopilot app, renamed the shortcut to say Microsoft Copilot. If you want the link to view in the start menu then open the following folders: Program Data, Microsoft, Windows, Start Menu, Programs then drag the shortcut to the folder down below the other icons. It'll do until they fix the actual link.
Tom Driscoll 0 Reputation points

2026-04-19T03:46:08.9533333+00:00

Thank you
Hendrix-V 14,170 Reputation points Microsoft External Staff Moderator

2026-04-19T04:02:39.4333333+00:00

Hello,

If it still fails after the steps above, the next approach is to use Get Help > Contact Support and also submit the behavior through Feedback Hub (Windows + F), especially since more than one Windows 10 user in the thread reported the same symptom after recent updates.

Please note that this is a user-to-user support forum. Moderators, contributors including external Microsoft employees cannot directly intervene in Microsoft product features or access back-end systems. Our role is limited to providing technical guidance on reported issues, requests, or ideas.

In the meantime, you can still use Copilot on the web, since Microsoft notes the Windows app generally supports the same core experience as the web version.
Monica Meza 10 Reputation points

2026-04-20T13:10:19.1866667+00:00
Thanks Hendrix-V for your response.

As others have said, step 3. Error in not finding the repository file and can't rename.

On step 5.

Windows Resource Protection found corrupt files and successfully repaired them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline repairs, details are included in the log file provided by the /OFFLOGFILE flag.

and after that, restarting -> installing the app, everything keeps the same - it launches but not after closing.

then as I read other comments I will install/repair the app when needed until a working fix is found.

Thanks all who comment this thread and if you try other steps and find the fix please share with us.
DarlaKay 5 Reputation points

2026-04-20T17:54:04.66+00:00

Brian Buehler- YES YES YES! Your workaround was spot on for me. Thanks for a very clear step-by-step instruction. After pasting on my desktop I dragged the icon to my taskbar where Copilot had been happily living until MS update evicted it. Thank you.
DarlaKay 5 Reputation points

2026-04-20T17:55:47.6333333+00:00

Hendrix - Because the 2nd part of step 3 didn't work for me is there anything I need to do to restore what did complete successfully (Step 2 and 1st part of step 3)?
Brian Buehler 10 Reputation points

2026-04-20T21:17:02.4533333+00:00

I discovered something. I checked to see if the Microsoft 365 Copilot would have the same issue but it didn't. I opened the WindowsApps location and saw that the files meant for that program had more in it plus the application for Microsoft 365 Copilot itself which would explain why it worked. The original Copilot only had three files and that was for all three packages. Maybe they forgot to put the needed files in or was that on purpose?
Brian Buehler 10 Reputation points

2026-04-20T21:37:32.4866667+00:00

I used Powershell and used the command Hendrix suggested but nothing happened and returned to the prompt. I'm not messing with it anymore and I'll just make due until a solution is made so if an update is released that it works.
Hendrix-V 14,170 Reputation points Microsoft External Staff Moderator

2026-04-24T06:37:20.0166667+00:00

Hi,

Please note that I can provide suggestions and share any potential workarounds that might help while the issue is still being reviewed. I’m in the same position of waiting for updates, and I’ll continue to support you with any new information or alternative solutions I can provide in the meantime.

As an alternative workaround, you can still use Copilot on the web, since Microsoft notes the Windows app generally supports the same core experience as the web version.
Michael Triggs 0 Reputation points

2026-04-30T03:32:16.08+00:00

To Brian Buehler - thank you. The workaround you suggested did the trick. I've had the same issue from Windows 10 with the application version of Copilot since last week.
AC 0 Reputation points

2026-05-04T07:27:36.1033333+00:00

same issue for me, an update has broken copilot on my Win 10 installation, wasted time uninstalling/reinstalling to no effect. The workaround posted by Brian Buehler did the trick, i.e. create a link to the .exe which via the store installation doesn't work in the start menu any more.

Answer 2

To fix a Copilot app on Windows 10 that won’t open (icon flashes/loads but no window), use these steps:

Uninstall Copilot completely
- Open Settings > Apps > Apps & features.
- Search for Copilot.
- Select Copilot > Uninstall and complete the removal.
(Optional, advanced) Remove via PowerShell if normal uninstall fails
- For advanced scenarios, a PowerShell script can be used to remove Copilot. See Remove the Copilot app in the documentation linked under “Remove the Copilot app” for details.
Restart Windows
- After uninstalling, restart the PC to clear any stuck processes or cached state.
Reinstall Copilot from Microsoft Store
- Open Microsoft Store.
- Search for Copilot.
- Install Copilot again from its Store page.
Test launch behavior
- Start Copilot from the Start menu.
- Close it and reopen it a few times to confirm it now launches reliably.

If the issue persists even after a clean uninstall/reinstall, run the Microsoft Store reset as well (this can fix Store-installed app issues):

Press Windows key + R.
Type wsreset.exe and select OK.
A blank Command Prompt window opens and closes after a few seconds, and Microsoft Store will open automatically.
Reinstall Copilot again from Microsoft Store and test.

If none of these steps resolve the problem, use the Get Help app and run the Copilot troubleshooters (license and connectivity) to see if there are underlying account or connectivity issues affecting Copilot.

References:

Share via

Copilot App in Windows 10. not starting keeps loading but nothing appears

2 answers

⭐ On Windows 10, Copilot did briefly create a normal Start Menu shortcut

⭐ Why it disappeared

⭐ On Windows 10, Copilot did briefly create a normal Start Menu shortcut

⭐ Why it disappeared

Your answer