I started using 2025 a few days ago, and the movebak path is being ignored but not all the time. For years I've had it set to c:\temp\bak with no issues.
Is anyone else having the same issue?
No, it's the AutoCAD Express Tool to specify where you want the BAK file to be written ("." for current directory or type in a specific directory).
I submitted a support case and was told even though the command is an Express Tool (which are provided as a courtesy and are unsupported by Autodesk) the developers are addressing the problem and it has the reference ID of ACD-42748.
Hi @jbokic2F9MM, Thanks for sharing about it. Honestly, when I read your post, I thought you were talking about a very different thing. Submitting the support ticket is the best way to solve that problem. I hope the support team helps you.
Best regards!
Thanks @ecfernandez and you're right. In cases like this it's a system bug and beyond peer help. Will post up with any new results.
I can see how this would seem like a Vehicle Tracking issue!
Hi, Yes, I'm having the same issue with movebak and likewise I've used it for years without issue.
I've seen this same scenario several times before: a command will work just fine for years then, for whatever reason, it gets broken in a new release.
Hi everyone,
I appreciate your patience as we address the issue with movebak in AutoCAD 2025. I've added notes to the development write-up, and I can confirm that our development team is actively working on a fix. While I cannot share a specific timeline, please know that resolving this issue is a top priority for us and is on their radar.
Thank you for bringing this to our attention.
@ShawnMcCorkle1211 wrote:I have been having the same issue.
Known 2025 issue, it's not going to get fixed anytime before a major SP update is released, try any and all updates as and when they show up HERE, if and when it happens you'll know as soon as the rest of us do.
The latest service patch seems to have fixed the MOVEBAK problem. My current builds are AutoCAD 2025.1 and Civil 3D 2025.0.2 Update.
Sadly, it appears I don't have access to the update you mention. Hopefully we get it soon.
Can't find what you're looking for? Ask the community or share your knowledge.