Share via

Error 1926/1307) on AutoCAD 2025 after User profile redirected to D: drive

LAM SHIU 20 Reputation points
2026-02-08T15:49:49.8733333+00:00

We are experiencing an issue on Windows 10 LTSC 21H2 (and possibly other versions) where non-administrator users cannot launch AutoCAD 2025 (and other Autodesk products like Revit 2025) for the first time without issues.

Symptoms:

When a standard user launches AutoCAD 2025 for the first time, it triggers a Windows Installer (MSI) repair/self-healing process.

This results in Error 1926: "Could not set file security for file 'D:\Config.Msi\xxxxxxxx.rbf'. Error: 1307. Verify that you have sufficient privileges to modify the security permissions for this file."

The user profile directory has been redirected to D:\Users (via ProfilesDirectory or Folder Redirection), so Config.Msi is created/accessed on D: drive instead of C:.

Permissions on D:\Config.Msi are already set to Full Control for SYSTEM, Administrators, and the user (verified with icacls), but the error persists on first launch.

Workarounds that work temporarily: Kill acad.exe process once and relaunch, or reboot the PC. After that, subsequent launches work normally for that user.

This affects multiple new users daily in a shared/enterprise environment, making per-user manual fixes impractical.

Windows for business | Windows Client for IT Pros | Devices and deployment | Set up, install, or upgrade
0 comments
Answer accepted by question author
  1. VPHAN 25,000 Reputation points Independent Advisor
    2026-02-08T16:23:09.46+00:00

    Hello LAM SHIU,

    To resolve this immediately across your enterprise without touching every user profile, the most robust engineering solution is to disable the MSI Rollback feature via Group Policy or Registry. Since the application is already successfully installed and this is merely a user-level self-healing event, the rollback functionality is redundant and causing the failure. Open the Registry Editor on your golden image or push this via GPO: navigate to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer. If the Installer key does not exist, create it. Inside, create a new DWORD (32-bit) Value named DisableRollback and set its value to 1. This directive forces the Windows Installer service to skip creating the problematic .rbf files in D:\Config.Msi entirely, thereby bypassing the security descriptor failure.

    If your security policy strictly forbids disabling rollback globally, you must manually pre-create the D:\Config.Msi folder and strictly enforce the ownership and attributes that the MSI service expects, though this is less reliable. You would need to ensure the folder is hidden and identified as a system folder (attrib +h +s D:\Config.Msi), set the Owner to the Administrators group (not the user), and ensure CREATOR OWNER has Full Control in the Advanced Security settings. However, given the "Could not set file security" error, the DisableRollback registry modification is the definitive fix for 21H2 LTSC environments utilizing ProfilesDirectory redirection.

    I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

    VP

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-02-08T15:50:01.0066667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The issue you are experiencing with AutoCAD 2025 and the Error 1926 is likely related to the User Account Control (UAC) prompts that can occur for standard users when performing Windows Installer (MSI) repair operations. After installing the August 2025 Windows security update, UAC prompts for administrator rights can appear for standard users in various scenarios, including launching applications like AutoCAD for the first time.

    In your case, since the user profile is redirected to the D: drive, the Windows Installer may be attempting to modify permissions on files located in that directory, which could lead to the error you are encountering. The error message indicates that the user does not have sufficient privileges to modify the security permissions for the file, even though permissions appear to be set correctly.

    To resolve this issue, you may consider the following approaches:

    1. Update Windows: Ensure that the latest Windows updates are installed, as subsequent updates after the August 2025 update have refined the UAC requirements for MSI operations.
    2. Allowlist MSI Files: IT admins can add specific MSI files to an allowlist to disable UAC prompts for those applications, which may help in your scenario.
    3. Group Policy: Consider utilizing Group Policy settings to manage UAC behavior for standard users in your enterprise environment.

    These steps may help mitigate the issue for new users in your shared environment without requiring manual fixes for each user.

    References:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.