Windows 10: CoPilot will not load - unable to connect to the service

My issue is that CoPilot will not load on my computer. This is happening on my new Surface Laptop 6 for Business with Co-Pilot built in, as well as within Edge. It attempts to load for a while, and eventually I get the message "We're sorry but we're unable to connect to the service at this time."I just reinstalled Windows 11 yesterday, so there may be something related to that. Any ideas on what is happening?Thanks,Rob

:)

 

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

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

 

Why I cannot access CoPilot or Bing as it show this:We're sorry but we're unable to connect to the service at this time. Please try again later or refresh

I cannot access Bing CoPilot anymore as it replies: We're sorry but we're unable to connect to the service at this time. Please try again later or refresh. I tried and tried and nothing happened.

 

Unable to Connect to Logical Disk Manager Service Error in Computer Management

EDIT: I also edited dcomcnfg properties to allow EXPLICIT access for the services involved with MY USERNAME, though it is part of a legit Admin group, I added it explicity... don't know if this had ANYTHING to do w/ it, but am adding it for reference here!

I got it, & the disk is formatting as I speak... listed as 100% @ this point now.

(Yes, it is rather "funny", but it helps me record steps & "think out" what the problem MIGHT be)...

* It was REALLY 'ticking me off', because I got SUCH a good deal (imo @ least) for this 250gb drive ($65 U.S. Dollars) I was rather upset I could not even format it because of this service NOT running as it should have... now, I know the way of it to get it working & so does everyone else (or, @ least this much of how to get it running again).

APK

P.S.=> Hopefully, this list will be useful to anyone else that hits a "snag" using diskmgmt.msc & finds it cannot connect... apk