DKE Unable to save or create this file. Check that the disk where you want to save the file is not full, w

Question

For more than a month we have opened an incident with Microsoft support ( TrackingID#[Moderator note: personal info removed]) , but the various consultants who have worked on this problem are currently unable to solve it.

We have fully documented the origin of the problem, but we are completely blocked to date in the project to deploy the purview DKE solution

https://workingtogether.fun/2025/11/11/dke-purview-encryption-unable-to-save-or-create-this-file-check-that-the-disk-where-you-want-to-save-the-file-is-not-full-and-write-protected-or-damaged/

Answer 1

The error message "Unable to save or create this file" can occur due to several reasons related to disk issues. Here are some potential causes and solutions:

1. Disk Full: Ensure that the disk where you are trying to save the file has enough free space. You may need to delete unnecessary files or move them to another location.
2. Write Protection: Check if the disk is write-protected. If it is a removable disk, ensure that the write protection switch is not enabled.
3. Disk Damage: The disk may be damaged. Try using a different disk or drive to see if the issue persists.
4. Disk Formatting: If the disk is not properly formatted, you may need to format it, but be aware that this will erase all data on the disk.
5. Network Issues: If you are saving to a network location, ensure that there are no network connectivity issues. Restarting your network may help.

If these solutions do not resolve the issue, it may be beneficial to continue working with Microsoft support to troubleshoot further, as they may have additional insights into the specific DKE implementation and any related issues.

---

References:

• Unable to write to the disk

Answer 2

Dear @laurent Teruin [MVP], 

Good day! Welcome to Microsoft Q&A forum! 

Based on your description, I understand that you're encountering a persistent DKE error (“Unable to save or create this file…”) and that, despite having an open Microsoft support case for over a month, the issue hasn’t been resolved and is preventing you from moving forward with your Purview DKE deployment.

I sincerely apologize for the inconvenience caused by this issue.

Regarding your situation, as forum moderators, we don’t have access to the deep diagnostic tools, internal logs, or backend systems needed to investigate this type of issue due to privacy and security requirements. Because of that limitation, the most effective next step is to continue working directly with the support engineer assigned to your case.

The troubleshooting steps they provide are part of a structured process designed to accurately identify the root cause and escalate the case to the appropriate engineering teams. These steps help ensure that nothing is overlooked and that your issue is being handled with the depth and precision it requires.

By continuing to follow the guidance from your support engineer, you help the investigation move smoothly through the correct channels, which ultimately leads to a more efficient and reliable resolution.

I understand how challenging it is when an issue impacts your project timeline, and I truly appreciate your patience throughout the process.

Please continue working closely with your support engineer as they’re equipped to dive deeper, escalate internally, and coordinate the next steps needed to reach a resolution.

Your cooperation and the documentation you’ve already provided are key parts of moving this toward a successful outcome. I appreciate the effort you’ve already put into this.

Thank you for your kindness and understanding!

---

If you have extra questions about this answer, please click "Comment". 

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.