Windows 10: Sorry, we ran into a problem loading this app Copilot error

WinClub · Nov 7, 2025 at 7:07 PM

While opening Copilot in Windows 11, if you encounter an error message saying Sorry, we ran into a problem loading this app, here is how you can troubleshoot the issue on a Windows 11 PC. Even with a valid subscription, you may encounter this error when opening the app. That is why we have consolidated […]

This article Sorry, we ran into a problem loading this app Copilot error first appeared on TheWindowsClub.com.

read more...

Brink · Nov 7, 2025 at 7:13 PM

Copilot added to DevTools in Microsoft Edge

We’re very excited to announce that, starting with Microsoft Edge 120, we’re making a new experimental DevTools feature available to all. You can now ask DevTools to explain any error or warning, and any code snippet by using Copilot in Edge. Whether you’re new to web development or have already been building websites, errors and warnings in the DevTools Console is something you probably deal with all the time. While some errors make sense and help you correct bugs, some can be very obscure or even scary. Can you confidently say what the following errors mean, without searching? Code:

Access to fetch at 'Your request has been blocked. This could be due to several reasons.' from origin 'https://microsoftedge.github.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Uncaught (in promise) SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON.

Uncaught TypeError: Converting circular structure to JSON.

Uncaught TypeError: Cannot define property x, object is not extensible.
Click to expand...

These errors can very often feel cryptic, especially when learning web development. But they also play a very important role in learning. They’re how the browser tells you something’s wrong, where it’s wrong, and perhaps how to fix the problem. Unlike other languages, JavaScript doesn’t require a compilation step to run. C++ or Rust, for example, give you a lot of information at compilation time. With JavaScript, these runtime errors in the DevTools console are often your only way to know something’s wrong. But let’s face it, compilers and JS engines are similar in that they don’t always make it easy to understand what they’re trying to say. Common solutions include:

Searching for the error message online, hoping to find a useful answer.

Or asking a coworker for help.

Unfortunately, this doesn’t always lead to a good solution. For instance, what if no one has written a clear explanation for your particular problem online? What if you don’t have a coworker who can help you right now? What if you’re focused on your code and don’t want to get distracted by going to another website? Given the right context, Copilot in Edge can reason about complex problems and easily find custom solutions for them. If you use Microsoft Edge for your web development, you already have access to Copilot in Edge. You can already use Copilot in the Microsoft Edge sidebar to generate text or images, or search for web results. Starting with Microsoft Edge version 120, you can now ask Copilot to explain console errors and warnings, as well as source code, right from where you need it in DevTools!

With Copilot in Edge integrated into DevTools you can:

Ask Copilot to explain any error or warning displayed in the Console. Just click the Copilot button next to an error:

Ask Copilot to explain any snippet of code selected in the Sources tool. Just select some code, right-click, and choose Copilot: Explain these lines of code:

When you do any of these two actions, the Copilot in Edge sidebar appears, and a conversation about the error, warning, or code that you selected starts. DevTools provides all the context that Copilot needs to reason about the particular problem you’re facing. Copilot generates an explanation, and you can then keep conversing if you want to keep on learning. We’re excited about the possibilities and truly believe that AI, when applied responsibly to specific web development problems, can be a very effective ally. This is only the beginning, and we have more ideas. But first, we’d love for you to try this new experimental feature and let us know what you think. To learn more about enabling the experiment and using the feature, read the docs at Explain errors and source code in Copilot in Edge. The feature is still under active development and you might need to enable it, before being able to use it. If you have any questions, comments, or feedback about the feature, please leave a comment on this GitHub issue.
Click to expand...

Read more:

Just a moment...

https://learn.microsoft.com/en-us/mi...opilot-explain

Try3 · Nov 7, 2025 at 7:13 PM

None of the methods to disable Copilot work, can't even hide it

The reg files do nothing. Copilot is not in the list of things you can turn on or off with the policy editor.
Click to expand...

I suggest you post your question in the tutorial thread to find out if Brink or the other tutorial participants can help you Enable or Disable Copilot - TenForumsTutorials Best of luck, Denis

John Jefferson Doyon · Nov 7, 2025 at 7:13 PM

Copilot problem

Thank you for sharing the video of what you're seeing.

You're not alone, some users are also experiencing this issue either because they're using a work or school PC or it is currently not available in their country or region. I found a very similar case to yours. Here is the link: (English forum) https://answers.microsoft.com/en-us/windows/for...

It is possible that Copilot for Windows (Copilot Taskbar) is currently not available in your country. The steps provided by user Bennmane suggest changing some registry settings and temporarily changing the language and region. Here is the link: (English forum) https://answers.microsoft.com/en-us/windows/for... It may not be applicable for you to change the region to the United States, so you can skip that step.

You can also make sure that the default browser is Microsoft Edge. Also, you can follow these steps to repair Microsoft Edge:

> Make sure your browser is closed, and you have administrative rights to your device.

> Press the Windows + I key to open Settings.

> Click on the "Apps" tab. > Click on "Installed apps."

> Scroll through the app list or use the search bar to locate the Microsoft Edge.

> Click the three-dots menu (...) next to Microsoft Edge and select "Modify"

> When prompted to allow changes, select Yes.

> Now, make sure you're connected to the internet and choose Repair. This process should not affect your browser data and settings.

> Wait for the process to complete, after that, Edge will open, close it and restart your PC.

After that, restart your PC and check if the issue persists.

If the issue persists, please let me know.

John J.D.

Windows 10: Sorry, we ran into a problem loading this app Copilot error

Sorry, we ran into a problem loading this app Copilot error

Sorry, we ran into a problem loading this app Copilot error

Sorry, we ran into a problem loading this app Copilot error

Sorry, we ran into a problem loading this app Copilot error - Similar Threads - Sorry ran problem

copilot stuck in a loop of "we cant talk about that, sorry."

copilot stuck in a loop of "we cant talk about that, sorry."

"Unexpected error. Sorry, we ran into a problem. Please try again." When trying to open...

"Unexpected error. Sorry, we ran into a problem. Please try again." When trying to open...

unexpected error sorry we ran into a problem windows defender

unexpected error sorry we ran into a problem windows defender

unexpected error sorry we ran into a problem windows defender

unexpected error sorry we ran into a problem windows defender

Microsoft Word Online Issue: Sorry we ran into a problem.