Please note: We are aware of an issue affecting replies on the Arm Community forums, which may not be loading as expected.
We apologize for any inconvenience and appreciate your patience while we investigate and work to resolve the issue.
Thank you for your understanding.
Hello,
I have the latest version of Keil uVision (5.43.1.0) and am using a community edition license.
This is my first time using Keil. When I try to create a project, after selecting the directory and device, I get an error saying: "Cannot write project file 'XXX.uvproj'!"
It creates empty 'Listings' and 'Objects' folders in the location but no project file.
I am able to open some example projects but cannot save them after modifying- I get the same error message.
I have tried:
I'm not sure what else to check or try. Would appreciate any help.
My first intention is to ensure read and write permission, but you already checked this.
- What is the exact Windows version in use?
- Do you have sufficient storage left on your drive?
- Do you have problems opening/writing data with other tools on your PC?
- Are you using a VPN?
- Is there any Virtual Machine in use?
- Windows Version 10.0.26200.8037
- I have over 280GB of free storage
- No issues with any other tools
- I'm not using a VPN nor a virtual machine.
I have a feeling there is something basic I am overlooking, maybe to do with my installation settings or something...
Appreciate the help!
Thank you.
You confirm "...I have the latest version of Keil uVision (5.43.1.0) and am using a community edition license..."
-> Please share a screenshot of the License Management window.
-> To what exact folder is MDK installed?
Hi, sorry for the delay.
Here's the screenshot:
MDK is currently installed in: C:\Keil_v5
Thanks again.
Thank you, that looks fine.
Other than the topics we have discussed already, an idea is to check the Windows Defender ransomware protection:
Windows Security → Virus & threat protection → Ransomware protection → Manage ransomware protectionIf Controlled folder access is on, either:
- temporarily turn it off to test, or- add UV4.exe / uVision as an allowed app
Also, try Run as administrator once, only as a diagnostic. If that fixes the problem, the issue, I assume, is definitely permission/policy related rather than project corruption.