Work in SolidWorks Often interrupted by critical errors, one of the most annoying is the message about the inability to create a log file. When the system reports that “it was not possible to create a auto recovery log file will not work”, it means that the data protection mechanism against failures is completely disabled. The engineer needs to respond immediately to this signal, as the risk of losing hours of work becomes critical.
The reason lies not in the bugs of the CAD engine itself, but in the conflict of operating system access rights or incorrect paths to system folders. Windows It can block the recording of temporary files in protected directories if the user does not have the appropriate privileges. Often the problem is exacerbated by antivirus software or a crowded system partition.
In this article, we will take a detailed look at the error-correction algorithm, ranging from checking the paths in the registry to changing security policies. Ignoring this problem is like working without insurance. Log files are created in a folder, a specific environment variable of %TEMP%, and that is where the system tries to write data before crashing. Understanding this mechanism is the key to a quick solution.
Analysis of the causes of the error
The first step in diagnosing is to understand why. SolidWorks Loses the right to record. The error often occurs after an operating system update or a user account change. In such cases, new profiles may not have full rights to create files in root directories or specific temporary storage folders.
Another common reason is antivirus protection. Programming Kaspersky or ESET You may consider trying to quickly create multiple temporary files as suspicious activity. The locking occurs at the file filter level, and the user sees only the final error message, without understanding the true source of the lock.
It is also worth considering the integrity of the installation of the software complex. If the component files SwScheduler.exe If the auto-save libraries are damaged, the process will not be able to initialize the creation of the log. Sometimes the problem lies in the overflow of the disk, where the system partition is located, which physically does not allow you to create a new file even if you have rights.
⚠️ Warning: Ignoring the “failed to create a log file” error results in no backups. If the power is suddenly turned off or the system freezes, all unsaved changes will be lost irrevocably.
For accurate diagnosis, it is useful to check whether the specified path is available for manual recording. Try to create a test text file in the folder specified in the autosave settings. If the system issues an access error, the problem lies in the NTFS rights plane, not the settings. SolidWorks.
Verification of paths to temporary files and registry
The main configuration of the ways of storing temporary data is in the system registry Windows. SolidWorks It relies on environmental variables, but it can have its own overdefinitions. You need to make sure that the path where the program is trying to write a journal is physically present and accessible.
Open the Registry Editor by entering the command regedit in the search bar. Go to the branch responsible for user settings or global settings SolidWorks. Often the path is spelled out explicitly, and if the folder has been deleted or renamed, creating the file will become impossible.
Where to find the keys of the SolidWorks registry?
Tracks are usually found in HKEY CURRENT USER\Software\SolidWorks\SOLIDWORKS [version]\ExtReferenceHandler or in Windows environment settings. Be careful when editing the registry – back up before making changes.
Check the operating system environment variables. To do this, right-click on “My Computer”, select “Properties” and go to “Additional System Settings”. In the "Ambient Variables" section, make sure that the variables are TEMP and TMP They are the directories that are in place, usually C:\Users\Username\AppData\Local\Temp.
If the paths in the registry lead to a network resource or an external drive that is not currently available, the error will occur constantly. Local paths are preferred for auto-save files, as they provide maximum write speed and minimal risk of connection breakage at a critical moment.
In some cases, cleaning the contents of the folder helps. Temp. Accumulation of thousands of old temporary files can slow down the file system or cause indexing errors, which prevents the creation of new log files. Deleting the contents of this folder is safe if no program is running.
Configure access rights and folder properties
The most effective solution to the problem is to adjust the NTFS access rights to the folder where temporary files are stored. Even if you are an administrator, a particular folder may have write restrictions for a current session or group of users.
Find the folder listed as the path for auto-save (usually this one). C:\SolidWorks Data\SolidWorks AutoRecover or similar. Right-click, select “Properties” and go to the “Security” tab. You need to check the list of groups and users.
☑️ Configuring access rights
Make sure that the Users group (or your user name) has the rights to Change and Record. If no such rights exist, click “Change”, select the user and tick “Full Access” or “Change”. Apply the changes to all attached files and folders.
It is also worth checking if the “read-only” checkbox is set in the general properties of the folder. While this is often ignored for system folders, in some configurations, it is not. Windows This attribute can block the creation of new files within the directory. Remove the “read-only” attribute and confirm the application to all nested items.
If you work on a corporate network, rights can be inherited from the parent folder or the group policy of the domain. In this case, the local change of rights can be blocked. Contact your system administrator to request that you exclude the autosave folder from your strict security policies.
⚠️ Note: Changing the permissions to system folders (e.g., the root of the C: disk) may disrupt other programs. Change permissions only for a specific SolidWorks or Temp work folder.
The impact of antivirus and firewall
Antivirus software is often the hidden culprit behind performance and stability issues. SolidWorks. Heuristic analysis mechanisms can mistakenly classify frequent log file recording as the behavior of a ransomware virus or miner.
To resolve the conflict, you need to add exceptions to your antivirus settings. Executable files should be included in the white list sldworks.exe, SwScheduler.exe And critically, the folder where the autosave files are created.
Also, check the firewall settings. Windows Defender. Although it is less likely to block a local record, it can interfere with the operation of components responsible for licensing or network preservation, which indirectly affects the process of creating a log. Make sure that SolidWorks They have permission to work in private and public networks.
Temporary shutdown of the antivirus will help to accurately diagnose the problem. If after disabling the protection, the error disappears, then you need to fine-tune the rules of the antivirus, not its complete removal. Do not leave your computer unprotected for a long time.
Use your antivirus’s “Quarantine” or “Events log” to see if it has recently blocked files with the .sldwrk or .swp extension.
Some system “optimizers” and registry cleaners can also delete lock files or change folder access rights. Temp in the background. Configure these snails to ignore the working directories of engineering software.
Solving Disk and File System Problems
The physical condition of the storage device plays an important role. If the disk on which the log is written has broken sectors or is full, the write operation will end in error. SolidWorks You cannot create a file if the file system refuses.
Check the free space on the system disk. For the right job SolidWorks It is recommended to have at least 10-15 GB of free space. Lack of space is one of the most common but frequent causes of failures.
Check the disk for errors. Open the command line on behalf of the administrator and enter the command to check the drive:
chkdsk C: /f /rThis command will check the file system and try to repair the damaged sectors. Please note that to check the system drive will require a restart of the computer. Also, defragmentation (for HDD) or optimization (for SSD) can improve response speed.
| Parameter | Norma. | Critical condition | Action. |
|---|---|---|---|
| Free seat | > 15 GB | < 2 GB | Clearing the disc |
| Fragmentation | < 5% | > 15% | Defragmentation |
| SMART Mistakes | 0 | > 0 | Disc replacement |
| File system | NTFS | FAT32 | Conversion |
If the disk is old or has signs of physical wear (strange sounds, slow work), files can be created with a delay, which is perceived by the program as a timeout and error. In this case, the replacement of the drive for modern SSD It's going to solve the problem.
The health of the hard drive directly affects the stability of the CAD systems. Regularly diagnosing the disk prevents data loss.
Alternative methods and resetting settings
If standard methods do not help, you can try to reset the settings. SolidWorks To the factory. This often resolves issues caused by user profile damage or conflicting plugins. Reset can be done through the utility "SolidWorks Rx" or manually through the registry.
Try changing the way you save temporary files to another local drive. For example, create a folder. C:\SW_TempGive it full access rights and specify this path in the settings. This will help eliminate rights problems in the standard folder. AppData.
In extreme cases, you can turn off the auto-save function, although this is highly discouraged. It's done through the menu. Service → Parameters → Backup / Restore. However, this is only a temporary measure until a basic solution to the file system problem is found.
Reinstallation SolidWorks It can also be an option if the program’s system files are damaged. Before reinstalation, be sure to use the removal tool SolidWorksTo clean up all the remnants of previous versions.
⚠️ WARNING: Before resetting or reinstalling, be sure to save your custom templates, materials libraries, and hotkey settings to avoid losing personalization.
Check for updates to be made to SolidWorks. The company regularly releases patches (Service Packs) that fix known compatibility errors with new versions. Windows. Installing the latest Service Pack can automatically fix the log bug.
What do you do if nothing helps?
If none of the solutions worked, create a new Windows user account with administrator rights and check out SolidWorks there. This will help you understand if the problem is in the user profile or in the system as a whole.
Frequently Asked Questions (FAQ)
Where exactly is SolidWorks trying to create a log file?
By default, the program uses a system variable. %TEMP%which usually leads to C:\Users\[User]\AppData\Local\Temp. Also, files can be created in the program installation folder or in the document folder if local autosave is configured.
Can I turn off the creation of a journal completely to remove the error?
Technically, you can disable logging in the settings, but it is extremely dangerous. Without a log and auto-save mechanism, you risk losing all your job in any failure. It is better to eliminate the cause of the error than to disable the protection.
Does the Windows version affect this error?
Yeah, in Windows 10 and Windows 11 More stringent security and process isolation policies than Windows 7. This often causes access rights conflicts for old software or misconfigured paths.
How often does SolidWorks create auto-save files?
The interval is set by the user in the settings (by default it often costs 20-30 minutes). At each interval, a new log file is created. If the disk is slow or busy, this is when the recording error occurs.
Will the launch on behalf of the administrator help?
Launch sldworks.exe On behalf of the administrator, the problem of access rights is often solved temporarily. However, it is not recommended as a permanent solution due to security concerns. It is better to configure the rights to the folder correctly.