Co-pilot is slow becoming a part of our daily journey in Windows. But, like every new feature in Windows, it isn’t completely error free. There are multiple error reports that looks like this “Can’t access your webpage” prompt apearing in the Co-pilot. There is a very simple workaround and you can use that to fix the problem.
Fix 1 – Use Co-Pilot in MS Edge
The Co-Pilot can be used in the Microsoft Edge as well.
Step 1 – To do this, open Micrsoft Edge or Google Chrome (won’t work on any other browser).
Step 2 – Then, paste this in a new tab and press Enter.
copilot.microsoft.com
Step 3 – Tap “Sign in” to sign in using your Microsoft account.
Now, ask the same question or perform the same thing that you were trying to do in Co-Pilot.
There won’t be anymore “Can’t access your webpage” error message in there.
Fix 2 – Refresh the CoPilot
Refresh the Co-Pilot and retry the same process.
Step 1 – In the Co-Pilot side panel, there is a small three dot button.
Step 2 – Tap that once and then, click “Refresh” afterwards to refresh the Co-Pilot page.
This will offer you a fresh, new page where you can start from the scratch.
Fix 3 – Check the internet connection
The Co-Pilot is completely dependent on the network connection (as it is basically an website running on the latest version of GPT). So, internet connectivity is crucial.
Check the network connectivity on your system. Use a mobile hotspot, if needed and put the same workload and test.
Fix 4 – Use ChatGPT or any other alternative
If your output requires a GPT or an AI, there are lots of free tools that you can use to do the work. Like, you can use these –
Creative work – ChatGPT
Grammar Checking, Summarizing, Paraphraser, Citation Generator – Quillbot
This way, you can work with alternative and get the desired output, without using Co-Pilot.
NOTE – The Co-Pilot program is still in it’s infancy. It is still offering a preview mode of the feature. So these types of bugs or glitches are quite common. If these solutions doesn’t fix your problem, we recommend restarting the device and checking again.