Share via

Surface copilot plus issue with 0xc0e90001 code

Anonymous
2025-01-29T18:49:03+00:00

I did rebuild using Microsoft software according to serial number

Did insider build updates it said on line that Microsoft is aware of the issue

I did talk with Microsoft rep he is thinking is a hardware issue but I don't have any other problems as far as I know.

Trying to avoid sending unit for warranty unless I have no choice

Is there any software fix for this?

Surface | Surface Pro | Performance and maintenance

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-02-08T08:22:04+00:00

    Hi Szadok,

    Even if you are willing to share the Case ID with us, unfortunately, we cannot query this Case, because we are not affiliated with the Surface technical support team, so we do not have the permission to query.

     If this problem does not exist in the official version of the system, only when the insider version is installed, it will appear abnormal, which means that the version does have a problem, it is recommended that you do not update for the time being, and report to Microsoft's development team through the feedback center:

    Send feedback to Microsoft with the Feedback Hub app - Microsoft Support

    Best Regards,

    Mitchell | Microsoft Community Support Specialist

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-01-30T16:26:36+00:00

    Yes I did this steps before I downloaded and updated to window insider build by updates .

    Ticket nr 7065530502

    Why I did the update to insider build I found info that one of the updates would take care of the code.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2025-01-30T08:55:54+00:00

    Hello Szadok,

    Welcome to Microsoft Community.

    I note that you seem to have communicated with Microsoft representatives on this issue, but it seems to me that there is no direct evidence pointing to a hardware issue unless you have presented corresponding evidence in previous communications, but have not shared it here.

    I suspect you may have seen a page that looks like this screenshot:

    So didn't the Microsoft agent guide you through the correct steps to redeploy the system all over again? If they did not, allow me to share the full steps here:

    Creating and using a USB recovery drive for Surface - Microsoft Support

    In fact I'm sure you're familiar with this process, but I would like to remind you to prioritize the deployment of the official version of your Surface Pro by going through this step first, and when you're done, please check if you still see this error when Surface Pro 11 is being used normally under the official version of the system.

    • If the same issue recurs under the official system, then I agree with the Microsoft agent that you need to take your Surface to the Surface Support team to have it checked.
    • However, if the problem doesn't recur, it means that the fault is not originating from the hardware, but most likely from the Insider version of the system. This is a test version and as such has some instability and is more prone to crashes than the official version.

    If you are still looking for some solutions, then I recommend you give my suggestions a try. 

    Best Regards,

    Mitchell | Microsoft Community Support Specialist

    Was this answer helpful?

    0 comments